Using the Integration Network

This chapter discusses how to:

Click to jump to parent topicUnderstanding the Integration Network

The integration network centralizes the administrative tasks of configuring, administering, and monitoring integrations in PeopleSoft Integration Broker. The network is delivered as a WorkCenter.

The integration network provides configuration and node status pages that allow you to quickly assess if the integration network is properly configured, as well as identify the nodes that are in the network and their configuration status. The integration network enables you to activate and deploy groups of integrations, assess the security permission status of service operations, and more. The integration network also provides the ability to monitor integration activity in the network by node or by transaction.

Important! Only nodes defined as PeopleSoft nodes (PIA node type) can participate in the integration network.

Click to jump to parent topicCommon Elements Used in the Integration Network

Hover over the Help icon to display information about the function of a configuration option.

Click to jump to parent topicAccessing the Integration Network

This section discusses how to:

Click to jump to top of pageClick to jump to parent topicUnderstanding Accessing the Integration Network

You can access integration network features using the Integration Network WorkCenter or in the Integration Network folder, both of which are located in the PeopleSoft Pure Internet Architecture.

Note. Procedures for accessing and using the integration network are documented in this chapter using the Integration Network WorkCenter

Click to jump to top of pageClick to jump to parent topicAccessing the Integration Network Using the Integration Network WorkCenter

The default location of the Integration Network WorkCenter is in the Integration Broker folder in the PeopleSoft Pure Internet Architecture. To access the Integration Network WorkCenter , select PeopleTools, Integration Broker, Integration Network WorkCenter. The following example show the Integration Network WorkCenter:

When you access the Integration Network WorkCenter, the Network Status page appears in the main work area.

The left navigation pane of the Integration Network WorkCenter provides links to the integration network features and pages. When you select a link from the left navigation pane, the corresponding page appears in the main work area.

Information for working with and customizing WorkCenters is provided elsewhere in PeopleBooks.

See PeopleTools 8.52: Using PeopleSoft Applications PeopleBook

Click to jump to top of pageClick to jump to parent topicAccessing the Integration Network Using the Integration Network Folder

You can access integration network features in the Integration Network folder in the PeopleSoft Pure Internet Architecture. To access the folder, select PeopleTools, Integration Broker, Integration Network. The Integration Network folder opens and links to integration network features appear, as shown in the following example:

Click to jump to parent topicConfiguring the Integration Network

This section discusses how to:

Click to jump to top of pageClick to jump to parent topicUnderstanding Configuring the Integration Network

The integration network is properly configured when the integration gateway is configured, when the default local node is configured, local and remote nodes are configured, and when the application server domain is active. The Integration Network folder features a Configuration Status page that enables you to quickly assess if the integration network is configured. The page also provides access to the PeopleSoft Integration Broker components used to perform configuration tasks if you want to view or modify settings.

Click to jump to top of pageClick to jump to parent topicUnderstanding Minimum Configuration Requirements for the Integration Network

The Configuration Status page indicates if the integration network is minimally configured to run. The following table lists the minimum configuration requirements for the network.

Note. All nodes to be managed and monitored in the Integration Network must be PeopleSoft nodes. PeopleSoft nodes are those nodes defined as PIA node types in the node definition.

Integration WorkCenter Navigation

Page and Object ID

Required Configuration

Alternate Integration Broker Navigation

Gateway Configured

  • Update Gateway Location

  • Register Target Connectors

Gateways – Gateways page

IB_GATEWAY

  • Define a local gateway. This gateway represents the source system.

    • In the definition you must specify a gateway URL and specify that the gateway is local.

    • Load the target connectors.

  • Define one or more remote gateways. These gateways represent the target systems.

    • In each remote gateway definition you must specify the URL of the remote gateway.

    • Load the target connector for each gateway.

PeopleTools, Integration Broker, Configuration, Gateways

Gateway Configured, Update Configuration Settings

Gateways – PeopleSoft Node Configuration page

(PSGTWPROPS_SEC)

Register and configure PeopleSoft nodes on the local gateway.

You must first create local and remote node definitions before you can register and configured them on the local gateway.

PeopleTools, Integration Broker, Configuration, Gateways, Gateway Setup Properties

Node Network Configured

Gateway Properties page

(BGWPROPERTIESPAGE)

In the Integration Gateway CERTIFICATE Section of the integration gateway properties file for each gateway defined, specify the secure keystore path and password.

PeopleTools, Integration Broker, Configuration, Gateways, Gateway Setup Properties, Advanced Properties Page

Node Network Configured

Nodes – Node Definitions

(IB_NODE)

Default Local Node:

  • Rename or define the local default node. This node represents the source system.

  • Activate the default local node.

Remote Nodes:

  • Define remote nodes as warranted. The remote nodes represent target systems.

  • Activate the nodes.

  • Assign the nodes to a gateway.

After you create local and remote node definitions, you must register and configure them on the gateway using the PeopleSoft Node Configuration page.

PeopleTools, Integration Broker, Integration Setup, Nodes, Node Definitions

Node Network Configured

Nodes-Connectors page

(IB_NODECONN)

Assign the default local node and any other local nodes to a gateway and target connector.

PeopleTools, Integration Broker, Integration Setup, Nodes, Connectors

Domain Active

Domain Status

(AMM_MULTIDOM)

Activate the application server domain.

PeopleTools, Integration Broker, Service Operations Monitor, Administration, Domain Status

Click to jump to top of pageClick to jump to parent topicUsing the Configuration Status Page

The Configuration Status page indicates if the integration network is minimally configured to run as described in the previous section.

The page provides visual cues that enable you to quickly asses if the integration network is properly configured. Integration components that are properly configured display on the page with a green check mark icon next to them; components that are not configured, are not configured properly, or that require additional configuration display on the page with a red “X” icon next to them.

To access the Configuration Status page, select PeopleTools, Integration Broker, Integration Network WorkCenter and click Configuration Status. The following example show the Configuration Status page:

In the previous example, green check mark icons appear next to the Gateway Configured and Node Network Configured links and indicate that each of these integration components are properly configured. A red “X” icon appears next to the Activate Domain link, and indicates that the domain is not active.

The following page elements appear on the Configuration Status page:

A green check mark icon appears next to an integration network component to indicate that the component is properly configured.

A red “X” icon appears next to an integration network component to indicate that the component is not configured, requires additional configuration, or is not properly configured.

Gateway Configured

Click the link to access the Gateways component to view the gateway configuration or to configure the gateway.

For the integration network to be properly configured, the integration gateway must be configured.

Node Network Configured

Click the link to access the Node Network page and view, configure and manage PeopleSoft nodes in the integration network.

For the integration network to be properly configured, the node network must be configured.

Domain Active

Click the link to access the Domain Status page in the Service Operations Monitor to activate an application server domain.

For the integration network to be properly configured, the application server domain must be active.

Service Configuration

(Optional.) Click the link to access the Service Configuration page where you specify services settings, such as the service namespace, the schema namespace, the target location, and so on.

Monitor Setup Options

(Optional.) Click the link to access the Monitor Setup Options page to set display and other options in the Service Operations Monitor. For example, use the page to verify or set the proper size limit (Data Length View Limit) for displaying XML in the Service Operations Monitor for asynchronous transactions, enable gateway logging, and more.

System Setup Options

(Optional.) Click the link to access the System Setup Options page to set the recursion level (Message Builder Depth Limit) for message parts, enabling runtime profiling to generate system performance statistics, and more.

Click to jump to top of pageClick to jump to parent topicVerifying and Managing Integration Gateway Configuration

At a minimum the following setting and options must be configured on the integration gateway for the integration network to function properly:

The Configuration Status page features a Gateway Configured link. When you click the link the Gateways component appears and you can view and configure integration gateway settings and options. You can also use the Gateway link in the Integration Network WorkCenter navigation pane to access the Gateways page and the features described in this section.

The following example shows the Gateways page when no integration gateway has yet been defined:

The following table provides links to PeopleBooks documentation that describes how to perform the minimum tasks required to configure the integration network:

Action

Documentation

Comments

Define local and remote gateways.

See Defining Integration Gateways.

NA

Load target connectors for each gateway.

See Loading Connectors by Introspection.

NA

Define jolt connection strings for each node

See Default Oracle Jolt Connect String Properties.

You must create the node definitions before you can register and configure them on integration gateways.

Click to jump to top of pageClick to jump to parent topicViewing Node Network Status

The Configuration Status page features a Node Network Configured link that opens a Node Network page. Use the Node Network page (IB_INTNETWORK) to view and configure details about PeopleSoft nodes in the integration network. The Node Network page provides a view of all the PeopleSoft nodes in the database.

Note. Only PeopleSoft nodes can be viewed and managed in the integration network pages. A PeopleSoft node is one defined as a PIA node type on the Nodes-Node Definition page.

The following example shows the Node Network page:

The Node Network page allows you to easily identify the current default local node, nodes that are defined in the integration network, active nodes, and so on.

