Consolidating apps in to one JVM

In the releases prior to 3.54 – GCeasy, fastThread, HeapHero tools were launched in its unique JVMs and ports. Starting from Release 3.54, we GCeasy, FastThread and HeapHero tools will be launched from one single JVM and port. The new tools page will start to look as shown in the below image:

Fig: New Tier1app Enterprise Edition landing page

Backward compatibility

We have seen our customers creating subdomains for each of the tools in their organizations. Example:

https://gceasy.mycompany.com

https://fastthread.mycompany.com

https://heaphero.mycompany.com

 These customers might be wondering how to make the deployment starting from this 3.54 release. We have a couple of options for them.

1. Remapping the domain

You can map all the 3 subdomains i.e. https://gceasy.mycompany.com, https://fastthread.mycompany.com, and https://heaphero.mycompany.com to the new JVM instance where the application is running because new landing page is universal to support all the 3 applications.

2. Launching each tool in separate JVM and port

If you would prefer to launch each application in separate JVMs and ports, that’s also supported. In the folder where the new tier1app installation is unzipped you will see the ‘launch-scripts’ folder. This folder has following scripts:

WINDOWS:
launch-gceasy.bat
launch-fastthread.bat
launch-heaphero.bat

UNIX:
launch-gceasy.sh
launch-fastthread.sh
launch-heaphero.sh

When you launch the tools with these scripts, each tool will be launched in its own JVM and port number. In this way, you don’t have to make any changes to domain mapping.

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 )

Connecting to %s

Blog at WordPress.com.

Up ↑

%d bloggers like this: