How do you have multiple TRIRIGA instances with one WAS profile?

Our customer wants to install multiple TRIRIGA environments on the same physical server, using WebSphere Application Server (WAS) Network Deployment (ND) within the same WAS profile.

But there is an annoying problem. When we launch a new installation, the WAS application (named IBM-TRIRIGA_Build-<building number>) will be reinstalled and the TRIRIGA application will be detached from the application server of the other instance. For the simple reason that the application name was the same for each installation and was installed under the same WAS profile.

There are two solutions in my mind:

  • 1. Install one TRIRIGA instance per WAS profile. So we won’t have the problem of duplicated application names, and the TRIRIGA instances are completely independent of each other.
  • 2. After standalone installation, uninstall the original WAS application, modify the <TRIRIGA_HOME>\was-build.xml by adding a prefix to the “” property. Then launch “ant install-was” to deploy the renamed EAR manually.

Are there any arguments to define the application name during installation? As a newbie, I need your opinion. Any suggestion would be appreciated!

[Admin: This post is related to the 02.16.16 post about multiple TRIRIGA instances on the same physical server.]

Continue reading

One thought on “How do you have multiple TRIRIGA instances with one WAS profile?

  1. 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: Logo

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

Google photo

You are commenting using your Google 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 )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.