The following page elements appear on the Node Network page:

Secure Keystore Value Defined

This page element is read-only.

A check mark in the box denotes that the secure keystore path and password has been defined in the integration properties file for the default local gateway.

The Node Network component is not set to Configured until the box is checked; The box displays checked after you define the keystore path and password in the integrationGateway.properties file.

Warning! Integrations will fail if you do not set the secure keystore path and password.

See Setting SSL/TLS Encryption Security Properties.

Default Local Node

This page element is read-only.

A check mark in this column denotes the default local node in the system.

There can be only one default local node in the PeopleSoft database.

Additional information about the default local node is provided elsewhere in this chapter and in PeopleBooks.

See Adding and Modifying Nodes in the PeopleSoft Database, Default Local Node.

Node

The node column lists the PeopleSoft nodes in the database. Only nodes defined as PeopleSoft nodes appear on the page. PeopleSoft nodes are those defined as PIA node types in the node definition.

Information about adding and modifying node definitions is provided elsewhere in this chapter and in PeopleBooks.

See Adding and Modifying Nodes in the PeopleSoft Database, Default Local Node.

In Network

A check mark in this column denotes that the node is defined as part of integration network.

Important! A node must be “in network” for you to be able view integration information and use the features of the integration network on the node.

The default local node is automatically defined in the network.

To include a node in the integration network, check the box. To remove a node from the integration network, clear the box.

The In Network box is enabled only when the node is active and you have defined jolt connection strings for the node in the integration gateway.

Additional information about adding nodes to the integration network is provided elsewhere in this chapter.

See Adding Nodes to the Network.

Configured in Gateway

This page element is read-only.

A check mark in this column denotes that the jolt connection strings for the node have been defined in the integration gateway.

Defining jolt connection strings for nodes is described elsewhere PeopleBooks.

See Setting Oracle Jolt Connection Properties.

Active Node

This page element is read-only.

A check mark in this column denotes that the node had been defined as an active node in the node definition.

To change the active status of a node, click the node name in the grid to access the node definition.

Information about activating a node is described elsewhere in PeopleBooks.

See Defining Node Parameters.

Remote Gateway Node

This page element is read-only.

A check mark in this column denotes that the node is defined on a remote gateway.

If the node is defined using a remote gateway, the defined gateway will not be checked to determine if the node information is configured in that remote gateway.

Click to jump to top of pageClick to jump to parent topicAdding and Modifying Nodes in the PeopleSoft Database

You can click the name of any node in the Node Network list to open the node definition in the Node Definition page and view or modify the node definition.

The following table lists the actions you must take to properly configure a node for the node network. The table also provides links to the corresponding PeopleBooks documentation that describes how to perform the actions:

Action

Documentation

Comments

  • Define the default local node.

  • Define a remote node for each additional system participating in integrations.

See Default Local Node, Local and Remote Nodes, Prerequisites for Adding and Configuring Nodes, Adding Node Definitions, Configuring Nodes, Specifying Gateways and Connectors.

  • You can rename the delivered default local node or define a new one.

  • For each node use the Nodes-Node Definition page to verify the following:

    • The node is defined as a PIA node type.

    • The node is set to Active.

  • For each node use the Nodes-Connectors page to assign the node to an integration gateway and target connector.

Click to jump to top of pageClick to jump to parent topicAdding Nodes to the Network

A check mark in the In Network column on the Node Network page indicates that the node is defined as part of the integration network. A node must be in network for you to be able view integration information and use the features of the integration network on the node.

The default local node is automatically defined in the network.

The In Network box for a node is enabled for selection or available to clear only when:

Click to jump to top of pageClick to jump to parent topicVerifying Publication/Subscription Server Domain Status

For the integration network to be properly configured the pub/sub server domain must be set to Active.

When the No Domain Active link appears on the Configuration Status page, the pub/sub server domain is not set to Active. Click the link to access the Domain Status page in the Service Operations Monitor and to activate the domain status.

See Activating Pub/Sub Server Domains.

Click to jump to parent topicVerifying Integration Network Status

This section discusses how to:

Click to jump to top of pageClick to jump to parent topicUnderstanding Verifying Integration Network Status

The Integration Network provides a Network Status page that enables you to verify integration network connectivity with PeopleSoft integration partners and to verify the status of integrations between those partners.

Click to jump to top of pageClick to jump to parent topicPrerequisites for Verifying Integration Network Status

Before you can verify integration network connectivity and status with remote PeopleSoft nodes in the integration network:

Click to jump to top of pageClick to jump to parent topicNavigating the Network Status Page

The Integration Network features a Network Status page (IB_VERIFYNETRS) that enables you to verify proper connectivity and status of all integrations between the default local node and remote nodes in the integration network.

To access the Network Status page, select PeopleTools, Integration Broker, Integration Network WorkCenter, Administration, Network Status. The following example shows the page:

The page features the following fields and control:

Configuration Status

Displays the configuration status of the network. The valid values are:

  • Configured.

    This value appears when the integration network is properly configured.

  • Configuration Required.

    This value appears as a link when the network is not configured, requires additional configuration, or is not properly configured.

    Click the link to access the Configuration Status page to identify and resolve any configuration issues. Verifying configuration status and using the Configuration Status page is described elsewhere in this chapter.

    See Using the Configuration Status Page.

Network Integration Status

Use this page control to verify the status of integrations with remote nodes in the integration network.

Network Monitor Setup

Click the link to access the Network Monitor Setup page where you can modify the time range the system uses for verifying the network status.

Time Range

Indicates the time range the system uses for reporting on the network status. Use the Network Monitor Setup link to modify this value.

Ping Status

Use this page control to verify the proper connectivity with remote nodes in the integration network.

Select

Check the box next to each node to include in network status and connectivity checks. Clear the box next to each node to exclude in the checks.

Node

Displays the name of the node.

Results

Area where a description of the results of the network status check and network ping appear.

Details

If additional details of the network status and network ping results are available, a Details link appears. Click the link to view the additional information.

Click to jump to top of pageClick to jump to parent topicVerifying Network Connectivity with Integration Partners

Use the Ping Status control on the Network Status page to verify connectivity with remote PeopleSoft nodes in the integration network.

A successful ping indicates that you have correctly defined the selected remote PeopleSoft nodes in the Integration Network and that the local system can connect to them. A successful ping also indicates that the PeopleSoft integration partners represented by the remote nodes have correctly defined your node as part of their integration network and they should be able to perform a successful integration network ping to your system as well.

The following table lists the possible results from performing a ping on an integration network nodes:

The action was successful. The local node and remote PeopleSoft node successfully connect to each other in the integration network.

The local node cannot connect to the remote PeopleSoft node.

To verify integration network connectivity with integration partners:

  1. Access the Network Status page. (Select PeopleTools, Integration Broker, Integration Network WorkCenter.)

  2. Click the Ping Status button.

The system displays the outcome of the ping in the Results column in the Network Node Status grid.

Click to jump to top of pageClick to jump to parent topicVerifying Integration Status with Integration Partners

The Network Integration Status control on the Network Status page enables you to verify integration network connectivity between the default local node and the selected remote PeopleSoft node as well as verify that integrations between the two systems are being processed.

The following table lists the possible results from performing an integration network status check:

The results grid displays a green check mark to indicate successful status of all integrations between the default local node and the indicated remote node.

The results grid displays a yellow triangle to indicate successful connectivity to the indicated remote node, however one of the following conditions exists:

  • The application server domain is not active.

    If the application server domain is not active, a Network Monitor link appears in the results grid. Click the link to access the Network Monitor and click the Domain Status link to activate the domain.

  • There are integrations on the local or remote node that are in Timeout, Standby, or Error status.

    If integrations are in any of these states, a Details link appears in the results grid. Click the link to obtain to transaction ID, transaction date, and other details for troubleshooting the integrations in the Service Operations Monitor.

The results grid displays a red X to indicate that the integration status check failed.

A Details link appears. Click the link to view transaction errors by node. The system displays additional information per transaction to easily access information in the Network Monitor and Transactional Tracker.

To verify integration status with integration partners in the integration network:

  1. Access the Network Status page. (Select PeopleTools, Integration Broker, Integration Network WorkCenter.)

  2. Click the Network Integration Status button.

The system displays the outcome of network status check in the Results column in the Network Node Status grid.

Click to jump to parent topicIntrospecting and Deploying Network Integrations

This section discusses how to:

Click to jump to top of pageClick to jump to parent topicUnderstanding Introspecting and Deploying Integrations

The Integration Network features a series of pages that enable you to introspect and deploy services on remote nodes.

The system can introspect and deploy integrations on any node defined in the integration network. However, to introspect integrations on the local node, a handler and a local routing must exist on any integration that you introspect.

Important! To introspect a service operation on the local node, a handler and a local routing must be defined for the service operation.

Introspection Checks

During the introspection process, the system checks the following items for the selected service operations for the selected nodes:

