Reviewing System Information

Use the System Troubleshooting page (Operations > System > Troubleshooter) to review system information and troubleshoot system issues in Sterling B2B Integrator.

From the System Troubleshooting page, you can perform the following tasks:

View system information on different nodes from any node in a clustered environment.
Refresh system status.
Stop Sterling B2B Integrator.
View database usage statistics.
Note: If IBM® DB2® is your database, the database usage statistics are always displayed as unavailable in the System Troubleshooting page.
View business process queue and usage statistics.
Terminate a business process.
View system classpath information.
View system JNDI tree information.
View environment statistics, including cache and memory used.
View adapter information.
View perimeter server information.
View when the archive, index, and purge tasks were completed.

The System Troubleshooting page provides quick access to system information. It provides links to key areas of system information instead of loading all of the system information at once. The system information for each area will be displayed in a pop-up window, which reduces the loading time of the System Troubleshooting page.

The following table provides a general description of each area. The subsequent sections provide further details about each area.

Area	Information
Stop the System	Stops the whole Sterling B2B Integrator cluster using the softstop script. After that, you still need to call the hardstop script to stop the whole system. Compare with the Soft Stop command.
Select Node	The Select Node list is displayed only if you are working in a clustered environment. Your selection determines which node's information is displayed in the rest of the System Troubleshooting page. The select node list enables you to select a node in a clustered environment, which in turn decides the node whose information is to be displayed in the System Troubleshooting page. For example, if you have two nodes in a cluster (Node 1 and Node 2) and you want to view the System Troubleshooting page for Node 2, select Node 2 from the list and the System Troubleshooting page for Node 2 displays. If you want to view Node 1 information, select Node 1 from the list and the System Troubleshooting information for Node 1 displays.
Host Information	The Host Information displays the following information: Start time Uptime Host Location State Memory available Active threads
Sterling Gentran:Server®	This area is displayed only if you have configured your system for Sterling Gentran:Server Data Manager support. The Sterling Gentran:Server area displays the following information: Host Location State Controllers Adapters
Classpath	Displays the Sterling B2B Integrator classpath.
JNDI Tree	Displays the JNDI tree in Sterling B2B Integrator.
Soft Stop	Stops a node of Sterling B2B Integrator using the softstop script interactively through the UI. Compare with the Stop the System command.
Database Usage	Displays the database space usage, database services (business process eligibility for archive, index, and purge), and environment pool usage. Note: For Oracle, the database usage indicator calculates free space used based on Oracle extents. The name of this area changes along with the database that you are running. For example, oraclePool is for an Oracle database.
Business Process Queue Usage	Displays business process queue usage statistics such as cache disk usage, cache memory usage, queue statistics, and cache statistics.
Business Process Usage	Displays count of business processes by its state.
Cache Usage	Displays size and hit rate for object caches.
Threads	Displays active processes at a thread level.
Clean-Up Processes Monitor	Displays the time since the archive, index, purge, and recovery tasks were completed.
Controllers	The state and name of each controller or server in the Sterling B2B Integrator installation.
Adapters	Displays list of all the adapters in the system and their status. Note: Click an adapter name to view details about its status in the Service Settings page.
Perimeter Server Status	The information in this area is displayed only after you have added a perimeter server to Sterling B2B Integrator. The Perimeter Servers area displays the following information: Cluster node name (in a clustered environment only) Whether the perimeter server is on or off State, either enabled or disabled Name of the perimeter server Last activity

Stopping Sterling B2B Integrator from the System Troubleshooting Page

You can stop Sterling B2B Integrator using the System Troubleshooting page, using either a soft stop (which allows all the business processes to complete) or a hard stop (which stops the system and all the processing immediately). After a soft stop, you must still perform a hard stop to stop the system. For more information about the soft stop process, refer to Soft Stop of Sterling B2B Integrator.

Important: Using the Soft Stop option stops only the Sterling B2B Integrator interface immediately, while all the business processes that are in progress run until complete. After all the current business processes are completed, you will need to perform a hard stop to fully stop Sterling B2B Integrator. To stop the system and all the processing immediately, use the Stop the System option. All processes that have not been completed will stop and have to be restarted.

To stop Sterling B2B Integrator using the System Troubleshooting page:

From the Administration menu, select Operations > System > Troubleshooter.
In the System Troubleshooting page, in the System Status area, click Soft Stop (for an interactive soft stop) or Stop the System (for an immediate soft stop).

Important: A soft stop does not stop all JVMs and system processing. To fully stop the system, you must perform a hard stop after the soft stop is complete. For instructions, see Hard Stop of Sterling B2B Integrator.

Viewing the Host Information

Host Information displays the current operational status of the processing environment for your installation of Sterling B2B Integrator. The System Troubleshooting page displays separate information for each installation.

Note: If you are working in a clustered installation of Sterling B2B Integrator, the information that displays is determined by the node you select from the Select Node list.

