This document describes information and tracing screens in the IS Administration Console. It covers services and screens on the following information types:
This screen shows the current level of EntireX Tracing. You can change this level with the Change Settings link. The trace levels are "0" (no tracing), "1" (trace calls), "2" (trace calls and buffers), "3" (full tracing).
The trace file is written to the standard log directory of the Integration Server or the directory defined in Change Settings and has the name wmentirexYYYYMMDD.log.
You can change the location (directory) for the trace files with the Change Settings link. This has immediate effect.
The adapter uses the logging facility of the Integration Server. The facility code is "0800" for the EntireX Adapter. The logging level specifies the amount of data logged. These log entries are written to the server log file.
This screen displays the following sections about connections and listeners.
Broker Information
The status of all brokers used in the connections. A green dot shows
that a connection to the broker is successful. As status, the version and the
operating system platform is displayed. A red dot shows that a connection to
the broker is not possible. As status, the error message is displayed.
Connections for Services
The status of the external servers such as RPC Server, IMS Connect and
CICS ECI used by the connections for adapter services. A green dot shows that
connection to the RPC server is successful and the status information from the
server is displayed. A red dot shows that a connection to the RPC server or to
the Broker is not possible. As status, the error message is displayed. The
current number of connection instances is shown in column
Count.
Connections for Listeners
For each Listener the corresponding name of the connection, Broker ID,
and server address is displayed.
The information on connections and listeners shown on the IS Administration Console's page is available with built-in services. The following services are available in the WmEntireX package:
The service retrieves the status of the broker given in the broker ID.
Use pub.wmentirex.connectioninfo:brokerList before to get the list
of broker IDs used in all connections.
brokerID
String |
The ID of the broker to be pinged.
|
|---|---|
refreshData String
|
The number of milliseconds to refresh the data. If
refreshData is null or not a number, the default of 10 seconds is
used.
|
errorFlag String
|
"true" if an error occurred, "false" if the call succeeded. |
|---|---|
message String
|
The result of the ping call to the broker. |
The service retrieves the list of all broker IDs configured in the connections.
refreshData
String |
The number of milliseconds to refresh the data. If
refreshData is null or not a number, the default of 10 seconds is
used.
|
|---|
brokerIDs String[]
|
The array of broker IDs. |
|---|
The service retrieves name, broker ID and server address for each listener.
refreshData String
|
The number of milliseconds to refresh the data. If
refreshData is null or not a number, the default of 10 seconds is
used.
|
|---|
listeners IData[]
|
The array of IData objects containing three strings name, brokerID, serverAddress for each listener. |
|---|
The service retrieves the result of the ping call for the connection.
connection String
|
The name of the connection to ping, e.g.
"folder:name".
|
|---|---|
refreshData String
|
The number of milliseconds to refresh the data. If
refreshData is null or not a number, the default of 10 seconds is
used.
|
errorFlag
String |
"true" if an error occurred, "false" if the call succeeded. |
|---|---|
message String
|
The result of the ping call to the connection. |
The service retrieves the connection names. One of these names can be
used as input for pub.wmentirex.connectioninfo:serviceInfo.
refreshData String
|
The number of milliseconds to refresh the data. If
refreshData is null or not a number, the default of 10 seconds is
used.
|
|---|
connections String[]
|
The array of connection names in the format
folder:connection.
|
|---|
Connections, adapter services and adapter listeners contain metadata
which is generated during deployment of connections and services. Use the
service pub.wmentirex.supportinfo:createInfo to extract this
metadata for support purposes and error diagnosis.
The service extracts the generated metadata from all connections and adapter services in a package and writes this to a file in the installation folder of the Integration Server.
packageName String
|
The name of a package. The generated metadata for all connections, adapter services and adapter listeners in this package is written to a file. |
|---|
result String
|
File <filename> created on host <hostname> |
|---|
This screen shows statistics about the adapter services of the EntireX Adapter. Only services that have been executed at least once during the runtime of the Integration Server are shown.
The following information is shown for each service:
name of the service
corresponding program name
number of successful calls
number of erroneous calls
average processing time in milliseconds (only successful calls)
time of last access
processing time in milliseconds for the last call
status of last call (detailed error message if the last call failed)
Note:
All these items except the service name can be reset with the link
"Reset Statistics".
This screen shows information on the license used to enable the usage of Direct RPC, or connections using IMS Connect or CICS ECI connectivity.
License File Location: name-of-licence-file. If the file is not found, the location where the file is expected is shown.
Valid until: values are a date specification or "Unlimited"
License for connections to IMS Connect: "Yes" or "No"
License for connections to CICS ECI: "Yes" or "No"
License for Direct RPC: "Yes" or "No"
Error message (only if the license is not granted)
Notes:
Application Monitoring is an EntireX feature that enables you to monitor the response times in your distributed applications, and it also enables you to monitor certain error situations. For details, see Application Monitoring in the EntireX documentation.
To enable application monitoring for Direct RPC, IMS Connect and CICS
ECI
In the administration menu of the EntireX Adapter, choose Application Monitoring.
In the Configuration section, enable Application Monitoring.
In the configuration entry Application Monitoring Data Collector ID, enter the address of the Application Monitoring Data Collector.
The address has the format host-name:port-number, where host-name is the host on which the Application Monitoring Data Collector is running and port-number is the port number of the Application Monitoring Data Collector. The default port number is 57900.
Caution:
If you have a Direct RPC scenario and you change the
application monitoring configuration, all involved client applications and/or
RPC servers have to be restarted (because they are caching information about
the Adapter’s application monitoring settings).