Introspection Checks (REST)

During the introspection process, the system checks the following items for the selected REST service operations for the selected nodes:

REST as consumer (source):

REST as provider (target):

Deployment Processing (Non-REST and REST)

In many cases during deployment processing, the system can activate service operations, handlers, and routings that are found to be inactive during the introspection process. The system can also frequently create routings if none are found to exist during introspection. However, there are some situations where manual intervention is required to resolve routing issues and handler issues. And in all cases where service operation permissions do not exist, manual intervention is required to assign permissions.

The following list shows the conditions that must exist for the system to deploy/create a routing for a non-REST service if none is found to exist during introspection. Note the system prioritizes creating routings for the provider default service operation, then the consumer default service operation:

  1. Service operation/version must exist.

  2. Service operation version checks.

    The system checks if there is a non-default service operation.version that matches the passed in service operation / version(s). If there is a match, the system checks if there is a logical transformation. If there is a transformation, the system builds the routing using the service.version for the alias name for the version matched.

  3. Handler exists.

    If a handler exists, the system can create inbound and outbound routings.

    If a handler does not exist, the system can create an outbound routing only.

During routing creation, the system uses the service operation.version for the alias name, unless there is a proper routing on the other side. If there is a proper routing on the other side, then the routing alias name is used. The consumer routing alias has priority. If there is no consumer routing alias, then the provider alias is used.

Click to jump to top of pageClick to jump to parent topicUsing the Search for Items–Introspection/Deployment Page

The Integration Network features a Search for Items – Introspection/Deployment page (IB_INTNETWORK2) that you use to search for select integrations to introspect and deploy.

To access the Search for Items – Introspection/Deployment page, select PeopleTools, Integration Broker, Integration Network WorkCenter,, Administration, Introspection and Deployment. The following example show the page:

Click to jump to top of pageClick to jump to parent topicSearching for Integrations to Introspect and Deploy

You can search for integrations to introspect and deploy at the integration group, service , or service operation level.

Use one of the following options to search for an integration:

Integration Group

Select the radio button to search for integrations to introspect and deploy by integration group.

Use one of the following integration group filters:

  • Show All Subgroups. (Default.) Select the radio button to display all integration subgroups associated with integration groups in the system.

  • Filter by Subgroup. Select the radio button to search for a specific integration subgroup and enter its name in the field.

  • No Subgroups. Select the radio button to omit integration subgroups from your search.

  • Show Services Tied to Group. Check the box to include the services tied to an integration group in the search results. By default this option is selected.

Group Name

If searching by integration group, enter the integration group name to search, or click the Lookup button to search for one.

Service

Select the radio button to search for integrations to introspect and deploy by service.

When you select this option a Lookup button appears next to the Service field.

Click the Lookup button to search for a service to introspect and deploy or enter the name directly in the field.

Operation

Select the radio button to search for integrations to introspect and deploy by service operation.

When you select this option a Lookup button appears next to the Operation field.

Click the Lookup button to search for a service operation to introspect and deploy or enter the name directly in the field.

After selecting one of the search options, click the Search button at the bottom of the page.

Results of the search appear in the Select Items to Process grid at the bottom of the page.

Click to jump to top of pageClick to jump to parent topicSelecting Integrations to Introspect and Deploy

When you search for integrations to introspect and deploy to remote PeopleSoft nodes in the integration network, the results appear in the Select Items to Process grid at the bottom of the Search for Items – Introspection/Deployment page. Use the grid to select the integrations to introspect and deploy.

The following controls and fields appear in the Select Items to Process grid:

Select

Check the box to introspect and deploy the integration.

Check the box again to clear the selection.

Service

Name of service in the integration.

Service Operation

Name of the service operation in the integration.

Integration Group

Name of the integration group to which the integration belongs.

By default, all integrations returned in the search are selected for introspection and deployment.

 

To select an integration to introspect and deploy:

  1. Use one of the following methods to select integrations from the grid to introspect and deploy:

  2. Click the Continue button to select access the Target page and to select the remote PeopleSoft nodes to introspect and deploy.

Click to jump to top of pageClick to jump to parent topicSelecting Nodes for Integration Introspection and Deployment

Use the Target page (IB_INTNETTARGET) to select nodes for integration introspect and deploy integrations. You can select the default local node, for local-to-local integrations, or select one or more remote nodes.

To access the Target page, from the Search for Items – Introspection/Deployment page, click the Continue button. The following example, shows the page:

To select nodes for introspection and deployment:

  1. Access the Target page. (From the Search for Items – Introspection/Deployment page, click the Continue button.)

  2. Perform one of the following actions:

Selecting the Local Default Node for Integration Introspection and Deployment

To select the local default node for integration introspection and deployment:

  1. Access the Target page. (From the Search for Items – Introspection/Deployment page, click the Continue button.)

  2. Select the Local Node radio button.

  3. Click the Continue button.

Selecting Remote PeopleSoft Nodes for Integration Introspection and Deployment

To select remote PeopleSoft nodes for integration introspection and deployment:

  1. Access the Target page. (From the Search for Items – Introspection/Deployment page, click the Continue button.)

  2. Select the Remote Nodes radio button.

  3. Use one of the following methods to select nodes for integration introspection and deployment:

    By default, all remote nodes in the integration network are selected for introspection and deployment.

  4. Click the Continue button to preview the integrations to be introspected and deployed.

Click to jump to top of pageClick to jump to parent topicVerifying Nodes and Services to Introspect

The Introspection/Deployment page (IB_INTNETWORK4) displays the nodes and service operations you selected for integration and deployment in the previous step. The following example shows the Introspection/Deployment page:

To make changes, use the Previous Step button located at the bottom of the page to return to the previous pages and make any necessary changes.

If the information is satisfactory, click the Introspect button to introspect the nodes in the node list. The results appear in the Introspection Results page discussed in the next section.

Click to jump to top of pageClick to jump to parent topicViewing Introspection Results and Deploying Actions

The results of the introspection appear on the Introspection Results page (IB_INTNETWORK3_SEC). The following example shows the page:

The Introspection Results page lists any needed deployment actions that you can correct using the page. To deploy an action, select a row in the grid and click the Deploy button.

For example, in the previous example, the first row in the Operation List grid for the QE_CRM grid shows that an inbound routing does not exist for the routing alias QE_FLIGHTPLAN_SYNC.VERSION_1. To create the routing, check the Select box for the item and click the Deploy button. The system generates a routing. The following example shows the Introspection Results page after the system performs the deployment action:

The status of the action appears in the Information field and the deployment action performed appears in the Deployment Action field.

Click the Return to Target Page link to return to the Target page select additional or different nodes to introspect. Click the Return to Search link to return to the Search for Items – Introspection/Deployment page to work with different integration groups, services, and service operations.

Click to jump to parent topicSetting Service Operation Permissions

This section discusses how to:

Click to jump to top of pageClick to jump to parent topicUnderstanding Setting Service Operation Permissions

The PeopleSoft Integration Network features a Service Operations Permissions page (IB_HOME_PAGE10) that enables you to set and modify permissions for network services operations defined on the local node.

Note. You can set and modify service operation permissions on the local node only.

Click to jump to top of pageClick to jump to parent topicUsing the Service Operation Permissions Page

To access the page, select PeopleTools, Integration Broker, Integration Network WorkCenter, Administration, Service Operation Permission. The following example shows the page:

Use the options in the Level section to search for service operations for which to set permissions. The results of your search appear in the Service Operations grid at the bottom of the page.

A check mark in the Permission Set field denotes if permissions have been set for a service operation. In the example, permissions have been set for the IB_EX_MP_ROWSET_ASYNC and IB_EX_MP_ROWSET_SYNC service operations.

Click the Set Security link to access the Web Service Access page to set permissions for the service operation. The Web Service Access page opens in a new browser window as shown in the following example:

Use the Web Service Access page to assign a permission list and access level to the service operation.

Click to jump to top of pageClick to jump to parent topicSearching for Service Operations to Set Permissions

You can search for service operations for which to set permissions at the integration group, service , or service operation level.

Use one of the following options to search for a service operation:

Integration Group

Select the radio button to search for service operations by integration group.

Use one of the following integration group filters:

  • Show All Subgroups. (Default.) Select the radio button to display all integration subgroups associated with integration groups in the system.

  • Filter by Subgroup. Select the radio button to search for a specific integration subgroup and enter its name in the field.

  • No Subgroups. Select the radio button to omit integration subgroups from your search.

  • Show Services Tied to Group. Check the box to include the services tied to an integration group in the search results. By default this option is selected.

Group Name

If searching by integration group, enter the integration group name to search, or click the Lookup button to search for one.

Service

Select the radio button to search for service operations by service.

When you select this option a Lookup button appears next to the Service field.

Click the Lookup button to search for a service to introspect and deploy or enter the name directly in the field.

Operation

Select the radio button to search for service operations by service operation.