To view Host Information:

From the Administration menu, select Operations > System > Troubleshooter.
In the System Troubleshooting page, click Host Information.

The following information is provided for each installation:

The cluster node name, if you are working in a clustered installation of Sterling B2B Integrator.
Note: The cluster node list displays only if you are working in a cluster. After you set up your cluster, the select cluster node list displays.
Host - The name of the host on which a specific installation resides.
Location - The location or path of the installation.
State - The running state of the installation, either Active (available for processing) or Inactive.
Memory in use - The amount of memory used by Sterling B2B Integrator.
Active threads - The number of concurrent threads that are active.

Viewing the System Classpath

You can view the system classpath for debugging purposes and to verify whether third-party libraries are available in the classpath.

To view the system classpath:

From the Administration menu, select Operations > System > Troubleshooter.
In the System Troubleshooting page, in the System Status area, click Classpath.
Information about the System Class Path and the Dynamic Class Loader is displayed.

Viewing the System JNDI Tree

You can view the system JNDI tree for debugging purposes and to verify whether the expected resources, for example, adapters or pool names, are in the JNDI tree.

To view the system JNDI tree:

From the Administration menu, select Operations > System > Troubleshooter.
In the System Troubleshooting page, in the System Status area, click JNDI Tree.
The system JNDI tree displays the JNDI name and class name pairs.

Viewing a Node JNDI Tree in a Clustered Environment

You can view a specific node's JNDI tree for debugging purposes and to verify whether the expected resources, for example, adapters or pool names, are in the JNDI tree. This option is available only in a clustered environment.

To view a node's JNDI tree in a clustered environment:

From the Administration menu, select Operations > System > Troubleshooter.
In the System Troubleshooting page, in the System Status area, click node#, where # is the number of the node you want to view information about.
The node's JNDI tree displays JNDI name, class name pairs, and the node name.

Viewing the Database Usage Statistics

Database usage statistics show how your database is performing, including database insert information, database capacity, and environment pool usage. Sterling B2B Integrator uses pools to store database connections. To change pool settings, you must manually edit the configuration files and restart the system.

Note: Database usage statistics are not available for DB2.

To view database usage statistics:

From the Administration menu, select Operations > System > Troubleshooter.
In the System Troubleshooting page, in the System Status area, click Database Usage.
Note: If you have the displayGraphics property, which is located in the install_dir/properties/ui.properties file, set to true, the Database Usage page is displayed in graphic format. Otherwise, the Database Usage page is displayed in text format. The default is true for Linux®, Sun™, HP, and Microsoft Windows® operating systems. The default is false for IBM AIX® operating system.

The Database Usage report is displayed with the following information for each unit test of the database:
- Average time taken to perform a given number of database inserts in a unit test
- Number of inserts performed to the database in a unit test
  Note: You can change the value of the dbAccessLoopCnt property in the install_dir/properties/ui.properties.in file. After making the changes, in the install_dir/bin directory, run the setupfiles script.
- Size of the inserts performed to the database in the unit test.
  Note: You can change the value of the dbAccessDataSize property in the install_dir/properties/ui.properties.in file. After making the changes, in the install_dir/bin directory, run the setupfiles script.
- Size of the database and the amount of the database used (in megabytes):
  - Green – Normal range
  - Yellow – Warning range
  - Red – Critical range
- Number of business processes that are waiting to be archived, indexed, or purged
- Size (in megabytes) of the following pools and the number of requests that had to wait for the following pools:
  - gentranTPPool
  - databaseArchivePool
  - databasePool
  - databasePool_local
  - databasePool_NoTrans
  - databasePool_Select
  - databaseUIPool
    Note: The database part of the pool names changes depending on the database you are using, for example, if the database is Oracle, you will see oraclePool.

Viewing the Business Process Queue Usage

The Business Process Queue Usage page enables you to diagnose problems with your business process queues.

To view Business Process Queue Usage:

From the Administration menu, select Operations > System > Troubleshooter.
In the System Troubleshooting page, click Business Process Usage.
The page provides the following queue information:
- The amount of memory available for cache and the amount consumed.
- The amount of disk space available for cache and the amount consumed.
- The average wait time based on priority.
- The average business process execution cycle time based on priority. The average business process execution cycle time may include the execution times of several steps. It captures the average time that business processes are active on threads before being rescheduled.
- The number of business processes in priority queues.
- The number of business processes that ran without being cached and the number that are currently in cache. Cache location is also specified so that you can determine the number of business processes that were found in the soft reference cache, in the disk cache, and in the memory cache.
- Number of business processes within the data size ranges that have been processed.

Viewing the Business Process Usage

The Business Process Usage page enables you to review the state of a business process and the process count. If a link is enabled in the Process Count area, you can select it to view affected business processes and manage them.

To view Business Process Usage:

From the Administration menu, select Operations > System > Troubleshooter.
In the System Troubleshooting page, click Business Process Usage.
The page provides the information about the following business process states and the process count:
- ASYNC_QUEUED
- Active
- Halted
- Halting
- Waiting
- Waiting_On_IO
- Interrupted_Man
- Interrupted_Auto

Viewing Cache Usage Information

Sterling B2B Integrator uses caches to hold information that is frequently requested by the system. For each cache, the Cache Usage report displays statistics pertaining to the count, number of requests, and number of successful hits. To change cache settings, refer to the information provided in Performance Tuning Utility. You can view the cache usage information to monitor the use of various cache types.

To view cache usage:

From the Administration menu, select Operations > System > Troubleshooter.
In the Application Status area of the System Troubleshooting page, click Cache Usage.
The Cache Usage report displays the following information for each cache type:
- Cache name – Name of the cache
- Count – Number of objects in the cache
- Requests – Number of times an object was requested from the cache, irrespective of whether it was found or not.
- Hits – Number of times an object was requested from the cache, and was found successfully.

Viewing Threads

The Threads pop-up window displays active processes at a thread level.

To view threads in Sterling B2B Integrator:

From the Administration menu, select Operations > System > Troubleshooter.
In the Application Status area of the System Troubleshooting page, click Threads.
The Threads report is displayed.

Viewing the Clean-Up Processes Monitor Details

You can view details about the time that has lapsed since the completion of different cleanup processes, including archiving, purging, and indexing. This helps you view, at a single location, information about whether these processes are running and completing.

To view the Clean-Up Process Monitor details:

From the Administration menu, select Operations > System > Troubleshooter.
In the System Troubleshooting page, in the System Status area, click Clean-Up Processes Monitor.
The Clean-Up Processes Monitor Details window displays the status, workflow (or cleanup process) name, the date and time at which the workflow was last run, and the workflow ID.
The Status column has the following values:
- Red – More than four times the scheduled interval has elapsed without a successful launch by the scheduler.
- Yellow – More than three times the scheduled interval has elapsed without a successful launch by the scheduler.
- Green – Less than three times the scheduled interval has elapsed since a successful launch by the scheduler.
- Gray – Either the process has never completed any scheduled instance or has never been scheduled.
Note: Red or Yellow status may mean that the process is not able to complete the data cleanup tasks. If this condition continues even after you have taken steps to resolve the errors, contact IBM Customer Support.

Refreshing a Controller

You can refresh the controllers that are running in your environment using the System Troubleshooting page.

To refresh a controller:

From the Administration menu, select Operations > System > Troubleshooter.
In the System Troubleshooting page, click Controllers. The Controllers pop-up windows appears and displays the state of the controller and name of the controller.
Click Refresh icons (arrows) next to the Controller you want to refresh.

The controller is refreshed.

Viewing Adapter Information

You can view the adapters by its state that are currently active or stopped, to verify accuracy or to plan changes as needed.

To view adapter settings:

From the Administration menu, select Operations > System > Troubleshooter.
In the Troubleshooting page, click Adapters.
In the Adapters page, click the name of the adapter that you want to view.

Enabling an Adapter

You can enable a disabled adapter using the System Troubleshooting page.

To enable an adapter:

From the Administration menu, select Operations > System > Troubleshooter.
In the Troubleshooting page, click Adapters.
In the Adapters page, next to the adapter that you want to enable, in the On/Off column, select the check box.

Disabling an Adapter

You can disable an enabled adapter using the System Troubleshooting page.

To disable an adapter:

From the Administration menu, select Operations > System > Troubleshooter.
In the Troubleshooting page, click Adapters.
In the Adapters page, next to the adapter that you want to disable, in the On/Off column, select the check box.

Viewing the Perimeter Server Status

The Perimeter Servers area of the System Troubleshooting page displays the following information about each of your perimeter servers:

Name of the cluster node with which the perimeter server is associated
State of the perimeter server, Enabled or Disabled
Name of the perimeter server
Date and time of the last activity the perimeter server performed

Notes:

If you are working in a clustered environment, the information that is displayed is determined by the node you select from the Select Node list.
If you are not using a perimeter server, the perimeter server name is displayed as local, and the server state is Enabled.

Enabling a Perimeter Server

You can enable a disabled perimeter server using the System Troubleshooting page.

To enable a perimeter server:

From the Administration menu, select Operations > System > Troubleshooter.
In the Perimeter Servers area of the System Troubleshooting page, under the On/Off column, select the check box adjacent to the perimeter server you wan to enable.

Disabling a Perimeter Server

You can disable an enabled perimeter server using the System Troubleshooting page.

To disable a perimeter server:

From the Administration menu, select Operations > System > Troubleshooter.
In the Perimeter Servers area of the System Troubleshooting page, under the On/Off column, select the check box adjacent to the perimeter server you want to disable.