This chapter covers the following topics:
Note:
If installing adapter solutions for Oracle E-Business Suite but not Oracle PeopleSoft, skip this chapter after completing the steps described in Configuring the Oracle E-Business Suite Plug-In.
Follow these steps to import the Oracle PeopleSoft project, which creates and populates the AXF-related Oracle PeopleSoft tables and enables AXF configuration on Oracle PeopleSoft pages:
Oracle PeopleSoft adapter security is configured through Integration Broker, where you select user name token authentication and then grant AXF access for Oracle PeopleSoft users.
This section covers the following topics:
Follow these main steps to implement web server SSL encryption for the Oracle PeopleSoft adapter:
Importing the AXF_PS_INTEGRATION project into Oracle PeopleSoft also imports the Integration Broker connection information. These components contain information needed to connect from Oracle PeopleSoft to the AXF Server. This section describes how to access this information in the Oracle PeopleSoft web client and edit it to point to the AXF Server.
Follow the steps listed to configure communication between the Integration Broker and AXF in Configuring Communication for Managed Attachments Web Service.
After configuring communication for the appropriate AXF Server version, complete these steps:
Note:
An Oracle PeopleSoft local integration gateway is required for Oracle PeopleSoft external communications. See the Oracle PeopleSoft Enterprise documentation for information about setting up gateways. You can then proceed with configuring the Oracle PeopleSoft service operation to communicate with an AXF server.
If Success is not displayed after pinging the node, encrypt the secureFileKeystorePasswd value under Gateway Properties, as described in the following steps.
Once you have configured the Integration Broker to communicate with AXF, follow these steps to verify its status.
Follow the steps in these sections to grant AXF access to Oracle PeopleSoft users:
During Oracle PeopleSoft project import, the AXF_ROLE is automatically configured. Follow these steps to verify that appropriate Oracle PeopleSoft users have access to AXF functionality. If needed, follow the steps listed to manually add the AXF_ROLE and permissions to Oracle PeopleSoft.
In Oracle PeopleSoft Server, open PeopleTools, then Security, then Permissions & Roles. The Permissions & Roles menu expands to show available options.
Click Roles. The Roles page displays.
Click the Find an Existing Value tab, and then enter AXF as the key.
Click Search. The AXF_ROLE should be displayed. If it is not, follow the steps below to add it.
AXF_ROLE
in the Role Name field and click Add. The Role Name field is cleared and the AXF_ROLE is added. Enter a description if needed and click Save.AXF_PERMS
in the Permission List field, and click Save.After creating the AXF_ROLE in Oracle PeopleSoft, follow these steps to assign the role to all users that require access to AXF functionality.
Note:
You must assign the AXF_ROLE in Oracle PeopleSoft to all users needing access to AXF functionality for AXF calls to process correctly from Oracle PeopleSoft.
AXF_ROLE
in a blank field (clicking the + icon to create a blank row if needed), or click the magnifying glass icon to search for the role.You configure AXF components on Oracle PeopleSoft pages using the Oracle PeopleSoft Application Designer and the AXF tables in Oracle PeopleSoft.
Determining Primary Keys and Business Objects for Oracle PeopleSoft Page
If needed, follow these steps:
In the Oracle PeopleSoft application, navigate to the page to enable.
Press Ctrl+J. In the info page, note the Page and Component entries for the selected page.
Note:
In the latest versions of PeopleTools 8.55, by default Alt+J is the hot key.In the Application Designer, select File/Open and choose Page from the Definition field.
In the Name field, enter the page name you noted in step 2 and click Open.
Select the Order tab at the top.
From the set of fields listed, identify the field that is the most likely unique ID (for example, VOUCHER_ID for Invoice Entry) and note the record name.
The record name is used for the business object value in the PS_AXF_CMD_PARAMS Table (Managed Attachments solution) and PS_AXF_COMMAND_PARAMS Table (Imaging solution).
From the Insert menu, choose the Definitions into Project command, and select Records from the Definition Type field.
In the Name field, enter the record name you noted in step 6 and click Insert.
Select the record in the list and click Insert. The record is inserted into the Project Tree on the left.
Expand the Records tree on the left, then expand the record you added. The primary keys are listed at the top, with a gold key icon to the left of the key name. Note the primary keys.
Sample primary keys
Table 3-1 Sample Primary Keys
Pages | Page Name | Record Name | Primary Key |
---|---|---|---|
Maintenance Management > Work Order Management > Work Order |
WM_WO_HDR |
WM_WO_HDR |
BUSINESS_UNIT |
Maintenance Management > Work Order Management > Work Order |
WM_WO_HDR |
WM_WO_HDR |
WO_ID |
Customer Contracts > Create and Amend > General Information |
CA_HDR_PNL |
CA_CONTR_HDR |
BUSINESS_UNIT |
Customer Contracts > Create and Amend > General Information |
CA_HDR_PNL |
CA_CONTR_HDR |
CONTRACT_NUM |
Purchasing > Requisitions > Add/Update Requisitions |
REQ_FORM |
REQ_HDR |
BUSINESS_UNIT |
Purchasing > Requisitions > Add/Update Requisitions |
REQ_FORM |
REQ_HDR |
REQ_ID |
About Placing AXF Components on Oracle PeopleSoft Pages
There are two categories of AXF components for use on Oracle PeopleSoft pages:
User interface items refer to AXF buttons, links, and menus you place on an Oracle PeopleSoft page. Five of each are provided (for example, AXF_BUTTON_1 through _5). The Managed Attachments solution uses these user interface items only.
A user interface item becomes active when positioned on a page. If AXF_BUTTON_1 is placed on multiple pages in the same Oracle PeopleSoft component, it shares the same configuration across the pages. To configure different actions for each page in the same component, use a different user interface item (for example, AXF_BUTTON_2). Note that you can reuse user interface items on different Oracle PeopleSoft components without conflicts.
System event components refer to pre- and post-save items you place on an Oracle PeopleSoft page that trigger a pre- or post-save system event. The Imaging solution uses both user interface and system event items.
System events, like user interface items, are configured at the Oracle PeopleSoft component level. However, because they are not visible to the user, they are triggered when appropriate regardless of the page on which they are placed. For example, the AXF_POST_SAVE_SBP and the AXF_PRE_SAVE_SBP items are placed on specific pages; if a Save event occurs on a page in an Oracle PeopleSoft component that is being saved, the configured command executes.
The AXF_POST_SAVE_SBP item captures SAVE_POST_CHANGE system events, which execute a configured command after an Oracle PeopleSoft component is saved.
For example, you might configure a SaveInvoice command to invoke during the SAVE_POST_CHANGE event, so that whenever an action inserts a new Oracle PeopleSoft transaction record, the SaveInvoice command automatically performs a save.
The AXF_PRE_SAVE_SBP item captures SAVE_PRE_CHANGE system events, which execute a configured command before an Oracle PeopleSoft component is saved.
Steps For Placing AXF Components on Oracle PeopleSoft Pages
Following are the steps for placing AXF components on Oracle PeopleSoft pages:
The AXF Oracle PeopleSoft adapter uses standard apache log4j logging. You can activate and manage logging through the log4j.properties file. This file is located in the PeopleSoft Installation Directory
/appserv/classes
directory. Set the following options:
# A1 is set to be a ConsoleAppender which outputs to System.out. log4j.appender.A1=org.apache.log4j.DailyRollingFileAppender log4j.appender.A1.File=./LOGS/PS_AXF.log # A1 uses PatternLayout. log4j.appender.A1.layout=org.apache.log4j.PatternLayout log4j.appender.A1.DatePattern=.yyyy-MM-dd log4j.appender.A1.layout.ConversionPattern=%{dDATE} [%t] %-5p %c %x - %m%n log4j.category.com.oracle.axf=DEBUG, A1
At a minimum, define an appender with a valid file location, and the level of messages to report (see above). Valid levels include the following in order of decreasing detail, where DEBUG displays all messages and detail:
DEBUG
INFO
WARN
ERROR
FATAL
Note:
For detailed information about log4j, see the log4j documentation.
See these sections listed below for additional tasks to configure each solution. After placing a component on an Oracle PeopleSoft page, a key task is to configure the AXF-related Oracle PeopleSoft tables to associate a command with the newly added button, link, or event.
For the Imaging Solution
Configure the Imaging solution as described in Configuring the BPEL Imaging Solution. Configure AXF-related Oracle PeopleSoft tables as described in Oracle PeopleSoft Tables For the BPEL Imaging Solution or apply a solution accelerator as described in Configuring the AXF Tables or Applying a Solution Accelerator.
Specify an Oracle PeopleSoft role in the PS_AXF_COMMANDS Table to either grant users permission to use a specified user interface item or allow a specified system event to trigger for a user.
For the Managed Attachments Solution
Configure the Managed Attachments solution as described in Configuring the Managed Attachments Solution.
Make entries or changes to the PeopleSoft AXF tables listed in Oracle PeopleSoft Tables For the Managed Attachments Solution. Running the sample script described in Enabling Managed Attachments for Oracle PeopleSoft populates the tables with sample values that you can modify. You must enter this information:
Enter the primary page keys you noted in Placing AXF Components on Oracle PeopleSoft Pages.
Specify an Oracle PeopleSoft role in the PS_AXF_COMMANDS Table to grant users permission to use a specified user interface item.