When you select this option a Lookup button appears next to the Operation field.

Click the Lookup button to search for a service operation to introspect and deploy or enter the name directly in the field.

No Permissions Exist

Check the box to filter your search results for only those service operations for which no permissions exist.

After selecting a search option , click the Search button at the bottom of the page.

Results of the search appear in the Select Items to Process grid at the bottom of the page.

Click to jump to top of pageClick to jump to parent topicSetting Service Operation Permissions

The results of a search for service operations for which to set permissions appear in the Service Operation grid of the Service Operation Permissions page. Click the Set Security link to access the Web Service Access page. The page opens in a separate browser page.

Using the Web Service Access page to assign permission lists and access levels to service operations is described elsewhere in PeopleBooks.

See Setting Web Services Permissions.

Click to jump to parent topicUsing the Integration Network Monitor

This section discusses how to:

Click to jump to top of pageClick to jump to parent topicUnderstanding Using the Integration Network Monitor

System administrators use the Integration Network Monitor to monitor integrations among other PeopleSoft systems defined in the integration network. Many of the pages and functions of the Network Monitor resemble those in the monitoring pages of the Service Operations Monitor. The major differences are that with the Network Monitor you are not limited to monitoring activity on the local node; you can monitor activity any remote PeopleSoft node defined in the network.

Network Monitor Features

The Network Monitor provides the following features:

Continue to use the Service Operation Monitor to perform the following tasks:

See PeopleTools 8.52: Integration Broker Service Operations Monitor PeopleBook

Network Monitor Pages

The Network Monitor features the following pages:

Monitor Overview

Use the Monitor Overview page (IB_INTNET_PUBCON) for a high-level overview of the status of asynchronous service operation transactions. You can group transactions by queue or service operation for viewing.

Operation Instances

The Operation Instances page (IB_INTNET_PUBHDR) enables you to monitor the status and details related to individual asynchronous service operation instances.

Publication Contracts

The Publication Contracts page (IB_INTNET_PUBCON) shows outbound publication transactions to send to remote nodes.

Subscription Contracts

The Subscription Contracts page (IB_INTNET_SUBCON) enables you to view transactions to which the local node subscribes. Subscription contracts for remote nodes do not appear.

Synchronous Transactions

The Synchronous Transaction page (IB_INTNET_SYNC) enables you to view synchronous transactions.

Domain Status

The Domain Status page (IB_INTNET_DOMSTAT) enables you to view and activate domains in the integration network.

In addition, every page of the Network Monitor features these links:

Monitor Setup

Click the link to access the Network Monitor Setup page to modify setup options, such as the number of rows to return for a query.

Search Details

Click the link to retrieve a summary detail for a specific transaction.

When you enter a transaction ID for an asynchronous transaction the Asynchronous Details page appears. When you enter a transaction ID for a synchronous transaction the Synchronous Details page appears.

Network Monitor Security

Upon accessing the monitor, you can see a list of all transactions in the system. However, to see specific information about a transaction and to view transaction details, you must have permission to the service operation.

See Setting Permissions to Service Operations.

Click to jump to top of pageClick to jump to parent topicUnderstanding Network Monitor Processing Status Information

The Network Monitor uses the same asynchronous and synchronous processing statuses as those that appear in the Service Operations Monitor.

See Asynchronous Service Operation Statuses, Understanding Synchronous Service Operation Statuses.

Click to jump to top of pageClick to jump to parent topicPrerequisites for Using the Integration Network Monitor

Note the following prerequisites for using the Network Monitor:

Click to jump to top of pageClick to jump to parent topicCommon Elements Used in the Integration Network Monitor

Click the button to show sender and receiver details in one view, instead of on separate sender and receiver tabs.

Click the button again to collapse the view.

Filter

Click the button to filter the fetched data using the filters selected.

Last Sync

The read-only field displays the date and time that the transaction data was refreshed.

Monitor Setup

Click the link to access the Network Monitor Setup page to modify setup options, such as the number of rows to return for a query.

Network Node List

Displays the active integration network nodes for which you can track activity.

Re-Sync Monitor Data

Click the button to refresh the fetched data.

The system automatically refreshes the data when you initially access any of the pages in the Transactional Tracker and when you initially select a node in the Network Node List.

Search Details

Click the link to retrieve a summary detail for a specific transaction.

When you enter a transaction ID for an asynchronous transaction the Transactional Tracker Details page appears. When you enter a transaction ID for a synchronous transaction the Synchronous Details page appears.

Time Period

Use the options in the Time Period section to limit the query results to transactions that occurred during a specific date range or that occurred between a specific date and time range.

Click to jump to top of pageClick to jump to parent topicSetting Up the Integration Network Monitor

Use the Network Monitor Setup page (IB_INTNET_MONSETUP) to set up Integration Network Monitor and Transactional Tracker options, such as the number of rows to display in the monitor, date/time ranges for query results, and more.

To access the page, select PeopleTools, Integration Broker, Integration Network WorkCenter and click the Network Monitor Setup link.

The following example shows the page:

Specifying the Number of Rows to Return

Use the Maximum Number of Rows to return field on the Network Monitor Setup page to specify the number of rows to return as search results. The default value is 1000 rows.

There is no minimum or maximum value that you can set for this parameter. Consider integration volume when setting this value.

Enabling Integration Broker Performance Statistics

Check the IB Profile Status On field on the Network Monitor Setup page to enable the collection and display of runtime Integration Broker performance statistics.

Viewing Integration Broker performance statistics is discussed elsewhere in PeopleBooks.

See Viewing System Performance Statistics.

Defining Date and Time Ranges for Query Results

Use the Time Frame section on the Network Monitor Setup page to define the date and time range in which query results should fall.

By default, the system returns search results for activity that has taken place in the past 30 days. However, you change the day range, or set parameters based on date and time ranges.

To define a date range in which query results are to fall:

  1. Select the Last X Days radio button.

  2. In the Last Number of Days field, enter a value.

    By default the value is 30, and the system returns query results for the last 30 days of activity.

To define a date and time range in which query results are to fall:

  1. Select the Date/Time Range radio button.

  2. Select the date range.

    1. In the Search from Date field, enter the start date of the date range.

      Alternatively, click the calendar icon to select a date.

    2. In the Search to Date field, enter the end date of the date range.

      Alternatively, click the calendar icon to select a date.

  3. Select the time range.

    1. In the Search from Time field, enter the start time of the time range.

    2. In the Search to Time field, enter the end time of the time range.

      Time field format is HH:MI:SS.999999, where HH represents hours, MI represents minutes, SS represents seconds, and 999999 represents microseconds.

Defining the Date Range of Network Status Query Results

In the Network Status Data section, select the number of days for which to return results of network status information for the Network Status page.

The default value is 30 days.

Click to jump to top of pageClick to jump to parent topicSelecting Nodes to Monitor in the Integration Network Monitor

Each page of the Network Monitor features a Network Node List. The Network Node List contains a list of active integration network nodes for which you can monitor integration activity. The following example shows the Network Node List:

The example shows that there are three active network nodes for which you can monitor data, AKTT, QE_CRM and QE_HCM. The QE_CRM node is highlighted and denotes that it is the currently selected node for monitoring network activity.

To change or select a node, click the node name in the tree.

When you select a node in the Network Node List, the system automatically resynchronizes and fetches the most current transaction data for the selected node.

Click to jump to top of pageClick to jump to parent topicFetching and Synchronizing Integration Network Monitor Data

The PeopleSoft system fetches and synchronizes Network Monitor data when you initially access the Network Monitor component and when you change nodes in the Network Node List.

You can also manually synchronize data by clicking the Re-Sync Monitor Data button. The Re-Sync Monitor Data appears on each page of the Network Monitor under the Network Node List.

The synchronization process synchronizes and updates the fetched data with changes in the database since the last synchronization.

A Last Sync field appears under the Re-Sync Monitor Data button and displays the date and time that the monitor data was last synchronized, whether it be by manual synchronization or system synchronization.

Click to jump to top of pageClick to jump to parent topicFiltering Integration Network Monitor Query Results

Controls on the Monitor Overview, Operation Instances, Publication Contracts, Subscription Contracts, and Synchronous Transaction pages provide data filters that enable you to narrow the fetched data results to that data which is most relevant to you.

The filters are listed on the pages on which they appear and are described in the Common Elements Used to Filter and View Asynchronous Network Monitor Data and the Common Elements Used to Filter and View Synchronous Network Monitor Data sections.

After choosing the filters, you click the Filter button to obtain the filtered results.

Click to jump to top of pageClick to jump to parent topicMonitoring Asynchronous Integration Network Service Operations

This section discusses how to:

Common Elements Used to Filter and View Network Monitor Asynchronous Service Operation Data

The following elements are used to filter and view the query results of Network Monitor service operation data.

Click the button to show sender and receiver details in one view, instead of on separate sender and receiver tab.

Click the button again to collapse the view.

Alias

