Journey Health Check

System Usage

1. System usage displays CPU Utilization and Memory Consumption of Journey Engine and its sub-process for Last 1 hr , 6hrs , 12 hrs , 1 day and 7 days.
2. Unica Director shows RSS memory Consumption on health check screen for RHEL Linux / SUSE/ Windows and AIX operating systems.
3. Memory Consumption displays memory used by the Journey Engine (unica_aclsnr) and its sub-process (unica_aolsnr, unica_acsvr).
4. System usage has zooming capability to verify the CPU utilization and memory consumption data details. Details can be expanded by dragging the mouse pointer to respective timeline.
5. Please use the Reset Zoom option to remove zoom feature from the Graph.

Notes

1. Unica Director %CPU Graph can display beyond 100% utilization. The calculation is

   %CPU = (Total Threads on all CPUs / Logical CPU cores) * 100

   For example, if there are 2 physical CPU each with 2 cores for a total of total 4 core CPU on system and if each core has 2 threads, there are 4*2=8 logical CPU cores. If the CPU is fully utilized on the engine, then Unica Director will show utilization of 8*100 = 800%

2. CPU Utilization and Memory Consumption Graph does not auto refresh. To refresh, click any of the time slots from 1 hour to 7 days.
3. System Usage page does not show generic message on the page after deselecting both memory utilization and CPU consumption options.

Managing Engine as Service through HCL Unica Director:

1. Adding, updating or deleting a engine will not be reflected automatically in environment details in Unica Director. You must delete the current environment from the Environment menu option and add it back so that the latest Engine will be monitored by Unica Director

Journey Data Source

All the data sources from the selected environment are listed

The connectivity of all data sources configured in Platform from all the Journey Analytical server are tested and displayed Connection failures should be reflected in the logs. You can get the status of your data sources. Start / stop actions are not supported for data sources. All data sources are supported in this connectivity check.

The following columns are listed on the screen:

1. Data Source Name
2. Type: This is typically the data source template type such as Oracle, MariaDB, OneDB, SQL Server
3. DSN name: Name of the DSN from the data source
4. JNDI: JNDI name

Application Deployments

The Webservers screen provides status of all the webapp servers being monitored and allows you to start and stop the Application.

Start/Stop status of the application server will be reflected in Job Queue page.

1. Server Host - Host name of the machine running the application Server.
2. Type - Displays the type of the application server (Websphere/Tomcat/JBOSS).
3. Application Name - Displays the Node Name of application server – this column displays only the value for Application Server.
4. Application Deployment Port details:
   • Node Name – Displays WebSphere application server nodename. e.g. zebra658Node01. Applicable to WebSphere only
   • JMX Port – Displays JMX port for Tomcat. Applicable for Tomcat only
   • Admin Port – Displays Management HTTP/console port for JBoss. Applicable for JBoss only
5. Actions : Start / Stop / Get Application Status
   1. Start and Stop action are updated in Job Queue
   2. Get Application Status updates the status icon with time stamp

Stop/Start operations on WAS, Tomcat and JBoss

• Start/Stop operation of JOurney applicaton is supported from Director for webservers - Tomcat , JBoss, Websphere.

Start operation on Websphere

• If Journey has already started via the webserver Console, starting it again from Unica Director will not change the status icon to ‘Running’ for Websphere.

Supported Application Servers:

• IBM Websphere Application Server - Standalone
• Tomcat - standalone
• JBOSS - standalone deployment

1. On clicking any of the action buttons (start / stop / get Status), you are prompted with a popup to enter your login credentials (userid / password) of the application server profile. On a successful login the respective actions will be carried out.
2. Application Server status is not reflected for the first time when the application server node is added in the environment. Click on Get Status icon to get the latest status of Journey Application.
3. Getting the status and Start/stop actions can only be performed on Journey application deployments. These cannot be performed on the application server profile.
4. Add the following JMX parameter for TOMCAT in the tomcat setenv script:

For Tomcat add the following entry in the setenv script:

– CATALINA_OPTS=-Dcom.sun.management.jmxremote

-Dcom.sun.management.jmxremote.port=5621

-Dcom.sun.management.jmxremote.ssl=false

-Dcom.sun.management.jmxremote.authenticate=true

-Dcom.sun.management.jmxremote.password.file=../conf/

jmxremote.password -Dcom.sun.management.jmxremote.access.file=../conf/jmxremote.access

1. jmxremote.password: It should provide the username and password for the tomcat user, this file allows access to only the user that runs the Director agent and restricts access to all other users
2. jmxremote.access: It should provide the access roles for the tomcat users. Standard users should be provided with access required to get statuses - like readonly and readwrite

Technical details:

1. For WebSphere application server we are using wsadmin tool to get the status of the application server node.
2. For TOMCAT, we are using JMX to connect to the application server.
3. For JBOSS we are using JBOSS CLI to get the application status and start / stop actions.

-Dweblogic.security.SSL.ignoreHostnameVerification=true

-DwebLogic.nodemanager.sslHostNameVerificationEnabled=false