18
Views
3
Comments
Solved
Mongo DB Connector is available for Reactive Application for On-premises
Question

Any Mongo DB Connector is available for Reactive Application for On-premises

2024-07-05 14-16-55
Daniël Kuhlmann
 
MVP
Solution

Hi Arkyadeep,

Why you need specifically for Reactive, the integration is on the backend so it would work for RWA, TWA or even mobile as it has no client side logic.

In the Forge there are some components available:

Then recently, OutSystems also introduced MongoDB integration in the Integration Builder, however for that to work in an On-Premise OutSystems infrastructure extra configuration is needed.

For more info on this:

Hope this information is useful for you,

Kind regards,

Daniel

2024-07-05 14-16-55
Daniël Kuhlmann
 
MVP
Solution

From the following document

https://success.outsystems.com/Documentation/11/Extensibility_and_Integration/Create_connectors_with_Integration_Builder/How_to_set_up_Integration_Builder

Integration Builder is a Software as a Service (SaaS) that connects to your OutSystems environment to authenticate and validate user connections. Integration Builder works with Integration Manager to keep the status of your integrations current, so it needs to be able to connect with the environments to which you deploy the integrations. In addition, Integration Builder is available in all OutSystems editions.

That is Free, Standard, Enterprise and Personal environments.

Your OutSystems on-prem infstructure needs to be able to communicate with the internet.

  • Allow inbound and outbound HTTPS communication (port 443) with https://integrationbuilder.outsystems.com. The Integration Builder will use the environment's public DNS hostname to communicate. Check Integration Builder network requirements for detailed information.

https://success.outsystems.com/Documentation/11/Extensibility_and_Integration/Create_connectors_with_Integration_Builder/How_to_set_up_Integration_Builder#setting-up-on-premises-environments

Setting up on-premises environments

When using an on-premises infrastructure with Integration Builder, you need to setup the addresses of the other environments where you'll deploy the integrations after finishing development. For example, for a standard infrastructure, Integration Builder must be able to connect to the development, quality assurance, and production environments but doesn't need to connect to the LifeTime.

After you develop and publish the first integration, the Setup widget at the bottom right prompts you to add the environment addresses.

To set up the environments, follow these steps:

  1. Click the Setup widget to expand it, and the click on Setup environments.
  2. Click Add environment.
  3. Enter a name for the environment and its URL, then click Add environment. The URL is the environment address.
  4. Repeat step 2 and 3 until you have added all your non-LifeTime environments.
2024-07-05 14-16-55
Daniël Kuhlmann
 
MVP
Solution

Hi Arkyadeep,

Why you need specifically for Reactive, the integration is on the backend so it would work for RWA, TWA or even mobile as it has no client side logic.

In the Forge there are some components available:

Then recently, OutSystems also introduced MongoDB integration in the Integration Builder, however for that to work in an On-Premise OutSystems infrastructure extra configuration is needed.

For more info on this:

Hope this information is useful for you,

Kind regards,

Daniel

2023-06-14 08-52-52
Arkyadeep Bharadwaj

Sorry I did not check the component fullyand if I use integration builder I think we can't use in onpremises right.correct me if am wrong.

I will check the component.

2024-07-05 14-16-55
Daniël Kuhlmann
 
MVP
Solution

From the following document

https://success.outsystems.com/Documentation/11/Extensibility_and_Integration/Create_connectors_with_Integration_Builder/How_to_set_up_Integration_Builder

Integration Builder is a Software as a Service (SaaS) that connects to your OutSystems environment to authenticate and validate user connections. Integration Builder works with Integration Manager to keep the status of your integrations current, so it needs to be able to connect with the environments to which you deploy the integrations. In addition, Integration Builder is available in all OutSystems editions.

That is Free, Standard, Enterprise and Personal environments.

Your OutSystems on-prem infstructure needs to be able to communicate with the internet.

  • Allow inbound and outbound HTTPS communication (port 443) with https://integrationbuilder.outsystems.com. The Integration Builder will use the environment's public DNS hostname to communicate. Check Integration Builder network requirements for detailed information.

https://success.outsystems.com/Documentation/11/Extensibility_and_Integration/Create_connectors_with_Integration_Builder/How_to_set_up_Integration_Builder#setting-up-on-premises-environments

Setting up on-premises environments

When using an on-premises infrastructure with Integration Builder, you need to setup the addresses of the other environments where you'll deploy the integrations after finishing development. For example, for a standard infrastructure, Integration Builder must be able to connect to the development, quality assurance, and production environments but doesn't need to connect to the LifeTime.

After you develop and publish the first integration, the Setup widget at the bottom right prompts you to add the environment addresses.

To set up the environments, follow these steps:

  1. Click the Setup widget to expand it, and the click on Setup environments.
  2. Click Add environment.
  3. Enter a name for the environment and its URL, then click Add environment. The URL is the environment address.
  4. Repeat step 2 and 3 until you have added all your non-LifeTime environments.
Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.