Service operation alias name if defined for the service operation.

Creation Dttm

Creation date and time.

External Service Name

The name of the inbound service operation received from an integration partner. This name is equivalent to the routing alias.

Filter

Click the button to filter the fetched data using the filters selected.

Group By

Indicates how the system groups returned data. The valid values are:

  • Queue. (Default.) Displays results by queue name.

  • Service Operation. Displays results by service operation name.

Last Update Dttm

Last update date and time.

Orig Transaction ID

The original transaction ID generated and used for the service operation instance. As contracts are created another transaction ID is created for each publication or subscription contract. However, the original transaction ID is always available as a reference.

Publish, Publish Node, Node Name

Indicates the node that published the service operation.

Publish Dttm

Publish date and time.

Queue Level

Indicates the pub/sub queue for which to display information. The valid values are:

  • OpInst. (Default.) Operation instance.

  • PubCon. Publication contract.

  • SubCon. Subscription contract.

Queue Name

Name of the service operation queue.

Queue Sequence ID

Identifies the sequence of a particular service operation in a queue. This field is applicable to only service operations in ordered queues.

Segment Number

When message segments are implemented, indicates the number of the segment message

Service Operation

Name of the service operation.

Service Operation Version, Version

Indicates the version of the service operation.

Status, Status String

Processing status of the service operation.

The Network Monitor uses the same processing statuses as those that appear in the Service Operations Monitor.

See Asynchronous Service Operation Statuses, Understanding Synchronous Service Operation Statuses.

Sub Node

The name of the subscribing node.

Sub Queue

If queue partitioning exists for a queue, a Sub Queue column appears in the Results grid on the Operation Instances page, Publication Contracts page and Subscription Contracts page . Click the link to open the Sub Queue Message Queue page to view all transactions in the sub queue.

Timestamp

Date and time of the publication.

Time Period

Use the options in the Time Period group box to limit the query results to transactions that occurred during a specific date range or that occurred between a specific date and time range.

The Time Period group box features four fields for searching by date and time: From Date, To Date, From Time and To Time. If you complete just the date fields, the time fields automatically populate from 12:01 a.m. to 11:59 p.m. When left blank, no date or time is used as part of the search criteria.

Transaction ID

The unique identifier for a transaction.

Monitoring General Asynchronous Network Service Operation Information

Use the Monitor Overview page (IB_INTNET_OVRVIEW) for a high-level overview of the status of asynchronous service operation transactions in the integration network. You can group transactions by queue or service operation for viewing. To access this page, select PeopleTools, Integration Broker, Integration Network WorkCenter, Network Monitor. The Monitor Overview page shown in the following example appears:

When you access the page, the system automatically synchronizes the with the database for the selected node in the Network Node List. The processing status of asynchronous transactions appears in the Results grid at the bottom of the page. The number of operation instances in a particular status display as a linked value. Click the link to open the data in the Operation Instances page where you can view more detailed information.

If you change the node for which to view information, by clicking a different node name in the Network Node List, the system automatically resynchronizes the page with the most up-to-date transaction information for the node.

By default, the system queries the database by service operation queue for operation instance information.

You can query the database by modifying the query filters and then clicking the Filter button. The filters available on the page are:

The data filters and data elements that appear in the Results grid are described in the Common Elements Used to Filter and View Asynchronous Network Monitor Data section.

Monitoring Asynchronous Network Service Operation Instances

Use the Operation Instances page (IB_INTNET_PUBHDR) to monitor the status and details related to individual asynchronous service operation instances. To access this page, select PeopleTools, Integration Broker, Integration Network WorkCenter, Network Monitor and click the Operation Instances tab. The following example shows the Operation Instances page:

The example shows a partial view of the query results appearing in the Results grid.

If you change the node for which to view information, by clicking a different node name in the Network Node List, the system automatically resynchronizes the page with the most up-to-date transaction information for the node.

By default, the system queries the database by service operation queue and the asynchronous processing status Done.

You can query the database by modifying the query filters and then clicking the Filter button. The filters available on the page are:

Query results appear in the Results Grid. If the queue in which a transaction is processed is partitioned, a hyperlinked transaction ID appears in the Sub Queue column in the Results grid. Click the link to view all network service operations in the sub queue.

For each transaction in the Results grid a Details link appears. Click the Details link access the Asynchronous Details page and to view additional details for the transaction. Based on the processing status of the transaction, the Asynchronous Details page enables you to view any transaction error messages and resubmit or cancel the transaction.

The data filters and data elements that appear in the Results grid are described in the Common Elements Used to Filter and View Asynchronous Network Monitor Data section.

Monitoring Asynchronous Network Service Operation Publication Contracts

Use the Publications Contracts page (IB_INTNET_PUBCON) to monitor the status and details related to asynchronous service operation publication contracts. To access this page, select PeopleTools, Integration Broker, Integration Network WorkCenter, Network Monitor and click the Publication Contracts tab. The following example shows the Publication Contracts page:

The example shows a partial view of the query results appearing in the Results grid.

If you change the node for which to view information, by clicking a different node name in the Network Node List, the system automatically resynchronizes the page with the most up-to-date transaction information for the node.

By default, the system queries the database by service operation queue and the asynchronous processing status Done.

You can query the database by modifying the query filters and then clicking the Filter button. The filters available on the page are:

Query results appear in the Results grid.

The data filters and data elements that appear in the Results grid are described in the Common Elements Used to Filter and View Asynchronous Network Monitor Data section.

If the queue in which a transaction is processed is partitioned, a hyperlinked transaction ID appears in the Sub Queue column in the Results grid. Click the link to view all network service operations in the sub queue.

For each transaction in the Results grid a Details link appears. Click the Details link to access the Asynchronous Details page and to view additional details for the transaction. Based on the processing status of the transaction, the Asynchronous Details page enables you to view any transaction error messages and resubmit or cancel the transaction.

The following example shows the Asynchronous Details (IB_INTNET_DET) page for an asynchronous network publication contract:

The top portion of the Asynchronous Details page shows the information that appears in the Results grid of the Publication Contracts page.

The Publication Contracts grid at the bottom of the page shows additional information about the transaction.

The Actions tab shows each node that is subscribing to the contract. In this example, the AKTT node and the QE_HCM node are the nodes that are subscribing to the contract. Depending on the processing status, the Resubmit and Cancel buttons are active and you can perform those related actions.

See Resubmitting and Cancelling Integration Network Transactions.

If there are any processing errors with a transaction, a View Info Details link appears . Click the link to view the error information. In this example the View Info Details link is enabled for the QE_HCM node, indicating that processing errors occurred with the transaction.

The Information tab reveals details about the publication transaction, including the transaction ID, the transaction time stamp, and so on.

Monitoring Asynchronous Network Service Operation Subscription Contracts

Use the Subscription Contracts page (IB_INTNET_SUBCON) to monitor the status and details related to asynchronous service operation subscription contracts. To access this page, select PeopleTools, Integration Broker, Integration Network WorkCenter, Network Monitor and click the Subscription Contracts tab. The following example shows the Subscription Contracts page:

The example shows a partial view of the query results appearing in the Results grid.

If you change the node for which to view information, by clicking a different node name in the Network Node List, the system automatically resynchronizes the page with the most up-to-date transaction information for the node.

By default, the system queries the database by service operation queue and the asynchronous processing status Done.

You can query the database by modifying the query filters and then clicking the Filter button. The filters available on the page are:

Query results appear in the Results grid.

The data filters and data elements that appear in the Results grid are described in the Common Elements Used to Filter and View Asynchronous Network Monitor Data section.

If the queue in which a transaction is processed is partitioned, a hyperlinked transaction ID appears in the Sub Queue column in the Results grid. Click the link to view all network service operations in the sub queue.

For each transaction in the Results grid a Details link appears. Click the Details link to access the Asynchronous Details page and to view additional details for the transaction. Based on the processing status of the transaction, the Asynchronous Details page enables you to view any transaction error messages and resubmit or cancel the transaction.

The following example shows the Asynchronous details page for an asynchronous network subscription contract:

The top portion of the Asynchronous Details page shows the information that appears in the Results grid of the Subscription Contracts page.

The Subscription Contracts grid at the bottom of the page shows additional information about the transaction.

The Actions tab shows the service operation handler name for the subscription contract. Depending on the processing status, the Resubmit and Cancel buttons are active and you can perform those related actions.

See Resubmitting and Cancelling Integration Network Transactions.

If there are any processing errors with a transaction, a View Info Details link appears on the Actions tab. Click the link to view the error information.

The Information tab reveals details about the subscription transaction, including the transaction ID, the transaction time stamp, and so on.

Click to jump to top of pageClick to jump to parent topicMonitoring Synchronous Integration Network Service Operations

This section discusses how to monitor synchronous network service operation transactions.

Common Elements Used to Filter and View Network Monitor Synchronous Service Operation Data

The following elements are used to filter and view the query results of Network Monitor service operation data.

