Planning and Scheduling Optimization Integration (SCH360) - Installation

This document describes how to install the IFS integration to Planning and Scheduling Optimization (PSO).

When to use this information:

When the necessary IFS components and PSO components are installed, this guide describes how to configure the two system to work together.

Note 1: Please note that many of the system settings are already inserted into the system. However, in some cases, these setting needs to be verified and/or modified. This guideline is also useful for troubleshooting scenarios.

Note 2 : 360 Scheduling is renamed to Planning and Scheduling Optimization (PSO), and therefore some artifacts containing the string 360 still occur in this documentation.

Contents

• Step 1: Setup and Configure Batch Queues (PSO_RESPONSE / PSO_REQUEST)
• Step 2: Configure Outbound and Inbound Routing Rules, Routing Addresses and Envelopes
• Step 3: Setup Broadcasts
• Step 4: Setup Datasets
• Step 5: Configure the integration interface user
• Step 6: Setup and Configure Scheduled Tasks for Load- and Change Messages for the Dataset
• Step 7: Configure Default Parameters for the PSO Integration
• Step 8: Configure PSO software to support the IFS PSO Integration
• Troubleshooting Guide

Step 1: Setup and Configure Batch Queues (PSO_RESPONSE / PSO_REQUEST)

PSO_RESPONSE (DEFAULT INBOUND QUEUE)

Verify the PSO_RESPONSE asynchronous queue for hosting all the inbound messages coming from PSO. Type of message can be file or http. The configuration screen should look as displayed below in Solution Manager/Integration/IFS Connect/Setup IFS Connect:

PSO_REQUEST (DEFAULT OUTBOUND QUEUE)

Verify the PSO_REQUEST asynchronous queue for hosting all the outbound messages. Type of message can be file or http. The configuration screen should look as displayed below in Solution Manager/Integration/IFS Connect/Setup IFS Connect:

FILE READERS

Validate the already existing file reader. This is done in Solution Manager/Integration/IFS Connect/Setup IFS Connect:

CLEAN UP

Create clean up task in Solution Manager/Background Processing/Scheduled Tasks/Scheduled Database Task for PSO_RESPONSE and PSO_REQUEST queues.

Note: Set proper values in the Parameters section on usage. This is to avoid too large tablespaces storing old messages.

SHRINK LOB SEGMENTS

To reduce the tablespace size, it is important to activate the background job SHRINK LOB SEGMENTS to run at least once a week. This is defined in My Administration/Scheduled Tasks/Schedule Database Tasks.

Note: If you have your LOB segments stored in secured files, this functionlaity is only supported if running Enterprise Edition of the Oracle database.

Step 2: Configure Outbound and Inbound Routing Rules, Routing Addresses and Envelopes

PSO - Send Scheduling Request - File (MANUAL INSTALLATION STEP)

Add an outbound routing rule for sending file messages to PSO in Solution Manager/Integration/IFS Connect/Routing Address. Output file must be updated to the correct server name and path for PSO Input Manager Service (IMS).

PSO - Send Scheduling Request - Http (MANUAL INSTALLATION STEP)

Add an outbound routing rule for sending http messages to PSO in Solution Manager/Integration/IFS Connect/Routing Address. URL address must be updated to the correct http address to the PSO web service interface server.

PSO - Receive Scheduling Response

Verify the existing inbound routing address rule for receiving file messages from PSO for scheduling messages. The configuration screen should look like this in Solution Manager/Integration/IFS Connect/Routing Address:

PSO - Receive Scheduling Response - File

Verify the existing inbound routing rule for receiving file messages from PSO for scheduling messages. The configuration screen should look like this in Solution Manager/Integration/IFS Connect/Routing Rules:

PSO - Receive Scheduling Response - Http

Verify the existing inbound routing rule for receiving HTTP messages from PSO for scheduling messages. The configuration screen should look like this in Solution Manager/Integration/IFS Connect/Routing Rules:

PSO - Receive Scheduling Workbench Update - Http

Verify the existing inbound routing rule for receiving HTTP messages from PSO for workbench commit. The configuration screen should look like this in Solution Manager/Integration/IFS Connect/Routing Rules:

PSO - Send Scheduling Request - File

Verify the existing outbound routing rule for sending scheduling file messages to PSO. The configuration screen should look like this in Solution Manager/Integration/IFS Connect/Routing Rules:

PSO - Send Scheduling Request - Http

Verify the already existing outbound http routing rule for sending http messages to PSO. The configuration screen should look like this in Solution Manager/Integration/IFS Connect/Routing Rules:

SCH360_INBOUND_TRANSFORMER

Verify the existing inbound transformer for transforming PSO XML to IFS XML. The configuration screen should look like this in Solution Manager/Integration/IFS Connect/Setup IFS Connect:

SCH360_INBOUND_TRANSFORMER_HTTP

