Preparing to Run the Portal Registry Load Process

This topic discusses preparing to run the portal registry load process.

Page Name

Definition Name

Usage

Node Definition - Routings Page

IB_NODEROUTINGS

Activate a routing definition on the default local node.

For additional information, see PeopleTools: Integration Broker, “Managing Service Operation Routing Definitions,” Adding Routing Definitions, Adding Routing Definitions Using the Nodes Component.

File Inbound Page

EO_FILE_INBOUND

Define inbound file processing.

For additional information, see PeopleSoft Integration Interfaces, “Using the Flat File Utility,” Initiating File Processing, File Inbound Page

Inbound File Publish Page

EO_FILETOMSG

Initiate file-to-message processing. The file-to-message processing function reads the file rowset and publishes it as a message.

For additional information, see PeopleSoft Integration Interfaces, “Using the Flat File Utility,” Initiating File Processing, Inbound File Publish Page

Monitor Overview Page

IB_MONITOR_OVRVIEW

Review the status of the service operation.

For additional information, see PeopleTools: Integration Broker Service Operations Monitor, “Monitoring Asynchronous Service Operations,” Monitoring Asynchronous Service Operation Transactions.

To set up the portal registry load message:

  1. In the browser, access the Node Definitions page (PeopleTools, Portal, Node Definitions)..

  2. Select the default local node for PeopleSoft Interaction Hub, which is PSFT_PA.

  3. Select the Routings page.

  4. Click the Find link in the grid and search for PORTAL_REG_LOAD.

  5. Activate one of the generated routing definitions.

  6. Click Save to save the node definition.

To define inbound file processing:

  1. Access the File Inbound page (Enterprise Components, Integration Definitions, Inbound File Rule)..

  2. Select the PORTAL_REG_LOAD file identifier.

  3. In the Inbound File field, enter the directory information for the file location on the application server machine.

    Note: The inbound file portal_reg_load_sample.csv must reside in a directory that is accessible to the application server.

  4. Set the Status field to Active.

  5. Clear the Create Message Header and Create Message Trailer options.

  6. Save the definition.

To run the Inbound File Publish Application Engine process (EOP_PUBLISHF):

  1. Access the Inbound File Publish page (Enterprise Components, Integration Definitions, Initiate Processes, Inbound File Publish).

  2. Add or enter an existing run control ID.

  3. Enter a request ID and description.

  4. In the Process Frequency group box, select Once .

  5. Select the file identifier that you created on the File Inbound page.

  6. Click Save.

  7. Click Run. Record the process instance number.

  8. Click the Process Monitor link to monitor the status of the process.

To monitor the service operation:

  1. Access the Monitor Overview page (PeopleTools, Integration Broker, Service Operations Monitor, Monitoring, Asynchronous Services.

  2. Check the queue status for the PORTAL_REGISTRY queue.