Destination Publish Node

Identifies the name of the node where the service operation was sent.

External Service Name

The name of the inbound service operation received from an integration partner. This name is equivalent to the routing alias.

Filter

Click the button to filter the fetched data using the filters selected.

Final Destination

Identifies the name of the node of the final destination for the service operation.

Last Update Dttm

Last update date and time.

Non-Repudiation ID

Identifies a unique number used to associate a service operation instance with the nonrepudiation log.

Pub/Sub Timestamp

Identifies the date and time that the service operation instance was last processed.

Publish, Pub Node

Indicates the node that published the service operation.

Publish Dttm

Publish date and time.

Segment Number

When message segments are implemented, indicates the number of the segment message

Service Operation

Name of the service operation.

Service Operation Version, Version

Indicates the version of the service operation.

Status, Status String

Processing status of the service operation.

The Network Monitor uses the same processing statuses as those that appear in the Service Operations Monitor.

See Asynchronous Service Operation Statuses, Understanding Synchronous Service Operation Statuses.

Timestamp

Date and time of the publication.

Time Period

Use the options in the Time Period group box to limit the query results to transactions that occurred during a specific date range or that occurred between a specific date and time range.

The Time Period group box features four fields for searching by date and time: From Date, To Date, From Time and To Time. If you complete just the date fields, the time fields automatically populate from 12:01 a.m. to 11:59 p.m. When left blank, no date or time is used as part of the search criteria.

Trans Type

Indicates the type of synchronous transaction. The valid values are:

  • OutSync: Outbound Synchronous.

  • InSync: Inbound Synchronous.

Transaction ID

The unique identifier for a transaction.

Updated Date/Time

Identifies the date and time the service operation was last updated.

Monitoring Synchronous Network Service Operation Transactions

Use the Synchronous Transactions page (IB_INTNET_SYNC) to monitor the status and details related to synchronous service operations in the integration network. To access this page, select PeopleTools, Integration Broker, Integration Network WorkCenter, Network Monitor and click the Synchronous Transactions tab. The following example shows the Synchronous Transactions page:

The example shows a partial view of the query results appearing in the Results grid.

If you change the node for which to view information, by clicking a different node name in the Network Node List, the system automatically resynchronizes the page with the most up-to-date transaction information for the node.

You can query the database by modifying the query filters and then clicking the Filter button. The filters available on the page are:

Query results appear in the Results grid.

The data filters and data elements that appear in the Results grid are described in the Common Elements Used to Filter and View Synchronous Network Monitor Data section.

For each transaction in the Results grid a Details link appears. Click the Details link to access the Synchronous Details page (IB_INTNET_SYNC_DET) and to view additional details for the transaction. Based on the processing status of the transaction, the Asynchronous Details page enables you to view any transaction error messages and resubmit or cancel the transaction. The following example shows the Synchronous Details page:

If there are any processing errors with a transaction, an Error Messages link appears. Click the link to view error message information.

Click to jump to top of pageClick to jump to parent topicMonitoring Integration Network Domain Status

Use the Domain Status page (IB_INTNET_DOMSTAT) to monitor the status of the domain for the node selected in the Network Node List. To access this page, select PeopleTools, Integration Broker, Integration Network WorkCenter, Network Monitor and click the Domain Status tab. The following example shows the Domain Status page:

Use the page to activate the domain of the selected node in the Network Node List, as necessary.

To activate a network node:

  1. Access the Domain Status page (PeopleTools, Integration Broker, Integration Network WorkCenter, Network Monitor).

    The Network Monitor – Monitor Overview page appears.

  2. In the Network Node List, select a node.

  3. Click the Domain Status tab.

  4. In the Domains grid, select the domain to activate.

  5. Click the Activate button.

Click to jump to top of pageClick to jump to parent topicResubmitting and Cancelling Integration Network Transactions

This section discusses how to:

Understanding Resubmitting and Canceling Network Transactions for Processing

You can resubmit and cancel network transactions for processing for only those to which you have permissions. If you attempt to resubmit or cancel a transaction for which you do not have permission, the system ignores the action.

Understanding Resubmitting and Canceling Future-Dated Network Transactions

You can cancel a future-dated transaction in the network monitor as you would any other transaction. However, when you cancel a future-dated transaction, the future date information is not retained. So if you subsequently resubmit the transaction, the system immediately submits it for processing.

Resubmitting and Canceling Individual Network Transactions

To resubmit or cancel individual transactions, select the check box next to the appropriate transaction and click the Resubmit or Cancel button. To deselect a transaction, clear the check box next to the transaction.

Resubmitting and Canceling Network Transactions in Bulk

You can resubmit and cancel network transaction for processing in bulk using the Network Monitor. Network transactions to resubmit in bulk must be in one of the following statuses:

Network transactions to cancel in bulk must be in one of the following statuses:

In addition to the Clear All, Resubmit and Cancel buttons, you can also use the following links when resubmitting and canceling network transactions in bulk:

Select All

Click the link to select all network transaction in the results grid to resubmit or cancel. After you click this link, click the Resubmit or Cancel button as appropriate.

Deselect All

Click the link to deselect all network transactions selected in the results grid.

Click to jump to parent topicUsing the Integration Network Transactional Tracker

This section discusses how to:

Click to jump to top of pageClick to jump to parent topicUnderstanding the Integration Network Transactional Tracker

The Network Transactional Tracker, or Transactional Tracker, enables you to track inbound and outbound integrations between the local node and all other nodes defined in the integration network.

The Transactional Tracker component (IB_INTNET_TRACKER) features three page for tracking activity:

Tracker Overview

The Tracker Overview page (IB_INTNET_TRACKOVR) shows information about inbound and outbound asynchronous service operation instances, including the number of service operation instances, publication contracts, and subscription contracts that have been processed between the local node and a selected remote node. You can filter transaction information to display by queue or by service operation. For each transaction returned as a query result, the system provides a link to the Transactional Tracker Details page where you can review complete information for the transaction as well as cancel the transaction or resubmit the transaction for processing, depending on its processing status.

Tracker Main View

The Tracker Main View page (IB_INTNET_TRACKER) shows detailed information for inbound and outbound asynchronous transactions, including transaction ID, publishing timestamp, and more. You can filter transaction information by transaction ID, service operation name, queue name, and/or the direction of the transactions. This page features a link to the Integration Broker Statistics pages, so you can view transaction performance statistics to identify performance issues in the integration system. For each transaction returned as a query result, the system provides a link to the Transactional Tracker Details page where you can review complete information for the transaction as well as cancel the transaction or resubmit the transaction for processing, depending on its processing status.

Synchronous Tracker View

The Synchronous Tracker View page (IB_INTNET_TRACKSYN) enables you to view detailed information for inbound and outbound synchronous transactions between integration network nodes. You can filter transaction information by service operation name, the direction of the transaction, and/or by the status of processing status in the system. Like the Tracker Main View page, this page also features a link to the Integration Broker Statistics pages to view performance statistics and identify issues in the integration system. You can also launch the Integration Broker Service Operations Monitor – Synchronous Details page from this page to view error and logging information for specific transactions, depending on its processing status.

The pages in the Transactional Tracker feature links to the following pages that enable you to view details for a single transaction:

Transactional Tracker Details

The Transactional Tracker Details page (IB_INTNET_TRACKDET) provides a snapshot view of all details for a single asynchronous transaction. The Tracker Main page and the Tracker Main View page provide links to the Transaction Tracker Details page. For the sending node and receiving node in the transaction, the system displays the transaction ID, the service operation name, queue name, processing status, and more. In addition, depending on the processing status you can cancel or resubmit the transaction for processing.

Synchronous Details

The Synchronous Details page (IB_INTNET_TRSYNCDT) provides a snapshot view of the transaction from the perspective of the sending node or the receiving node. The page features controls that enable you to view transaction errors and resubmit or cancel a transaction if there is a processing error.

Click to jump to top of pageClick to jump to parent topicPrerequisites for Using the Transactional Tracker

Note the following prerequisites for using the transactional tracker:

Click to jump to top of pageClick to jump to parent topicCommon Elements Used in the Transactional Tracker

Network Node List

Displays the active integration network nodes for which you can track activity.

Re-Sync Monitor Data

Click the button to refresh the fetched data.

The system automatically refreshes the data when you initially access any of the pages in the Transactional Tracker and when you initially select a node in the Network Node List.

Last Sync

The read-only field displays the date and time that the transaction data was refreshed.

Monitor Setup

Click the link to access the Network Monitor Setup page to modify setup options, such as the number of rows to return for a query.

Search Details

Click the link to retrieve a summary detail for a specific transaction.

When you enter a transaction ID for an asynchronous transaction the Transactional Tracker Details page appears. When you enter a transaction ID for a synchronous transaction the Synchronous Details page appears.

Time Period

Use the options in the Time Period group box to limit the query results to transactions that occurred during a specific date range or that occurred between a specific date and time range.