Verify the existing inbound transformer for transforming PSO XML to IFS XML. The configuration screen should look like this in Solution Manager/Integration/IFS Connect/Setup IFS Connect:

SCH360_OUTBOUND_TRANSFORMER_HTTP

Verify the already existing outbound HTTP transformer for transforming IFS XML to PSO XML. The configuration screen should look like this in Solution Manager/Integration/IFS Connect/Setup IFS Connect:

Step 3: Setup Broadcasts

Please refer to the section BDR for PSO in IFS Applications Online Documentation. The activity to be used is Define Broadcast.

Note: Please note that you have to set up the basic data requirements for this activity.

Step 4: Setup Datasets

Please refer to the section BDR for PSO in IFS Applications Online Documentation. The activity to be used is Define Dataset.

Note: Please note that you have to set up the basic data requirements for this activity.

Step 5: Configure the integration interface user

When utilizing Receive Scheduling Request - HTTP routing rule, a specific system user must be created in IFS Applications to handle HTTP requests. This user must have access to the permission set SCH360_WEBSERVICE.

Note: This user must also exist as a Company User and Site User for the sites used for the integration.

Step 6: Setup and Configure Scheduled Tasks for Load- and Change Messages for the Dataset

Please refer to the section BDR for PSO in IFS Applications Online Documentation. The activity to be used is Set up a Scheduled Task for transferring data to PSO.

Note: Please note that you have to set up the basic data requirements for this activity.

Step 7: Configure Default Parameters for the PSO Integration

Please refer to the section BDR for PSO in IFS Applications Online Documentation. The activity to be used is Define Scheduling Configuration.

Note: Please note that you have to set up the basic data requirements for this activity.

Step 8: Configure PSO software to support the IFS PSO Integration

SPECIFIC PSO CONFIGURATION FOR IFS INTEGRATION

The PSO software when used by the IFS integration is set up in a specific way. The following configurations need to be imported into PSO:

• IFS Language (Language Files/MessageTexts-en-IFS.xml)
• IFS Parameters (Setup Files/IFS APP10 Configuration.xml)

For information on how to import the configuration files, please refer to the PSO Installation Guide.
 

SETTING UP IFS SITES TO BE USED IN PSO

In PSO, permission groups defines which users that are allowed to see a set of resources (IFS Employees) and activities (IFS Work Orders). These permission groups are called object groups. In the integration, object groups has the equivalence of IFS Sites. This means that in order for an PSO user to be able to see information like resources and activities belonging to a particular site, the user must be connected to the corresponding object group in PSO. Object groups for activities and resources are automatically transferred from IFS to PSO but object groups for the PSO users must be set up and granted to the PSO users manually from the PSO SWB. The usage of object groups can be controlled with the parameter Object Group Filter in Scheduling Configuration (see Step 7 above).

HIERARCHICAL TRAVEL MATRIX (HTM)

To optimize the PSO travel calculations, please install PSO Hierarchical Travel Matrix (HTM) for the preferred geographical area. For information on how to install the PSO Hierarchical Travel Matrix (HTM), please refer to document PSO Installation Guide.

Troubleshooting Guide

Use the following logging tools for tracking down a possible problem in the integration:

• Data is transferred to from IFS to PSO using XML messages. These messages are created using background jobs. To verify that the XML messages has been created and placed in the application messages queue, please examine the corresponding background job log in My Administration/Background Jobs.
• The XML message is transferred to the PSO server using IFS Connect. In order to verify that, the message has been sent and received by PSO, please examine the application message in its corresponding message queue in Solution Manager/Integration/IFS Connect/Application Messages.
• If using the HTTP Protocol for transferring the message, please verify that the message has been received by the IFS Scheduling Web Interface service for PSO. These logs are found the event viewer in the operating system, hosting the PSO software.
• Once the message has reached the PSO server, it will be consumed by the IFS Schedule Input Manager service. Please verify that this service was able to interpret this file. These logs are found in the event viewer in the operating system, hosting the PSO software.
• Once PSO has interpreted the file, it will try to schedule the data in the file. If any problems occur, these will be displayed in the log called IFS Dynamic Scheduling Engine. These logs are found in the event viewer in the operating system, hosting the PSO software. The IFS Dynamic Scheduling Engine service is usually installed on a separate server.
• When PSO has been able to produce a schedule, it will try to return the result as an XML to IFS. This action is performed by the IFS Scheduling Broadcast Manager service. Please verify that the XML has been created and returned either to the IFS Web Service or to the IFS Connect Input Folder. These logs are found in the event viewer in the operating system, hosting the PSO software.
• If the XML message have been successfully received by IFS Connect, and where possible to interpret by IFS Connect, the message will end up in the defined inbound applications message queue for PSO. Please examine the application message in its corresponding message queue in Solution Manager/Integration/IFS Connect/Application Messages.
• The last step for incoming messages is to again look at the logs in My Administration/Background Jobs. The messages received by IFS Connect will process partly as background jobs.