How do you have multiple TRIRIGA instances on a physical server?


Our customer wants to have two authentication approaches for TRIRIGA: (1) SAML SSO for internal users via the intranet, and (2) RADIUS for external users via the internet. We will have two HTTP servers to handle the external and internal users.

Regarding the different authentication requirements (TRIRIGAWEB.properties settings could be different), we will need two TRIRIGA app server instances. From what I have understand, the TRIRIGAWEB.properties is not packaged into an EAR file. If we deploy the EAR file twice, both TRIRIGA instances will share the same settings. My questions are:

  • 1. Shall we install TRIRIGA twice (so we will have two <TRIRIGA_home> folders) on the same physical server? Can we just have two “config” folders?
  • 2. How does the app server identify the location of the <TRIRIGA_home> folder? The properties files in the EAR file? Or by using classpath?

For this use case, you would want to install TRIRIGA twice, each with its own TRIRIGAWEB.properties and installation directory. One URL and application server would be used for internal users, and the other server would be used for external users.

Continue reading

2 thoughts on “How do you have multiple TRIRIGA instances on a physical server?

  1. Pingback: How do you have multiple TRIRIGA instances with one WAS profile? | TRIRIGAFEEDIA

  2. Pingback: How do you install multiple TDI instances on the same server? | TRIRIGAFEEDIA

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s