The Time Period group box features four fields for searching by date and time: From Date, To Date, From Time and To Time. If you complete just the date fields, the time fields automatically populate from 12:01 a.m. to 11:59 p.m. When left blank, no date or time is used as part of the search criteria.

Filter

Click the button to filter the fetched data using the filters selected.

Sender Node

This read-only field displays the name of the sending node for the transaction query.

Receiver Node

This read-only field displays the name of the receiving node for the transaction query.

View Statistics

Click the link to view system performance statistics for asynchronous and synchronous transactions that flow through PeopleSoft Integration Broker. The statistics can help you to identify bottlenecks and other performance issues in your integration system.

Click the button to show sender and receiver details in one view, instead of on separate sender and receiver tab.

Click the button again to collapse the view.

Sender

Click the tab to view transaction overview information for the sending node.

Receiver

Click the tab to view transaction overview information for the receiving node.

Click to jump to top of pageClick to jump to parent topicSelecting Nodes to Track in the Transactional Tracker

Each page of the Transactional Tracker features a Network Node List. The Network Node List contains a list of active integration network nodes for which you can track transaction activity between the local node. The following example shows the Network Node List:

The example shows that there are two active network nodes, QE_CRM and QE_HCM. The QE_CRM node is highlighted and denotes that it is the currently selected node for tracking transactions between the local node.

To change or select a node, click the node name in the tree.

When you select a node in the Network Node List, the system automatically resynchronizes and fetches the most current transaction data for the selected node and the local node.

Click to jump to top of pageClick to jump to parent topicFetching and Synchronizing Transactional Tracker Data

The PeopleSoft system fetches and synchronizes Transactional Tracker data when you initially access the Transactional Tracker component and when you change nodes in the Network Node List.

You can also manually synchronize data by clicking the Re-Sync Monitor Data button. The Re-Sync Monitor Data appears on each page of the Transactional Tracker under the Network Node List.

The synchronization process synchronizes and updates the fetched data with changes in the database since the last synchronization.

A Last Sync field appears under the Re-Sync Monitor Data button and displays the date and time that the tracker data was last synchronized, whether it be by manual synchronization or system synchronization.

Click to jump to top of pageClick to jump to parent topicFiltering Transactional Tracker Data

Controls on each page the Transactional Tracker provide data filters that enable you to narrow the fetched data results to that data which is most relevant to you.

After choosing the filters, you click the Filter button to obtain the filtered results.

For example, each page of the Transactional Tracker features a Time Period group box where you can filter the fetched data by date or by date and time.

The specific data filters for each page are described in the Common Elements Used in the Transactional Tracker section and in the documentation for the pages on which they appear.

See Common Elements Used in the Transactional Tracker.

Click to jump to top of pageClick to jump to parent topicViewing Network Asynchronous Transaction Instances

Use the Tracker Overview page (IB_INTNET_TRACKOVR) to view instance information for asynchronous transactions between the local node and remote nodes in the integration network.

Before using the Tracker Overview page see the prerequisites for using the Transactional Tracker described elsewhere in this chapter.

See Prerequisites for Using the Transactional Tracker.

The page enables you to view transaction instance counts for sending and receiving nodes at each queue level in the system. You can view this information by service operation or queue, and the direction of the transaction (inbound or outbound).

When you access the Transactional Tracker component, the Tracker Overview page appears by default.

To access the Tracker Overview page, select PeopleTools, Integration Broker, Integration Network WorkCenter. In the WorkCenter navigation pane, click Transactional Tracker. The following example shows the Tracker Overview page:

Use the Network Node List to select the remote node for which to track transactions. The system fetches available transaction data between the local node and the remote node. The system automatically synchronizes the data that appears on the page when you initially access the page and when you change the remote node.

Use one or more of the following data filters on this page:

Group By

Displays transactions based on the option selected. The valid options are:

  • Queue. (Default.) Use this option to filter transaction data by queue. Enter the queue name or click the Lookup button to search the database for a value.

  • Service Operation. Use this option to filter transaction data by service operation. Enter the service operation name or click the Lookup button to search the database for a value.

Direction

Indicates the direction of the transaction. The valid values are:

  • Inbound. Indicates an inbound transaction from the node selected in the Network Node List to the local node.

  • Outbound. (Default.) Indicates an outbound transaction from the local node to the node selected in the Network Node List.

Time Period

Use the options in the Time Period group box to limit the query results to transactions that occurred during a specific date range or that occurred between a specific date and time range.

The Time Period group box features four fields for searching by date and time: From Date, To Date, From Time and To Time. If you complete just the date fields, the time fields automatically populate from 12:01 a.m. to 11:59 p.m. When left blank, no date or time is used as part of the search criteria.

The Results grid displays the transaction instance data based on the default values for the filters. You can change the values for any of the fields and click the Filter button to display data based on the different filters.

When viewing the fetched data click the Expand icon to view the columns for all returned data. The following example shows the Tracker Overview page with the Results grid expanded:

In the Results grid, click the Sender or Receiver tab to view counts of message instances, publication contracts, and subscription contracts processed by each respective node.

The following information appears in the Results grid on the Sender tab:

Queue Name

Appears when the Group By filter is set to Queue.

The name of the queue that contains the name of the instances shown. Click a queue name link to launch the Tracker Main View page to view details of the transactions associated with the queue.

Service Operation

Appears when the Group By filter is set to Service Operation.

The name of the service operation that contains the instances shown. Click a service operation name link launch the Tracker Main View page to view details of the transactions associated with the service operation.

Sender Instance Count

Shows the number of message instances the sender has sent to the receiving node.

The following information appears in the Results grid on the Receiver tab:

Sender Publication Count

Shows the number of publication contracts the sender has sent to the receiving node.

Sender Subscription Count

Shows the number of subscription contracts the sender has sent to the receiving node.

Receiver Instance Count

Shows the number of message instances received by the receiving node.

When viewing the Sender tab you may have to click the Expand icon on the Results grid to view this field.

Receiver Subscription Count

Shows the number of subscription contracts received by the receiving node.

Click to jump to top of pageClick to jump to parent topicViewing Network Asynchronous Transaction Detail Information

This section describes how to use the Transactional Tracker to view asynchronous transaction details.

Understanding Integration Network Asynchronous Processing Status Information

Asynchronous transactional detail information that the Transactional Tracker provides includes processing status information for service operation instances, publication contracts, and subscription contracts.

The processing statuses that the Transactional Tracker uses for asynchronous service operations are the same as those used in the Service Operations Monitor.

See Asynchronous Service Operation Statuses.

Viewing Integration Network Asynchronous Transactional Details

Use the Tracker Main View page (IB_INTNET_TRACKER) to view details for asynchronous transactions between the local node and remote nodes in the integration network.

Before using the Tracker Main View page see the prerequisites for using the Transactional Tracker described elsewhere in this chapter.

See Prerequisites for Using the Transactional Tracker.

The Tracker Main View page enables you to view the transaction IDs, queue names, processing status, and more for the transactions.

You can access the Tracker Main View page from the Tracker Overview page using the Results grid; click the queue name or service operation link in the grid. You can also access the page using the standard PeopleSoft Pure Internet Architecture navigation by selecting PeopleTools, Integration Broker, Integration Network WorkCenter, then in the WorkCenter navigation pane click the Transactional Tracker link, and click the Tracker Main View page. The following example shows the Tracker Main View page:

If you access the page from the Tracker Overview page, the page populates with data based on the query results from the Tracker Overview page. If you access the page without first conducting a query on the Tracker Overview page, click the Re-Sync Monitor Data button to populate the page with query data.

Use one of more of the following filters on this page:

Transaction ID

Enter the unique identifier for the transaction in the PeopleSoft system.

Service Operation

Enter the name of a service operation to view transactions using the operation.

Queue Name

Enter the name of a service operation queue that is processing transactions to view.

Direction

Indicates the direction of the transaction. The valid values are:

  • Inbound. Indicates an inbound transaction from the node selected in the Network Node List to the local node.

  • Outbound. (Default.) Indicates an outbound transaction from the local node to the node selected in the Network Node List.

Time Period

Use the options in the Time Period group box to limit the query results to transactions that occurred during a specific date range or that occurred between a specific date and time range.

The Time Period group box features four fields for searching by date and time: From Date, To Date, From Time and To Time. If you complete just the date fields, the time fields automatically populate from 12:01 a.m. to 11:59 p.m. When left blank, no date or time is used as part of the search criteria.

If you access the Tracker Main View page from the Tracker Overview page, the system defaults the queue name or service operation name from the Tracker Overview page as a filter. In addition, the direction of the transaction as viewed on the Tracker Overview page is also defaulted on the page.

The following information appears in the Results grid on the Sender Node tab:

Transaction ID

The unique identifier for the transaction in the PeopleSoft system.

Publish Timestamp

Date and time the transaction was published. (Outbound transactions.)

Sender Instance Status

Processing status of the instance on the sending system.

Sender Publishing Status

Processing status of the publication contract on the sending system.

Sender Subscription Status

Processing status of the subscription contract on the sending system.

Additional Receiver Nodes

Click the link to view the names of other nodes in the network receiving the transaction.

Details

Click the Details link for a summary view of the transaction using the Transaction Tracker Details page. In addition a snapshot view of sending and receiving node details, you can also cancel and resubmit transactions for processing from the page.

After a query the following information appears in the Results grid on the Receiver Node tab:

Receiver Instance Status

Processing status of the service operation instance on the receiving system.

Receiver Subscription Status

Processing status of the subscription contract on the receiving system.

Click to jump to top of pageClick to jump to parent topicViewing Network Synchronous Transactional Details

This section describes using the Synchronous Tracker View page to view integration network synchronous transactional details.

Understanding Integration Network Synchronous Processing Status Information

Synchronous transactional detail information that the Transactional Tracker provides includes processing status information for service operations.

The processing statuses that the Transactional Tracker uses for synchronous service operations are the same as those used in the Service Operations Monitor. The statuses for synchronous service operations are:

Done

Indicates the synchronous request was successful.

Error

Indicates that an error occurred during processing. Manual intervention is required.

See Understanding Synchronous Service Operation Statuses.

Prerequisites for Viewing Integration Network Synchronous Transactional Details

Before using the Synchronous Tracker View page see the prerequisites for using the Transactional Tracker described elsewhere in this chapter.

See Prerequisites for Using the Transactional Tracker.

As part of the query results for synchronous transaction queries the system provides a Details link. The Detail link provides access to the Synchronous Details page in the Service Operations Monitor where you can view logging information. To access and view the logs you must set the logging level on the routing definition of all service operations for which you want to view logging information.

Viewing Integration Network Synchronous Transactional Details

Use the Synchronous Tracker View page (IB_INTNET_TRACKSYN) to view details for synchronous transactions between the local node and remote nodes in the integration network. The page enables you to view the transaction IDs, timestamps, service operation name, service operation version, service operation type, and more for integration network synchronous transactions.

To access the page select PeopleTools, Integration Broker, Integration Network WorkCenter, then in the WorkCenter navigation pane click the Transactional Tracker link, and click the Synchronous Tracker View page. The following example shows the Synchronous Tracker View page:

When you access the page, click the Re-Sync Monitor Data button fetch the data. The system displays the query results in the Results grid, based on the default filters.

The following example shows query results for the QE_CRM mode based on the default Outbound direction filter:

As with all the pages in the Transactional Tracker, the Synchronous Tracker View page features several filter options so that you can view the most relevant data for your business requirements. After you select filter options, click the Filter button to apply the filter(s). View the results in the Results grid. The valid data filters for the Synchronous Tracker View page are:

Service Operation

Use this option to filter transaction data by service operation. Enter the service operation name or click the Lookup button to search the database for a value.

Direction

Indicates the direction of the transaction. The valid values are:

  • Inbound. Indicates an inbound transaction from the node selected in the Network Node List to the local node.

  • Outbound. (Default.) Indicates an outbound transaction from the local node to the node selected in the Network Node List.

Status

Filter the fetched results by the processing status of the service operation. The valid values are:

  • Done.

  • Error.

Time Period

Use the options in the Time Period group box to limit the query results to transactions that occurred during a specific date range or that occurred between a specific date and time range.

The Time Period group box features four fields for searching by date and time: From Date, To Date, From Time and To Time. If you complete just the date fields, the time fields automatically populate from 12:01 a.m. to 11:59 p.m. When left blank, no date or time is used as part of the search criteria.

After a query the results appear on the Transactions and Information tabs in the Results grid.

The following information appears in the Results grid on the Transactions tab:

Timestamp

The date and time the service operation was sent to the receiving node.

Transaction ID

The unique identifier for the transaction in the PeopleSoft system.

Service Operation

The name of the service operation.

Version

The service operation version.

Trans Type

The service operation type. The valid values are:

  • OutSync: Outbound synchronous.

  • InSync: Inbound synchronous.

Pub Node

The name of the node sending the transaction.

String Status

The processing status of the service operation. The valid values are:

  • Done.

  • Error.

Details

Click the Details link to access the transaction in the Service Operations Monitor – Synchronous Details and view logging and error information.

To capture logging information for a service operation you must set the logging level on the routing definition of the service operation. The Routings-Routing Definitions page features a Log Details drop-down list for setting the log level.

See Defining General Routing Information.

The following information appears in the Results grid on the Information tab:

Publisher

Publisher of the service operation. This is usually the user ID of the person in the publishing system who triggered the publication.

Last Upd DtTm

Indicates the date and time the transaction was last updated.

NRID

Nonrepudiation ID. Identifies a unique number used to associate a service operation instance with the nonrepudiation log.

Dest Pub Node

Destination publish node. Identifies the name of the node where the service operation was sent.

Final Dest Node

Final destination node. Identifies the name of the node of the final destination for the service operation.

Details

Click the Details link to access the transaction in the Service Operations Monitor – Synchronous Details and view logging and error information.

To capture logging information for a service operation you must set the logging level on the routing definition of the service operation. The Routings-Routing Definitions page features a Log Details drop-down list for setting the log level.

See Defining General Routing Information.

Click to jump to top of pageClick to jump to parent topicViewing Network Transaction Information for Specific Transactions

This section discusses how to:

Understanding Viewing Integration Network Transaction Information for Specific Transactions

The Transactional Tracker features pages for viewing the details of specific transactions. Use the Transactional Tracker Details page to view information for an asynchronous transaction; use the Synchronous Details page to view information for a synchronous transaction.

Before using the Transactional Tracker Details page or the Synchronous Details page see the prerequisites for using the Transactional Tracker described elsewhere in this chapter.

See Defining General Routing Information.

Searching for Transaction Data

You can search for and access the Transactional Tracker Details page or the Synchronous Details page using the Search Details link that appears on the Tracker Overview page, the Tracker Main View page, and the Synchronous Main View page.

Access the pages as follows:

On each these pages the Search Details link appears under the Network Node list as shown in the following example:

When you click the Search Details link the Search for Transaction Details page (IB_VERIFYNET_SEC) appears where you enter the transaction ID of the transaction you want to view.

Important! The transaction ID that you enter should always be the instance transaction ID.

The following example shows the Search for Transaction Details page:

When you click the Search Details button to search for the transaction the following Multiple Target Nodes (IB_NODELIST_SEC) page appears if the transaction exists on more than one network node:

If the transaction exists on more than one network node, click the name of the node for which you want to view the transaction.

If you selected an asynchronous transaction, the Transactional Tracker Detail page appears in a separate browser window for the transaction on the selected node. If you selected a synchronous transaction, the Synchronous Details page appears in a separate browser window for the transaction on the selected node.

Note. If the Transactional Tracker Detail page or the Synchronous Details page does not appear in a full-size browser window, click the browser Restore button in the upper right-corner of the browser to restore the browser window to full size.

Accessing Transaction Data from Query Results Grids

When you conduct a query on the Tracker Main View page or the Synchronous Main View page the results appear in the Results grid at the bottom of the page. At the end of each row of results is a Details link that provides access to the transaction details for the specific transaction.

Access the pages as follows:

After you select a remote node and synchronize the data the query results appear in the Results grid at the bottom of the page. The following example shows a partial view of the Results grid for an asynchronous query on the Tracker Main View page:

The following example shows a partial view of the Results grid for a synchronous query on the Synchronous Main View page:

Click the Details link for a transaction to launch the Transactional Tracker Details page for an asynchronous transaction or to launch the Synchronous Details page for a synchronous transaction. Note that either page appears in a separate browser window.

Note. If the Transactional Tracker Detail page or the Synchronous Details page does not appear in a full-size browser window, click the browser Restore button in the upper right-corner of the browser to restore the browser window to full size.

Viewing Data for an Asynchronous Transaction

The following example shows the Transactional Tracker Details page:

The Transactional Tracker Details page features transaction information for the sending and receiving node. If errors exist in the transaction the Error Messages and View Error Details links are active and you can click them for additional details. The Resubmit and Cancel buttons on the page are enabled if the status of the transaction is such that these actions are warranted.

The fields that appear on the page are described elsewhere in this section.

You can search for a specific transaction to view or you can launch the Transactional Tracker Details page from the results grid on the Tracker Main page or the Tracker Main View page.

Viewing Data for a Synchronous Transaction

The following example shows the Synchronous Details page:

The Synchronous Details page in the Transactional Tracker has the same format and content of the Synchronous Details page in the Integration Broker Service Operations Monitor, except that you cannot view transactional XML using the page in the Transactional Tracker.

If errors exist in the transaction the Error Messages link is active and you can click the link for additional details. The Resubmit and Cancel buttons on the page are enabled if the status of the transaction is such that these actions are warranted.

The fields that appear on the page are described elsewhere in this section.