Oracle Public Sector Revenue Management Self Service Installation Guide

Release 1.1.0

E53302-01

June 2014

Copyright © 2012, 2014, Oracle and/or its affiliates. All rights reserved.

Documentation build: 6.22.2014 9:42:53 [TS_1403455373000]

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Installation Overview

This guide describes the installation steps that must be completed in order to use Public Sector Revenue Management Self Service (PSRMSS) integrated with Oracle Public Sector Revenue Management (PSRM).

Note: This document is subject to revision and updating. For the most recent version of this document and related documentation check BUG 18601054.

- Additional Resources

- Abbreviations

- PSRMSS Installation and Configuration Flowchart

- Software Requirements

Additional Resources

For more information on products related to PSRMSS installation, see the following documents:

Resource

Location

Oracle WebCenter documentation

http://www.oracle.com/technetwork/middleware/webcenter/portal/documentation/index.html

Oracle Java Sun JDK

http://www.oracle.com/technetwork/indexes/documentation/index.html

Oracle JRockit

http://www.oracle.com/technetwork/middleware/jrockit/documentation/index.html

Oracle SOA Suite documentation

http://www.oracle.com/technetwork/middleware/soasuite/documentation/index.html

Oracle UCM Documentation

http://www.oracle.com/technetwork/middleware/webcenter/content/documentation/index.html

Oracle Fusion Middleware Requirements

http://docs.oracle.com/cd/E12839_01/install.1111/e12001/overview.htm#BABDFJAB

Oracle WebLogic Documentation

http://www.oracle.com/technetwork/middleware/weblogic/documentation/index.html

Oracle Policy Automation

http://www.oracle.com/technetwork/apps-tech/policy-automation/downloads/index.html

Oracle OIM Overview

http://www.oracle.com/technetwork/middleware/id-mgmt/overview/index-098451.html

Oracle OUD Overview

http://www.oracle.com/technetwork/middleware/id-mgmt/overview/oud-433568.html

Oracle Public Sector Revenue Management Documentation Library

http://www.oracle.com/technetwork/documentation/pubsectrevmgmt-154608.html

Abbreviations

ADF

Application Development Framework

BPEL

Business Process Execution Language

DDL

Data Definition Language

EAR

Enterprise Archive

EM/OEM

Oracle Enterprise Manager

MDS

Metadata Services

OIM

Oracle Identity Management

OPA

Oracle Policy Automation

OUD

Oracle Unified Directory

OUI

Oracle Universal Installer

OWSM

Oracle Web Services Manager

PSRMSS

Oracle Public Sector Revenue Management Self Service

PSRM

Oracle Public Sector Revenue Management

RCU

Repository Creation Utility

SOA

Service Oriented Architecture

WC

Oracle WebCenter

WLS

Oracle WebLogic Server

PSRMSS Installation and Configuration Flowchart

Software Requirements

The following software must be installed and configured prior to installation of Oracle PSRM Self Service:

- Oracle RCU Database 11.1.1.6.0

- Oracle WebLogic Server 10.3.6

- Oracle WebCenter Release 11.1.1.6.0

- Oracle Content Server (UCM) 11.1.1.6.0

- Oracle SOA 11.1.1.6.0

Optional installations:

- Oracle BI Publisher 11.1.1.7.0

- Oracle OIM 11.1.2.x

- Oracle OUD 11.1.2.x

- Oracle OPA 10.4.4.21

When using PSRM as your back-end data management system:

- Oracle Public Sector Revenue Management Release 2.3.1.2.0

- PSRM Service Pack 2 - BUG 18845734

- Oracle Documaker 12.0.x

PSRMSS Installation

- Types of Installation Packages

- Pre-Installation Tasks

Types of Installation Packages

Installation Type

Description

Demo installation

Refer to PSRMSS Bug 18978475 for the latest demo download installation for PSRMSS and the demo components available for PSRM.

Pre-integrated with PSRM 2.3.1.2.

This type of installation renders PSRMSS 1.1 integrated with PSRM 2.3.1.2.

Standalone installation (PSRMSS and PSRMSS-<EDGE-PROD> Integration)

This type of installation renders a standalone PSRMSS 1.1 instance.

Note: Each package has the same basic installation procedure.

Pre-Installation Tasks

The following applications, scripts, and utilities must be installed or run in the recommended order prior to installing PSRMSS:

1. Install Oracle RCU database components (see Appendix B for additional details).

Note: This installation requires that you create an additional empty MDS schema for PSRMSS.

2. Install Oracle WebLogic 11.1.1.6

3. Install Oracle WebCenter 11.1.1.6

4. Install Oracle UCM 11.1.1.6

5. Install Oracle SOA 11.1.1.6

6. Create and configure a new Oracle WebLogic domain for Oracle WebCenter, Oracle UCM, and Oracle SOA (see Appendix C for additional details).

7. Ensure that Oracle WebLogic Admin Server 11.1.1.6 is running.

Note: The following servers should be installed prior to installing PSRMSS (all should be installed and configured through the installations noted above). See Appendix E for additional details.

- UCM_server1

- WC_Portlet

- WC_Spaces

- WC_Utilities

- soa_server1

8. Ensure that the Node Manager is running to start and stop servers.

When starting Node Manager for the first time you will need to run the setNMProps script to set StartScriptEnabled=true in the nodemanager.properties file:

On UNIX/Linux:

MW_HOME/oracle_common/common/bin/setNMProps.sh

On Windows:

MW_HOME \ORACLE_COMMON\common\bin\setNMProps.cmd

Note: MW_HOME is set after initializing the setWLSEnv script for either OS.

For subsequent Node Manager starts, navigate to WL_HOME/server/bin and enter:

On UNIX/Linux:

./startNodeManager.sh

On Windows:

startNodeManager.cmd

When Node Manager starts, it reads the nodemanager.properties file with the StartScriptEnabled=true property, and uses the start scripts when it subsequently starts the managed servers.

The script setNMProps only needs to be executed once.

9. Verify that the Oracle WebLogic Admin Server is running, and you are able to access the WebLogic console:

http://<administration_server_host>:<administration_server_port>/console

Installing Integrations

- Integration Pre-Installation Tasks

- Integrated Flows Installation Directory Structure

- Completing the Integration Installation

- Post-Integration Configuration Tasks

- Updating the Worklist Application

- Post-Integration Checklist

- Accessing the Worklist Application

- PSRMSS Installation Directory Structure

Integration Pre-Installation Tasks

The following tasks should be completed before you install PSRMSS-PSRM integrated flows:

- Extract the PSRMSS BPEL integration package to a local destination. This destination will be referred to as the PRODUCT_HOME for this installation.

- Ensure that the Oracle SOA Suite is installed and running.

Note: For additional information on SOA, see http://www.oracle.com/technetwork/middleware/soasuite/documentation/index.html#111130

- Log in to the WebLogic console to confirm there are no changes in Pending Activation status.

- Restart the Enterprise Manager and the WebLogic Administration servers.

- Ensure that the WebLogic Admin server, SOA server, and Node Manager are running.

- Ensure that PSRM V2.3.1.2.0 is properly installed and configured.

Integrated Flows Installation Directory Structure

This folder includes a subfolder hierarchy as shown in the following image:

Note: If any of the folders are read-only, remove the read-only attribute from the folder.

- bin contains the scripts to launch the installation utility (one script each for Linux and for Windows):

File

Description

InstallBuild.xml

This is the deployment and installation driver file.

DeployUndeployUtility.xml

This is the deployment driver file for the MDS repository.

install.sh

Install script for Linux.

- config contains the installation configuration file. This file must be updated with the environment configuration prior running the installer (see Appendix A for details on SOA InstallProperties.)

File

Description

InstallProperties.xml

Install parameters file.

- Install contains the work file for the application, installation property files, and installation utilities.

- MDS-Artifacts contains the artifacts that will be uploaded into the MDS repository.

- services contains the services that will be compiled and deployed to the soa-server.

Completing the Integration Installation

1. Download the installation from the Oracle Software Delivery Cloud (edelivery.oracle.com) and unjar into a target installation directory:

Example:

jar –xvf BPEL-Release-V1.1.0.0.0-<<Install-Type>>.jar

Note: You must have the platform-appropriate Java JDK installed on the machine on which the Integration Installation package is unzipped.

2. Set the following environment variables (see Appendix I for a PSRMSS-PSRM Integration environment settings example):

Variable

Example

SOA_HOME

<BEA_HOME>Oracle_SOA1

ORACLE_HOME

<BEA_HOME>Oracle_SOA1

MW_HOME

<WebLogic_HOME>/Middleware

WL_HOME

<BEA_HOME>//wlserver_10.3

PRODUCT_HOME

This is the BPEL PSRMSS-PSRM product installation home.

Linux Example:

PRODUCT_HOME=/psrmss/PSRM-SS/BPEL-Release-V1.1.0.0.0-Release-InitialInstall/OTSS-ETPM

Windows Example:

PRODUCT_HOME=D:\psrmss\PSRM-SS\BPEL-Release-V1.1.0.0.0-Release-InitialInstall\OTSS-ETPM

3. Update the <PRODUCT_HOME>/config/InstallProperties.xml file with values appropriate to your environment (see Appendix A, BPEL/SOA for a sample InstallProperties.xml file and an explanation of the properties and elements available in the file).

4. Run the setWLSEnv script to set the environment variables for executing the installation scripts.

On UNIX/Linux:

source "${WL_HOME}/wlserver_10.3/server/bin/setWLSEnv.sh"

On Windows:

cd %WL_HOME%\wlsserver_10.3\server\bin\

setWLSEnv.cmd

5. Execute the following installation scripts for your OS to copy the files from the downloaded directory (PRODUCT_HOME) to the appropriate locations in MW_HOME

6. Change (cd) to the <PRODUCT_HOME>/bin directory.

Note: The following ant command should be entered on one line. No output will be echoed to the screen; refer to the log file to check progress.

On UNIX/Linux:

cd $PRODUCT_HOME/bin

./install.sh -install

On Windows:

Note: The following ant command should be entered on one line.

cd %PRODUCT_HOME%\bin

ant -f InstallBuild.xml -DInstallProperties=%PRODUCT_HOME%\config\InstallProperties.xml -l installBPEL-PSRMSS.log

When running the command, examine InstallBPEL_<DATE_TIME> for any build errors. If "BUILD SUCCESSFUL" does not appear at the end of the file, fix any errors listed in the log before proceeding.

7. Execute the following installation scripts in a command window for your OS to deploy MDS.

On UNIX/Linux:

cd $PRODUCT_HOME/bin

./install.sh -deployMDS

On Windows:

Note: The following ant command should be entered on one line.

cd %PRODUCT_HOME%\bin

ant -f =%PRODUCT_HOME%\bin\DeployUndeployUtility.xml

-DInstallProperties==%PRODUCT_HOME%\config\InstallProperties.xml DeployMDS

Note: Once the installation has been completed successfully, it is recommended that you copy the installation log file produced into a secure location.

8. Restart both the WebLogic Admin server and the SOA server to activate the installation, then perform the tasks listed in the Post-Integration Configuration Tasks section of this document.

Post-Integration Configuration Tasks

The following describes items that must be configured after a successful installation of the BPEL Integration.

1. Log in into the Oracle Enterprise Manager console at http://WLSAdminHost:WLSAdminServerPort/em with your wlsadminuser/wlsadminpasswd credentials

2. Expand the Farm_soa_domain > soa > soa-infra OTSS-ETPM partition.

3. Navigate to the OTSSReportReconciliationRequestEBF Composite. Right-click and select Service/Reference > OTSSReportReconciliationFileAdapter:

4. On the Properties tab, enter a value in the FilePath field:

Note: This FilePath will be the location where the OPC reconciliation reports will be placed, so this directory must be readable and accessible.

5. Click Apply.

Updating the Worklist Application

1. Log in into the Oracle Enterprise Manager console at http://WLSAdminHost:WLSAdminServerPort/em with your wlsadminuser/wlsadminpasswd credentials

2. Expand the Farm_soa_domain > soa > soa-infra OTSS-ETPM partition.

3. Navigate to the OTSSUserAccessApprovalService Composite.

4. On the Dashboard tab, navigate to the BlockedUserAccessApprovalTask and OnHoldUserAccessApprovalTask components. Configure each component using the details provided in the next step.

5. On the Administration tab, add the URI configuration for the task details for each component:

For the BlockedUserAccessApprovalTask:

- Application Name: worklist

- Host Name: The server host name on which the worklist application is deployed (e.g., the soa_host)

- HTTP Port: The port number for the worklist application (e.g., the soa port number)

- HTTPS Port:

- URI: /workflow/OTSSBlockedUserAccessApprovalTask/faces/adf.task-flow?_id=BlockedUserAccessApprovalTask_TaskFlow&_document=WEB-INF/BlockedUserAccessApprovalTask_TaskFlow.xml

Click Apply after providing the URI details for the changes to take effect.

For the OnHoldUserAccessApprovalTask:

- Application Name: worklist

- Host Name: The server host name on which the worklist application is deployed.

- HTTP Port: The port number for the worklist application (e.g., 8001).

- HTTPS Port:

- URI: /workflow/OTSSOnHoldUserAccessApprovalTask/faces/adf.task-flow?_id=OnHoldUserAccessApprovalTask_TaskFlow&_document=WEB-INF/OnHoldUserAccessApprovalTask_TaskFlow.xml

Click Apply after providing the URI details for the changes to take effect.

Post-Integration Checklist

This section describes procedures to verify integration of the PSRMSS-PSRM flows.

- Verifying Creation of the OTSS-SOADS and OTSS-USRACS Data Sources

- Verifying Creation of the JMS Modules

- Verifying Creation of the Outbound Connection Pools

- Verifying the Composites in Enterprise Manager

- Verifying Worklist Applications Deployment

- Verifying Creation of Keys

Verifying Creation of the OTSS-SOADS and OTSS-USRACS Data Sources

1. Log in to the Oracle WebLogic Server console at http://WLSHostName:WLSAdminServerPort/console with your weblogicAdminUser/weblogicAdminPassword credentials.

2. Select the <soa-domain>, then expand Services, and click Data Sources.

The list of data sources should include OTSS-SOADS and OTSS-USRACS, as shown in the following image:

Verifying Creation of the JMS Modules

1. Log in to the Oracle WebLogic Server console at http://WLSHostName:WLSAdminServerPort/console with your weblogicAdminUser/weblogicAdminPassword credentials.

2. Select the <soa_domain>, expand Messaging, and click JMS Modules.

The list of JMS Modules should include OTSSETPMJMSModule, as shown in the following image:

3. Click OTSSETPMJMSModule.

The Summary of Resources is displayed:

The list of resources should include the following:

- OTSSCreateEnrollment

- OTSSPSRMConnectionFactory

- OTSSPaymentPosting

- OTSSPaymentPostingError

- OTSSPaymentReport

- OTSSPaymentReportError

- OTSSProcessRegistrationForm

- OTSSProcessTaxForm

- OTSSServiceRequest

- OTSSServiceRequestError

Verifying Creation of the Outbound Connection Pools

1. Log in to the Oracle WebLogic Server console at http://WLSHostName:WLSAdminServerPort/console with your weblogicAdminUser/weblogicAdminPassword credentials.

2. Select the <soa-domain>, then click on Deployments, and click the deployment for DbAdapter, as shown in the following image:

3. Click Configuration – Outbound Connection Pools, with a Group and Instance of eis/DB/OTSS-SOADS1 and eis/DB/OTSS-USRACS, as shown in the following image:

Verifying the Composites in Enterprise Manager

To verify that the OTSS-ETPM partition was created with all composites deployed:

1. Log in into the Oracle Enterprise Manager console at http://WLSAdminHost:WLSAdminServerPort/em with your wlsadminuser/wlsadminpasswd credentials.

2. Expand the Farm_<domain-name>_domain > soa > soa-infra OTSS-PSRM partition.

3. Verify that following composites are deployed (there should be a total of 48):

- OTSSProcessTaxFormServiceProvider [1.0]

- OTSSCreateEnrollmentJMSProducer [1.0]

- OTSSRequestStatusInquiryEBF [1.0]

- OTSSPaymentPostingRequestProvider [1.0]

- OTSSRefundStatusInquiryEBF [1.0]

- OTSSGetTaxAccountAlertsEBF [1.0]

- OTSSServiceRequestJMSConsumer [1.0]

- OTSSRefreshFormLookupEBF [1.0]

- OTSSProcessRegistrationFormJMSProducer [1.0]

- OTSSCreateEnrollmentServiceProvider [1.0]

- OTSSProcessRegistrationFormJMSConsumer [1.0]

- OTSSProcessRegistrationFormEBF [1.0]

- OTSSAddressMaintenanceEBF [1.0]

- OTSSPaymentPostingRequestEBF [1.0]

- OTSSTaxpayerServiceRequestProvider [1.0]

- OTSSGetTaxpayerContactInfoEBF [1.0]

- OTSSProcessRegistrationFormServiceProvider [1.0]

- OTSSFormValidationService [1.0]

- OTSSSummaryEnrollmentEBF [1.0]

- OTSSGetFilingHistoryEBF [1.0]

- OTSSIdentifyTaxpayerEBF [1.0]

- OTSSGetTaxpayerCorrespondenceInfoEBF [1.0]

- OTSSUserAccessService [1.0]

- OTSSRetrieveFormTypeDefinitionsEBF [1.0]

- OTSSReportReconciliationRequestProvider [1.0]

- OTSSPrintFormEBF [1.0]

- OTSSGetPaymentHistoryEBF [1.0]

- OTSSBase64EncodeDataService [1.0]

- OTSSFormUploadEBF [1.0]

- OTSSEnrollmentIDService [1.0]

- OTSSRetrieveActiveFormTypesEBF [1.0]

- OTSSTaxpayerServiceRequestEBF [1.0]

- OTSSUserAccessApprovalService [1.0]

- OTSSProcessTaxFormEBF [1.0]

- OTSSQueryPaymentsDueEBF [1.0]

- OTSSDocumentLocatorNumberService [1.0]

- OTSSCreateEnrollmentEBF [1.0]

- OTSSCreateEnrollmentJMSConsumer [1.0]

- OTSSGetExternalPaymentDataEBF [1.0]

- OTSSReportReconciliationRequestEBF [1.0]

- OTSSProcessTaxFormJMSConsumer [1.0]

- OTSSQueryEnrollmentEBF [1.0]

- OTSSGetTaxpayerSummaryEBF [1.0]

- OTSSProcessTaxFormJMSProducer [1.0]

- OTSSGetTaxAccountSummaryEBF [1.0]

- OTSSConfirmationIdService [1.0]

- OTSSPaymentEBF [1.0]

- OTSSServiceRequestJMSProducer [1.0]

Verifying Worklist Applications Deployment

1. Log in to the Oracle WebLogic Server console at http://WLSHostName:WLSAdminServerPort/console with your weblogicAdminUser/weblogicAdminPassword credentials.

2. Expand the Farm_<domain-name>_domain > Application Deployments .

3. Verify that following two Applications are displayed:

- OTSSBlockedUserAccessApprovalTask

- OTSSOnHoldUserAccessApprovalTask

Verifying Creation of Keys

To verify that the PSRMSS_RMSYS and PSRMSS_EXTUCM keys have been created:

1. Log in to the Oracle WebLogic Server console at http://WLSHostName:WLSAdminServerPort/console with your weblogicAdminUser/weblogicAdminPassword credentials.

2. Expand the Farm_<domain-name>_domain > WebLogic Domain > Domain Name > Security > Credentials .

3. Expand oracle.wsm.security

Two keys should be listed:

- PSRMSS_EXTUCM

- PSRMSS_RMSYS

Accessing the Worklist Application

To access the Worklist application after a successful installation:

User

http/s://<soa-server>:<soa-port>/integration/worklistapp/faces/login.jspx

PSRMSS Installation Directory Structure

The product installation directory contains the following hierarchy:

- bin contains the scripts to launch the installation utility. Two scripts are provided (one each for Windows and for Linux):

File

Description

install.sh

Install script for Linux

install.cmd

Install script for Windows

- config contains the installation configuration file. This file must be updated with the environment configuration prior running the installer (for details, see Appendix F).

File

Description

PSRM-SS-InstallProperties.xml

Installation parameters file.

- Install contains the PSRMSS application, installation property files, and installation utilities.

- Log contains the log for the installation utility.

If any of the folders are read-only, remove the read-only attribute from the folder.

PSRMSS Product Installation

This topic describes the basic installation procedure for PSRMSS.

1. Download PSRMSS-Release-V1.1.0.0.0<<Install-Type>>.jar from the from the Oracle Software Delivery Cloud (edelivery.oracle.com) and unjar into a target installation directory:

Example: jar –xvf PSRMSS-Release-V1.1.0.0.0<<Install-Type>>.jar

Linux example:

/PSRM-SS/PSRM-SS-ProductInstall

Windows example:

D:\PSRM-SS\PSRM-SS-ProductInstall

You must have the platform-appropriate Java JDK installed on the machine on which the PSRMSS package is unjarred.

2. Set the PRODUCT_HOME environment variable to point to PSRM-SS-Product-Install:

Linux example:

export PRODUCT_HOME=/PSRMSS/PSRM-SS-Release-V1.1.0.0.0

echo $PRODUCT_HOME

echo should return PRODUCT_HOME as the location of the top-level directory of the installation media, e.g., /PSRMSS/PSRM-SS-Release-V1.1.0.0.0.

Windows example:

SET PRODUCT_HOME=D:\PSRMSS\PSRM-SS-Release-V1.1.0.0.0

echo %PRODUCT_HOME%

echo should return PRODUCT_HOME as location of the top level directory of the installation media, e.g., D:\PSRMSS\PSRM-SS-Release-V1.1.0.0.0.

See Appendix J for a PSRMSS environment settings example.

3. Set the WebLogic server environment by running the setWLSEnv script. The scripts are located in <WEBLOGIC_HOME>\wlserver_10.3\server\bin.

Linux example:

source /PSRMSS/weblogic-10.3.6/wlserver_10.3/server/bin/setWLSEnv.sh

Windows example:

run D:\weblogic-10.3.6\wlserver_10.3\server\bin\setWLSEnv.cmd

After running the script, verify that the wlserver environment is set in your classpath and path environment variables.

4. Update the <PRODUCT_HOME>/config/PSRM-SS-InstallProperties.xml file with values appropriate to your environment (see Appendix F for a sample PSRM-SS-InstallProperties.xml file and an explanation of the properties and elements available in the file).

5. Execute following command to change to PRODUCT_HOME/bin:

On Linux:

source /PSRMSS/weblogic-10.3.6/wlserver_10.3/server/bin/setWLSEnv.sh

On Windows:

cd %PRODUCT_HOME%\bin

Important: Before proceeding to the final step, ensure that both the Admin server and Node Manager are up and running.

6. Run the installation script to install PSRMSS.

On Linux:

./install.sh -i

Note: You must change the access permissions on install.sh using the command chmod 755.

On Windows:

install.cmd -i

The following message is displayed on a successful installation of PSRMSS:

-----------------------------------------------------------

Installation of PSRM-SS V1.1.0.0.0 is Successful

-----------------------------------------------------------

If any message appears that indicates an unsuccessful installation after executing the installation utility, see Appendix G, Installer Utility Overview.

- Post-Installation Tasks

Post-Installation Tasks

- Verifying the Installation

- Accessing the PSRMSS Application

- Configuring UCM for PSRMSS

- Configuring SSL for a PSRMSS Server

Verifying the Installation

The following topics comprise a verification checklist for the PSRMSS installation.

- Verifying ADF Connections for the PSRMSS Application

- Verifying the PSRMSS Schema Tables

- Verifying Creation of the PSRMSS Server

- Verifying the WSSDS Data Source

- Verifying the mds-PSRMSS_MDS Data Source

- Verifying the PSRMSSFormsAdmin Group

- Verifying wasadmin User Creation

- Verifying Successful Application Deployment

- Verifying Successful Key Creation

Verifying ADF Connections for the PSRMSS Application

To configure and verify that the PSRMSS application WSDLs are correctly tokenized and OWSM Policies are correctly set:

1. Log in into the Oracle Enterprise Manager console at http://WLSAdminHost:WLSAdminServerPort/em with your wlsadminuser/wlsadminpasswd credentials.

2. Select Application Deployments, choose PSRMSS, then right-click and choose ADF > Configure ADF Connections from the context menu as shown in the following image:

3. Select a Connection Name, then right-click Advanced Connection Configuration:

4. Click on the OWSM tab. Check that the Directly Attached Policies section contains the correct policy and that the value of csf-key is PSRMSS_BPEL in the Security Configuration Details section.

Note: If the correct policies are not properly attached to the Web Service Connection, see the troubleshooting section in this document on this subject under the heading, "ADF Connection strings are not properly updated".

5. Click on the Configuration tab. Check that the Endpoint Address has been properly updated to the correct endpoint address for your implementation.

Verifying the PSRMSS Schema Tables

1. Log in into the database with the PSRMSS dbuser/passwd credentials that you created during the installation process.

2. Verify that the following tables exist by executing the following query:

select table_name from user_tables order by table_name;

Results should be:

"PS_TXN"

"TS_ACCESS_TYPE"

"TS_ACCESS_TYPE_L"

"TS_ACCESS_TYPE_SUMMARY"

"TS_ADDRESS_CONFIG"

"TS_ADDRESS_CONFIG_FIELD"

"TS_ALERT_TYPE"

"TS_ALERT_TYPE_L"

"TS_CONFIGURATION"

"TS_EMAIL_DEFINITION"

"TS_EMAIL_DEFINITION_L"

"TS_FIELD"

"TS_FIELD_L"

"TS_FORM_ACTION"

"TS_FORM_COLUMN_WORK"

"TS_FORM_CUSTOM_PROPERTY"

"TS_FORM_DATATYPE"

"TS_FORM_DEFINITION"

"TS_FORM_DEFINITION_L"

"TS_FORM_LINE_WORK"

"TS_FORM_PROCESS_CONTROL"

"TS_FORM_SECTION_WORK"

"TS_FORM_VAL_RULE"

"TS_FORM_VERSION"

"TS_FORM_WORK"

"TS_INTERVIEW"

"TS_INTERVIEW_L"

"TS_INTERVIEW_SET"

"TS_INTERVIEW_SET_L"

"TS_LANGUAGE"

"TS_LINE_OF_BUSINESS"

"TS_LINE_OF_BUSINESS_L"

"TS_LOOKUP"

"TS_LOOKUP_L"

"TS_LOOKUP_VAL"

"TS_LOOKUP_VAL_L"

"TS_MESSAGE"

"TS_MESSAGE_L"

"TS_MESSAGE_PARAMETER"

"TS_PATCH_LOG"

"TS_PAYDEST_CUSTOM_PROPERTY"

"TS_PAYMENT_DESTINATION"

"TS_PAYMENT_DESTINATION_FIELD"

"TS_PAYMENT_DESTINATION_FIELD_L"

"TS_PAYMENT_DESTINATION_L"

"TS_PAYMENT_METHOD"

"TS_PAYMENT_PROVIDER"

"TS_PAYMENT_PROVIDER_L"

"TS_PROPERTY"

"TS_PROPERTY_L"

"TS_SERVICE_REQUEST_DEFN"

"TS_SERVICE_REQUEST_DEFN_L"

"TS_SERVICE_REQUEST_FIELD"

"TS_SERVICE_REQUEST_FIELD_L"

"TS_SVC_REQ_CUSTOM_PROPERTY"

"TS_VALIDATION_RULE"

"TS_VALIDATION_RULE_L"

Verifying Creation of the PSRMSS Server

1. Log in to the Oracle WebLogic Server console at http://WLSHostName:WLSAdminServerPort/console with your weblogicAdminUser/weblogicAdminPassword credentials.

2. Select the <PSRMSS-domainname>, then expand Environment, and click Server.

The server list should include the server name from your installation (as indicated by "psrmss_server1" in this example).

Verifying the WSSDS Data Source

1. Log in to the Oracle WebLogic Server console at http://WLSHostName:WLSAdminServerPort/console with your weblogicAdminUser/weblogicAdminPassword credentials.

2. Select the <PSRMSS-domainname>, then expand Services, and click Data Sources.

The list of data sources should include WSSDS, targeted to your server, as shown in the following image:

Verifying the mds-PSRMSS_MDS Data Source

1. Log in to the Oracle WebLogic Server console at http://WLSHostName:WLSAdminServerPort/console with your weblogicAdminUser/weblogicAdminPassword credentials.

2. Select the <PSRMSS_domain >, then expand Services, and click Data Sources.

The list of data sources should include mds-PSRMSS_MDS, targeted to your server, as shown in the following image:

Verifying the PSRMSSFormsAdmin Group

1. Log in to the Oracle WebLogic Server console at http://WLSHostName:WLSAdminServerPort/console with your weblogicAdminUser/weblogicAdminPassword credentials.

2. Select PSRMSS_domain > Security Realms > myrealm > Users and Groups .

The list of groups should include PSRMSSFormsAdmin and be part of the Administrators group, as shown in the following image:

Verifying wasadmin User Creation

1. Log in to the Oracle WebLogic Server console at http://WLSHostName:WLSAdminServerPort/console with your weblogicAdminUser/weblogicAdminPassword credentials.

2. Select PSRMSS_domain > Security Realms > myrealm > Users and Groups .

The list of users should include wasadmin and be part of the Administrators and PSRMSSFormsAdmin groups, as shown in the following images:

Verifying Successful Application Deployment

1. Log in to the Oracle WebLogic Server console at http://WLSHostName:WLSAdminServerPort/console with your weblogicAdminUser/weblogicAdminPassword credentials.

2. Select the <PSRMSS_domain>, then expand Summary of Deployments.

The list of deployments should include a oracle.psrmss.extension(1.0,1.0) shared library, as shown in the following image:

In addition, the list of deployments should include the PSRMSS application, as shown in the following image:

Verifying Successful Key Creation

1. Log in to the Oracle WebLogic Server console at http://WLSHostName:WLSAdminServerPort/console with your weblogicAdminUser/weblogicAdminPassword credentials.

2. Expand the Farm_<PSRMSS_domain> > WebLogic Domain > Security > Credentials .

3. Expand oracle.wsm.security and verify that the PSRMSS_RMSYS key is listed:

Accessing the PSRMSS Application

To access the PSRMSS application after a successful installation:

User

http/s://<weblogic-Server>:<PSRM-ss-server-port>/PSRMss/faces/pages_home

Admin login page

http/s://<weblogic-Server>:<PSRM-ss-server-port> /PSRMss/faces/oracle/webcenter/portalapp/pages/login.jspx

Main landing page

http/s://<weblogic-Server>:<PSRM-ss-server-port> /PSRMss/faces/oracle/webcenter/portalapp/pages/WSSHome.jspx

Configuring UCM for PSRMSS

- UCM Configuration: Part 1

- UCM Configuration: Part 2

UCM Configuration: Part 1

When the installation process is complete there are a few recommended configuration options that should be set in the UCM server in order to support the ability to include UCM content in the PSRMSS portal pages.

1. Log in to the Oracle UCM at http://WLSAdminHost:UCMServerPortNumber/cs with wlsadminuser/wlsadminpasswd. When this is the first login to the UCM server you will be asked to confirm the settings in order to finalize the installation of UCM. You need only confirm all settings—there is no need to change anything at this point—and proceed according to the instructions on the screen.

2. Restart the UCM Server after settings are confirmed.

3. Login to the UCM server again using the same credentials you used in the previous step. Expand the Administration category in the navigation area, then select the Admin Server option. A new window opens for the admin server.

4. Perform the following configuration steps:

1. Log in to the Oracle UCM cs-admin console using the following URL:

http://ucm_host:ucm_port/cs/idcplg/cs-admin/pxs?IdcService=GET_COMPONENT_DATA

2. In Disabled Components, select:

- folders_g

- FolderStructureArchive

3. Click Enable, then Save.

4. In the Admin Server window, select the Component Manager category in the navigation area, then select the All Features option. Browse down the list of components and ensure that the following are checked:

- WebcenterConfigure

- InboundRefinerySupport

- DynamicConverter

5. Restart the UCM Server.

UCM Configuration: Part 2

Use the following procedure to configure a socket connection for PSRMSS.

Note: The UCM server must be up and running.

1. Log in into the Oracle Enterprise Manager console at http://WLSAdminHost:WLSAdminServerPort/em with wlsadminuser/wlsadminpasswd.

2. Perform the following configuration steps:

1. Choose WebCenter > Content > Content Server , then select Oracle WebCenter Content - Content Server (UCM Server 1)..

2. Right-click and select Configuration.

3. Enter the following in the Server Configuration section:

- Set the Intradoc ServerPort to 4444

- Modify the IP Address Filter list to add either a specific IP address or *.*.*.*

3. Restart the UCM Server.

Configuring SSL for a PSRMSS Server

For details on configuring SSL on a WebLogic server, see Configuring SSL (http://docs.oracle.com/cd/E23943_01/web.1111/e13707/ssl.htm) in the Oracle Fusion Middleware Securing Oracle WebLogic Server documentation.

Note: Implementing SSL is recommended for production environments.

Appendix A

- BPEL/SOA installProperties.xml

BPEL/SOA installProperties.xml

The following listing shows the structure and sample data contained in installProperties.xml.

Security Note : After a successful installation it is recommended that the installProperties.xml file is moved to a secured location. It is also recommended that passwords supplied in the intallProperties.xml file be changed after the installation.

<?xml version="1.0" standalone="yes"?>

<config>

<OTSS-ETPM>

<modulename>OTSS-ETPM</modulename>

<ETPM>

<ApplicationUsername></ApplicationUsername>

<ApplicationPassword></ApplicationPassword>

<AdminServer>

<protocol>http</protocol>

<hostname></hostname>

<portnumber> </portnumber>

<servername>   </servername>

<appcontextroot> </appcontextroot>

<username>  </username>

<password>    </password>

</AdminServer>

<ManagedServer>

<hostname>   </hostname>

<portnumber> </portnumber>

<servername> </servername>

<username> <username>

<password>    </password>

</ManagedServer>

</ETPM>

<WorkFlow.Notification>

<from.emailid> </from.emailid>

</WorkFlow.Notification>

</OTSS-ETPM>

<SOA>

<AdminServer>

<protocol>  </protocol>

<hostname> </hostname>

<portnumber> </portnumber>

<servername> </servername>

<username> </username>

<password> </password>

<domainname> </domainname>

<adminemail> </adminemail>

</AdminServer>

<ManagedServer>

<protocol>  </protocol>

<hostname> </hostname>

<portnumber> </portnumber>

<servername> </servername>

<username>  </username>

<password> </password>

</ManagedServer>

<mdsconfig>

<mdsdbusername> </mdsdbusername>

<mdsdbuserpassword> </mdsdbuserpassword>

<mdsdbhostname> </mdsdbhostname>

<mdsdbportnumber> </mdsdbportnumber>

<mdsdbsid>  </mdsdbsid>

</mdsconfig>

<JMS>

<serverName>OTSSPSRMJMSServer</serverName>

<ModuleName>OTSSPSRMJMSModule</ModuleName>

<SubDeploymentName>OTSSPSRMSubDeployment</SubDeploymentName>

<TargetServerName>soa_server1</TargetServerName>

<PersitentStoreName>OTSSPSRMFileStore</PersitentStoreName>

<PersitentStoreType>FileStores</PersitentStoreType>

<PersistentStoreFilename> </PersistentStoreFilename>

</JMS>

</SOA>

<UCM>

<ManagedServer>

<protocol>  </protocol>

<hostname>  </hostname>

<portnumber> </portnumber>

<servername>  </servername>

<username> </username>

<password> </password>

</ManagedServer>

</UCM>

<BI>

<ManagedServer>

<protocol>  </protocol>

<hostname>  </hostname>

<portnumber> </portnumber>

<username>  </username>

<password> </password>

<reportLocation> </reportLocation>

</ManagedServer>

</BI>

<DS>

<dba.dbusername> </dba.dbusername>

<dba.dbuserpassword> </dba.dbuserpassword>

<dbusername> </dbusername>

<dbuserpassword>  </dbuserpassword>

<dbuser.createflag>true</dbuser.createflag>

<dbhostname> </dbhostname>

<dbportnumber> </dbportnumber>

<dbsid>

</dbsid>

</DS>

<USR>

<dba.dbusername> </dba.dbusername>

<dba.dbuserpassword>  </dba.dbuserpassword>

<dbusername> </dbusername>

<dbuserpassword>  </dbuserpassword>

<dbuser.createflag>true</dbuser.createflag>

<dbhostname> </dbhostname>

<dbportnumber> </dbportnumber>

<dbsid> </dbsid>

</USR>

</config>

InstallProperties Descriptions and Examples

Security Values denote values that should be changed when in production.

Property

Description

Example

<config>

<modulename>

Name of the integration module

Default: OTSS-PSRM

Do not change this value.

<PSRM>

<AdminServer>

Currently not used; leave subelements blank

<protocol>

The protocol of the application (https or http)

<hostname>

Host name of the server in which the PSRM admin server is installed

<portnumber>

PSRM port number the admin server is listening to

<servername>

Admin PSRM server name

<username>

User name used to log in as an Admin server administrator

<appcontextroot>

Context root of the PSRM Application

ouaf

<password>

Password used to log in as an Admin server administrator. Note: This is a Security Value.

<ManagedServer>

Currently not used; leave this and subelement blank

<hostname>

Currently not used; leave this and subelement blank

<portnumber>

Currently not used; leave this and subelement blank

<servername>

Currently not used; leave this and subelement blank

<username>

Currently not used; leave this and subelement blank

<password>

Currently not used; leave this and subelement blank

<WorkFlow.Notification>

<from.emailid>

Email ID which should be set in the “From” property of Workflow Notification bean

admin@oracle.com

<SOA>

<protocol>

Currently not used; leave this as http

http

<hostname>

Host name of the server where admin server hosting SOA suite is installed.

soaadmin.oracle.com

<portnumber>

Port number the admin server (hosting SOA suite) is listening to.

7001

<servername>

Admin server name (hosting SOA suite)

AdminServer

<username>

User name used to log in as an Admin server (hosting SOA suite) administrator.

weblogic

<password>

Password used to log in as an Admin server (hosting SOA suite) administrator. Note: This is a Security Value.

<domainname>

WebLogic domain name hosting SOA suite.

soa_domain

<adminemail>

Admin Email Address for OPC

Security Note: When integrating between PSRMSS and OPC, it is not mandatory to use a secured connection configuration (SSL). It is recommended, however, to use a secured connection whenever possible, and the user should inquire about this option with Official Payment Corporation when implementing the integration with this payment processing vendor.

<ManagedServer>

<protocol>

Currently not used; leave this as http

http

<hostname>

Host name of the server where managed server (hosting SOA suite) is installed.

managedserver.oracle.com

<portnumber>

Port number the managed server (hosting SOA suite) is listening to.

8001

<servername>

Managed server name (hosting SOA suite)

soa-server1

<username>

User name used to log in to managed server (hosting SOA suite) as an administrator.

weblogic

<password>

Password used to log in to managed server (hosting SOA suite) as an administrator. Note: This is a Security Value.

<mdsconfig>

<mdsdbusername>

User name used to log in to MDS schema.

DEV_MDS

<mdsdbuserpassword>

Password used to log in to MDS schema. Note: This is a Security Value.

<mdsdbhostname>

Host name of the server hosting the database containing MDS schema

<mdsdbportnumber>

Port number of the database containing MDS schema.

1521

<mdsdbsid>

SID of the database containing MDS schema

<JMS>

<serverName>

Server name hosting the JMS queue.

Note: Queues are hosted and targeted on a WebLogic domain hosting SOA suite, do not change this value

OTSSETPMJMSServer

<ModuleName>

Module name hosting the JMS queue.

OTSSETPMJMSModule

<SubDeploymentName>

Sub deployment name for JMS queues

OTSSETPMSubDeployment

<TargetServerName>

WebLogic managed server name.

soa-server1

<PersistentStoreName>

JMS persistent store name

OTSSETPMFileStore

<PersistentStoreType>

JMS persistent store name

FileStores

<PersistentStoreFilename>

JMS persistent store type (FileStores)

This value should be pointing to directory that exists and is accessible.

/psrmss/filestore

<UCM>

<protocol>

The protocol of the application (https or http).

<hostname>

Host name of the server on which the managed server (hosting UCM Server) is installed.

<portnumber>

Port number on which the managed UCM server is listening.

<servername>

Managed server name for UCM_server1.

<username>

User name used to log in to UCM; used to create the UCM Key.

<password>

Password used to log in to UCM; used to create the UCM Key.

Note: This is a Security Value.

<BI>

<protocol>

The protocol of the application (https or http).

<hostname>

Host name of the server on which the managed server (hosting BI Server) is installed.

<portnumber>

Port number on which the managed BI server is listening.

<username>

User name used to log in to BI; used to create the connection to BI.

<password>

User name used to log in to BI; used to create the connection to BI.

Note: This is a Security Value.

<reportLocation>

This value should be set to the report folder location in BI Publisher.

Example value: /~weblogic/Drafts/

<DS>

<dba.dbusername>

User name used to log in as a database administrator (DBA).

This database hosts the schema required for the PSRMSS Direct Flows Integration

system

<dba.dbuserpassword>

Password used to log in as a database administrator (DBA). Note: This is a Security Value.

<dbusername>

User name used to log in to OTSSBPEL schema for PSRMSS Direct Flows integration.

This user can be automatically created by the install (set dbuser.createflag to true) or manually outside the install process.

<dbuserpassword>

Password used to log in to PSRMSSBPEL schema for PSRMSS Direct Flows Integration. Note: This is a Security Value.

<dbuser.createflag>

Flag specifying whether to create a new schema or use the existing schema for PSRMSS Direct Flows Integration.

If the schema is created manually outside of the installation process, then set this value to "false". Otherwise, set the value to "true", if the installation script should automatically create the schema.

Valid values: true or false (case sensitive)

true

<dbhostname>

Database host name used for PSRMSS Direct Flows Integration.

Database.us.oracle.com

<dbportnumber>

Database port number used for PSRMSS Direct Flows Integration.

1521

<dbsid>

Database SID used for PSRMSS Direct Flows Integration.

SID

<USR>

<dba.dbusername>

User name used to log in as a database administrator (DBA).

This database hosts the schema required for the User Enrollment Integration.

<dba.dbuserpassword>

Password used to log in as a database administrator (DBA).

Note: This is a Security Value

<dbusername>

User name used to log in to User Enrollment schema for PSRMSS Direct Flows integration.

This user can be automatically created by the install (set dbuser.createflag to true) or can be created manually outside of the install process.

<dbuserpassword>

Password used to log in to users schema for User Enrollment.

Note: This is a Security Value.

<dbuser.createflag>

Flag specifying whether to create a new schema or use the existing schema for Users schema.

If the schema is created manually outside of the installation process, then set this value to "false". Otherwise, set the value to "true" if the installation script should automatically create the schema.

Valid values: true or false (case sensitive).

true

<XdbhostnameXX>

Database host name used User Enrollment.

database.us.oracle.com

<dbportnumber>

Database port number used for User Enrollment.

1521

<dbsid>

Database SID used for User Enrollment. This stores information about different users of the Self Service Application, you may want to consider placing this User Schema in a different database than in the PSRMSS Direct Flows Integration.

SID

Appendix B

- RCU Database Creation (Sample)

RCU Database Creation (Sample)

When creating the RCU database you should configure the following components.

Required RCU Components

Schema Owner

Metadata Services

<PREFIX>_MDS

Oracle Content Server 11g - Complete

<PREFIX>_OCS

SOA Infrastructure

<PREFIX>_SOAINFRA

User Messaging Service

<PREFIX>_ORASDPM

WebCenter Spaces

<PREFIX>_WEBCENTER

Portlet Producers

<PREFIX>_PORTLET

Activity Graph and Analytic

<PREFIX>_ACTIVITIES

You will also need to create a separate MDS schema in the database for the PSRMSS application.

Required RCU Components

Schema Owner

Metadata Services

<PREFIX>_MDS

Appendix C

- PSRMSS Sample Domain Creation

PSRMSS Sample Domain Creation

The following is a sample of the extension that will be needed to be installed prior to installing PSRMSS.

The following components need to be selected for the domain:

- Basic WebLogic Server Domain

- Oracle WebCenter Spaces

- Oracle Portlet Producers

- Oracle Enterprise Manager

- Oracle SOA Suite

- Oracle WebCenter Activities Graph Engine

- Oracle WebCenter Spaces

- Oracle Universal Content Management

- Oracle WebCenter Analytics Collector

- Oracle WSM Policy Manager

- Oracle JRF

In the configure JDBC Component Schema screen, you should see following Components if the correct extensions are selected in the previous steps of the domain creation.

Appendix D

- Sample Oracle WebLogic Data Sources

Sample Oracle WebLogic Data Sources

The following are the sample layout of the data sources that should be present in your domain when working with PSRMSS:

Appendix E

- Sample Summary of Servers

Sample Summary of Servers

The following are the servers that need to be installed into the domain prior to installing PSRMSS.

Appendix F

- Installation Properties

Installation Properties

The following listing shows the structure and sample data contained in PSRM-SS-InstallProperties.xml file.

Security Note: After a successful installation it is recommended that the PSRM-SS-InstallProperties.xml file be moved to a secured location. It is also recommended that passwords supplied in the PSRM-SS-InstallProperties.xml file be changed. The values that should be changed are marked with "Security Value" in the description fields in the table that follows the file listing.

<?xml version="1.0" standalone="yes"?>

<config>

<WSS>

<modulename>PSRM-SS-APPLICATION</modulename>

<otss>

<username> </username>

<password> </password>

<AdminServer>

<protocol>t3</protocol>

<hostname> </hostname>

<portnumber> </portnumber>

<servername>AdminServer</servername>

<usekeyfile>false</usekeyfile>

<username> </username>

<password> </password>

<userconfigfile> </userconfigfile>

<userkeyfile> </userkeyfile>

<domainname> </domainname>

<realmName> </realmName>

</AdminServer>

<ManagedServer>

<hostname> </hostname>

<portnumber> </portnumber>

<servername>psrmss_server1</servername>

<machine> </machine>

<clustername></clustername>

</ManagedServer>

<DB>

<dba.dbusername> </dba.dbusername>

<dba.dbuserpassword> </dba.dbuserpassword>

<dbusername> </dbusername>

<dbuserpassword> </dbuserpassword>

<dbuser.createflag>true</dbuser.createflag>

<dbhostname> </dbhostname>

<dbportnumber> </dbportnumber>

<dbsid> </dbsid>

<script>select 1 from dual</script>

</DB>

<mdsconfig>

<mdsdbusername> </mdsdbusername>

<mdsdbuserpassword> </mdsdbuserpassword>

<mdsdbhostname> </mdsdbhostname>

<mdsdbportnumber> </mdsdbportnumber>

<mdsdbsid> </mdsdbsid>

</mdsconfig>

</otss>

<UCM>

<hostnamejcr> </hostnamejcr>

<portnumberjcr> </portnumberjcr>

</UCM>

<SOA>

<ManagedServer>

<hostname> </hostname>

<portnumber> </portnumber>

<servername>soa_server1</servername>

<createbpelmap>true</createbpelmap>

<adminusername> </adminusername>

<adminpassword> </adminpassword>

<protocol>http</protocol>

</ManagedServer>

</SOA>

</WSS>

</config>

PSRM-SS-InstallProperties.xml Descriptions and Examples

Security Note: Security values denote values that should be changed when in production.

XPath

Description

Example

Modulename

ModuleName for which this installation property is used. Not used by installation framework. Hardcoded to "PSRM-SS-APPLICATION".

/config/otss/username

The username used to access the PSRMSS Application. This will be created during the installation.

/config/otss/password

The password that will be used to access the PSRMSS Application. This will be the password of the user that will create during the application. The password needs to be at least eight characters long. Note: This is a Security Value.

/config/otss/AdminServer/protocol

The protocol to access the admin console

Leave the default of t3; this will be used in future releases.

t3

/config/otss//AdminServer/ hostname

Hostname of Admin Server of WebLogic domain hosting the PSRMSS application

PSRM-SS-hostname.oracle.com

/config/otss//AdminServer/portnumber

Port Number of Admin Server of WebLogic domain hosting the PSRMSS application

7001

/config/otss//AdminServer/servername

Managed server name for the Admin Server hosting server.

AdminServer

/config/otss//AdminServer/userkeyfile

When this value is set to true, the userconfigfile and userkeyfile are used to connect to the server.

false

/config/otss//AdminServer/username

Admin Username which should be used to access the Admin Server.

weblogic

/config/otss//AdminServer/password

Admin Password which should be used to access the Admin Server

Note: This is a Security Value.

WLSAdminPasswd

/config/otss//AdminServer/userconfigfile

This value should be set to the location of the user configuration file.

The value does not need to be set unless you are using the user store configuration.

/config/otss//AdminServer/userkeyfile

This value should be set to the location of the user key file.

The value does not need to be set unless you are using the user store configuration.

/config/otss//AdminServer/domainname

WebLogic domain name hosting the PSRMSS managed server.

base_domain

/config/otss//AdminServer/realmname

Realm name of the embedded WebLogic LDAP configured for WebLogic domain hosting PSRMSS

myrealm

/config/otss//ManagedServer/hostname

Hostname of Managed server hosting PSRMSS.

Note: This is used during the installation process.

PSRM-SS-hostname.oracle.com

/config/otss//ManagedServer/portnumber

Managed server port number.

Note: This is used during the installation process. The port number should not be in use by a different process on the server.

/config/otss//ManagedServer/servername

Managed server name hosting PSRMSS.

Note: This is created during the installation process.

psrmss_server1

/config/otss//ManagedServer/machinename

Machine name to associate with the managed server name hosting PSRMSS

Note: The Administration Server uses the machine definition in conjunction with Node Manager to start remote servers during the installation process.

Qa

/config/otss//DB/dba.dbusername

Sys user to connect to DB which will host WSS-specific DB objects.

system

Note: If using sys user then use "sys as sysdba".

/config/otss//DB/dba.dbuserpassword

sys user password. Note: This is a Security Value.

/config/otss//DB//dbusername

Database username which will host PSRMSS specific DB objects.

WSSADM

/config/otss//DB/dbuserpassword

Password of DB username which will host PSRMSS specific DB objects. Note: This is a Security Value.

/config/otss///DB/dbuser.createflag

Flag to state whether to create database user or specify if user already exists. Valid values:

true – Create user during the installation of PSRMSS.

true

/config/otss///DB/dbhostname

Hostname to connect to Databases

databaseserver.oracle.com

/config/otss///DB/dbportnumber

Port Number to connect to Database

1521

/config/otss///DB/dbsid

SID/service name to connect to database

DBSID

/config/otss/mdsconfig/mdsdbusername

Username of schema hosting MDS for WSS application.

Note: This should be the user that was created for the for the empty MDS Schema.

PSRMSS_MDS

/config/otss/mdsconfig/mdsdbuserpassword

Password to connect to the schema. Note: This is a Security Value.

/config/otss/mdsconfig/mdsdbhostname

Hostname to connect to Database

databaseserver.oracle.com

/config/otss/mdsconfig/mdsdbportnumber

Port Number to connect to DB

1521

/config/otss/mdsconfig/mdsdbsid

SID/service name to connect to schema

DBSID

/config/otss/UCM/hostnamejcr

Hostname of the UCM Server

UCM-HostName.oracle.com

/config/otss/UCM/portnumberjcr

JCR Port Number of the UCM Server.

/config/otss/SOA/hostname

Hostname of the SOA Server

SOA-HostName.oracle.com

/config/otss/SOA/portnumber

SOA Port Number of the SOA Server

8001

/config/otss/SOA/servername

SOA Server Name

soa_server1

/config/otss/SOA/createbpelmap

This value specifies whether to create the Map for the connection between PSRMSS and the SOA endpoints.

true

/config/otss/SOA/adminuser

This username is used to create the map for the connection between PSRMSS and the SOA endpoints.

weblogic

/config/otss/SOA/adminpassword

This value of password is used to create the map for the connection between PSRMSS and the SOA end points.

Note: This is a Security Value.

/config/otss/SOA/protocol

The protocol to access the SOA Server (https or http)

Note: This is a Security Value; it is recommended that the connection between the Portal Application and the SOA server be SSL-enabled.

http

Appendix G

- Installer Utility Overview

Installer Utility Overview

The installation utility has several different input options that can be passed in as input. The following table contains the available options:

Table 1. Installation Options

Option

Description

Tasks Performed

i

Full installation of PSRMSS

- Creates a WebLogic managed server

- Links needed Libraries and applications to the WebLogic managed server

- Creates a MetaData Repository mds-PSRMSS_MDS

- Creates a Database Source WSSDS

- Deploys PSRMSS shared library

- Configures and Deploys PSRMSS ear File

- Creates and Installs a Database Schema for PSRMSS

d

Full uninstallation of PSRMSS

- Removes a WebLogic managed server

- Removes a MetaData Repository mds-PSRMSS_MDS

- Removes a Database Source WSSDS

- Undeploys PSRMSS ear File

- Undeploys PSRMSS shared library

- Drops a Database Schema for PSRMSS

r

Redeployment of PSRMSS components

- Undeploys PSRMSS Application ear

- Deploys PSRMSS Application ear

- Undeploys PSRMSS shared library

- Deploys PSRMSS shared library

The installer will continue with the installation should a task fail. Failures will be listed on the screen as a summary at the end of the installation, along with the install.log file. You can rerun the installer after corrective action is taken.

Appendix H

- URL Examples

URL Examples

Component

URL Syntax

WebLogic EM Console

http://<weblogicHost>:<webLogicPortNumber>/em

WebLogic Console

http://<weblogicHost>:<webLogicPortNumber>/console

SOA Composer

http://<SOAHost>:<SOAPortNumber>//soa/composer

UCM Console

http://<UCMHost>:<UCMPortNumber>/cs

Appendix I

- Integration Environment Settings Example

Integration Environment Settings Example

The following is an example of setting the needed environment variables for the PSRMSS-PSRM Integration.

On Linux:

PRODUCT_HOME=/ouaf/versions/Releases/PSRMSS/BPEL-Release-V1.1.0-InitialInstall/OTSS-PSRM/;

export PRODUCT_HOME

WL_HOME=/PSRM-SS/qa2_middleware1035/; export WL_HOME

SOA_HOME=PSRM-SS/qa2_middleware1035/Oracle_SOA1; export SOA_HOME

ORACLE_HOME=/PSRM-SS/qa2_middleware1035/Oracle_SOA1; export ORACLE_HOME

source "${WL_HOME}/wlserver_10.3/server/bin/setWLSEnv.sh"

cd $PRODUCT_HOME/bin

On Windows:

SET PRODUCT_HOME=C:\download\Release\PSRM-SS\OTSS-Release-V1.1.0-Initialinstall\OTSS-PSRM

SET WL_HOME=C:\PSRM-ss\middleware10.3.6;

SET SOA_HOME=C:\PSRM-ss\middleware10.3.6\Oracle_SOA1

SET ORACLE_HOME=C:\PSRM-ss\middleware10.3.6\Oracle_SOA1;

run C:\PSRM-ss\middleware10.3.6\wlserver_10.3\server\bin\setWLSEnv.cmd

cd %PRODUCT_HOME%\bin

For additional details, see Appendix A.

Appendix J

- PSRMSS Environment Settings Example

PSRMSS Environment Settings Example

The following is an example of setting the needed environment variables for the installation of PSRMSS.

On Linux:

PRODUCT_HOME=/PSRM-ss/version/PSRMSS-Release-V1.1.0-Initialinstall/; export PRODUCT_HOME

WL_HOME=/ PSRM-ss /middleware10.3.6; export WL_HOME

SOA_HOME=/ PSRM-ss /middleware10.3.6/Oracle_SOA1; export SOA_HOME

ORACLE_HOME=/ PSRM-ss /middleware10.3.6/Oracle_SOA1; export ORACLE_HOME

source "${WL_HOME}/wlserver_10.3/server/bin/setWLSEnv.sh"

cd $PRODUCT_HOME/bin

On Windows:

SET PRODUCT_HOME=C:\download\Release\PSRM-SS\PSRMSS-Release-V1.1.0-Initialinstall\

SET WL_HOME=C:\PSRM-SS\middleware10.3.6;

SET SOA_HOME=C:\PSRM-SS\middleware10.3.6\Oracle_SOA1

SET ORACLE_HOME=C:\PSRM-SS\middleware10.3.6\Oracle_SOA1;

run C:\PSRM-SS\middleware10.3.6\wlserver_10.3\server\bin\setWLSEnv.cmd

cd %PRODUCT_HOME%\bin

Appendix K

- Security Notes

Security Notes

The following documents provide additional information on securing the application.

Configuring SSL on a WebLogic server:

- http://docs.oracle.com/cd/E23943_01/web.1111/e13707/ssl.htm

WebLogic Security:

- http://docs.oracle.com/cd/E23943_01/web.1111/e13711/thin_client.htm

Securing SOA (BPEL):

- http://docs.oracle.com/cd/E17904_01/integration.1111/e10226/soacompapp_secure.htm

Securing UCM:

- http://docs.oracle.com/cd/E14571_01/doc.1111/e10792/c03_security002.htm

Appendix L

- Sample: Reassociating the Identity Store with an External LDAP (OUD)

Sample: Reassociating the Identity Store with an External LDAP (OUD)

This appendix describes how to configure the identity store to use an external LDAP server, such as an Oracle Unified Directory, rather than the default embedded LDAP.

To reassociate the identity store:

- Log in to the WebLogic Administration Console.

- Navigate to the Domain Structure.

The Summary of Security Realms pane displays:

In the Name column, click the realm for which you want to reassociate the identity store.

The Realm Settings pane displays:

- Open the Providers tab.

The Providers Settings pane displays:

Settings Pane - Providers

- Click New to add a new provider.

The Create a New Authentication Provider pane displays:

Enter a name for the provider (for example OUDAuthenticator for a provider that will authenticate the user for the Oracle Unified Directory).

Select the authenticator appropriate for your LDAP directory from the list of authenticators.

Be sure to select the authenticator associated with the LDAP you are configuring rather than choosing the generic DefaultAuthenticator. For example, for OUD select OpenLDAPAuthentication, or for OID select OracleInternetDirectoryAuthenticator.

- Click OK to save your settings.

- The Settings pane displays with the new authentication provider

- In the list of Authentication Providers, click the newly created provider.

The Settings Pane for the new authentication provider displays.

Settings Pane for Authenticator:

- Set the Control Flag to SUFFICIENT.

Setting the Control Flag to SUFFICIENT indicates that if a user can be authenticated successfully by this authenticator, then the authentication provider should accept that authentication and should not invoke any additional authenticators.

Note: If the authentication fails, it will fall through to the next authenticator in the chain. Therefore, be sure all subsequent authenticators also have their control flag set to SUFFICIENT.

- Click Save to save this setting.

- Open the Provider Specific tab to enter the details for the LDAP server.

- Enter the details specific to your LDAP server.

Parameter

Value

Description

Host:

The LDAP server's server ID (for example, <ldap_host>example.com)

Port:

The LDAP server's port number (for example, 1389)

Principal:

The LDAP user DN used to connect to the LDAP server (for example, cn=Directory Manager)

Credential:

The password used to connect to the LDAP server

User Base DN:

Specify the DN under which your Users start (for example, cn=users,dc=example,dc=com)

User From Name Filter:

Specify User From name Filter (for example &(uid=%u)(objectclass=person))

)

User Search Scope:

Specify User Search Scope (for example subtree

)

User Name Attribute

Enter User Name Attribute (for example uid

)

User Object Class

Enter User Object Class (for example person)

Group Base DN

Specify the DN that points to your Groups node (for example, cn=groups,dc=example,dc=com)

Group From Name Filter

Enter Group From Name Filter ( for example (|(&(cn=%g)(objectclass=groupofUniqueNames))(&(cn=%g)(objectclass=groupOfURLs))))

Group Search Scope

Enter Group Search Scope (for example subtree)

Group Membership Searching

Enter Group Membership Searching ( for example Unlimited)

Static Group Name Attribute

Enter Static Group Name Attribute ( for example cn )

Static Group Object Class

Enter Static Group Object Class ( for example groupofuniquenames)

Static Member DNAttribute

Enter Static Member DNAttribute ( for example uniqemember )

Static Group DN sfrom Member DNFilter

Enter Static Group DNsfrom Member DNFilter ( for example (&(uniquemember=%M)(objectclass=groupofuniquenames))

)

Dynamic Group Name Attribute

Enter Dynamic Group Name Attribute ( for example cn)

Dynamic Group Object Class

Enter Dynamic Group Object Class ( for example groupofURLs)

Dynamic Member URLAttribute

Enter Dynamic Member URLAttribute ( for example memberURL)

Use Retrieved User Name as Principal

Checked

Must be turned on

All Users Filter:

(&(uid=*)(objectclass=person))

Search to find all users under the User Base DN

User From Name Filter:

(&(uid=%u)(objectclass=person))

User Name Attribute:

uid

- Click Save.

- Return to the Providers tab and reorder the providers so that the new authentication provider is on top, followed by any other authenticators with the DefaultAuthenticator placed at the end of the list.

All should have their Control Flags set to SUFFICIENT so that subsequent authenticators can authenticate identities that fall through from the new provider all the way through to the DefaultAuthenticator (which is used only for the default file-based embedded LDAP). For example, logins such as the default administrator account are not typically created in the LDAP directory, but still need to be authenticated to start up the server. Unless identities are allowed to fall through to the DefaultAuthenticator, the default administrator account will not be authenticated.

- Restart the Administration Server and the managed servers for the changes to take effect.

The following users will need to be seeded in the external LDAP Repository (these users must be added to be able to access the WebCenter Portal Administration Console):

User: contentadmin

This user should be a member of the Administrators group:

User: wssadmin

This user should be a member of the Administrators group:

References

OUD:

http://www.oracle.com/technetwork/middleware/id-mgmt/documentation/index.html

WebCenter:

http://docs.oracle.com/cd/E12839_01/webcenter.1111/e12405/wcadm_security.htm

http://docs.oracle.com/cd/E12839_01/webcenter.1111/e12405/wcadm_security.htm#BGBHHGEH

Appendix M

- Updating BPEL/SOA Configuration Settings (ConfigurationProperties.xml)

Updating BPEL/SOA Configuration Settings (ConfigurationProperties.xml)

The following section describes how to update the MDS repository after the installation has been completed.

Linux/Unix file location:

$PRODUCT_HOME/MDS-Artifacts/OTSS-ETPM/AIAMetaData/config

Windows file location:

%PRODUCT_HOME%/MDS-Artifacts/OTSS-ETPM/AIAMetaData/config

Once the proper updates are completed, upload the changes to the MDS.

The following are the steps to upload the MDS from the delivered utilities.

You will need to set the following variables:

Variable

Example

SOA_HOME

<BEA_HOME>/>Oracle_SOA1

ORACLE_HOME

<BEA_HOME>/>Oracle_SOA1

MW_HOME

<WebLogic_HOME>/Middleware

WL_HOME

<BEA_HOME>//wlserver_10.3

PRODUCT_HOME

This is the BPEL OTSS-ETPM product installation home.

Linux Example:

PRODUCT_HOME=/psrmss/PSRM-SS/BPEL-Release-V1.1.0.0.0-Release-InitialInstall/OTSS-ETPM

Windows Example:

PRODUCT_HOME=D:\psrmss\PSRM-SS\BPEL-Release-V1.1.0.0.0-Release-InitialInstall\OTSS-ETPM

On UNIX/Linux:

cd $PRODUCT_HOME/bin

./install.sh -deployMDS

Note: The following ant command should be entered on one line On Windows:

cd %PRODUCT_HOME%\bin

ant -f =%PRODUCT_HOME%\bin\DeployUndeployUtility.xml

-DInstallProperties==%PRODUCT_HOME%\config\InstallProperties.xml DeployMDS

You will need to restart the SOA server to activate the updates for MDS.

Appendix N

- UCM and Configuration.Properties

UCM and Configuration.Properties

For the link from PSRM to UCM to work (using the setup for the property below), the uploaded documents need to be uploaded into a UCM FOLDER.

This is done by setting the UploadFolderID property in the Configuration.Properties file.

Note: See Appendix M, "Updating BPEL/SOA Configuration Settings".

Configuration.Properties file Description for UCM Properties.

The example values specified are only examples, and will need to be updated to your implementation of UCM.

Property

Value

FileUpload.UCM.Endpoint.URL

Example Value:

https://ucm_server:ucm_port/idcws/GenericSoapPort</Property>

Note: This value is detokenized with the installation with the value entered in the installProperties.xml. This value may need to be updated depending on your implementation of UCM.

FileUpload.UCM.User

This value should be the user to connect to UCM

Value for user of the document that will be uploaded

Example Value: weblogic

FileUpload.UCM.DocumentType

Value for document type of the document that will be uploaded.

Example Value: Document

FileUpload.UCM.SecurityGroup

Value for security group of the document that will be uploaded

Example Value: Secure

FileUpload.UCM.DocumentAuthor

Value for author of the document that will be uploaded.

Example Value: weblogic

FileUpload.UCM.DocumentAccount

Xpath containing the value of the account of the document that will be uploaded. Xpath is relative to head element.

Example Value: webUserId

FileUpload.UCM.UploadFolderID

Content ID of the UCM file upload folder. This is used in case FileUpload.UCM.UploadFolderName is not specified.

Example Value: The steps to locate this valued are describe below.

FileUpload.UCM.UploadFolderName

Content Name of the UCM file upload folder

FileUpload.UCM.UploadFolderWebLocation

Web folder location of the uploaded file. This is concatenated with the uploaded filename to generate the complete path to the file.

Example Value: http://ucm_host:ucm_port/cs/Contribution%20Folders/

FileUpload.RetainContent

Flag to determine whether uploaded file contents should be forwarded to the back-end system

Example Value: true

<Property name="FileUpload.UCM.Endpoint.URL">http://<yourSecuredUCMServer>:<port>/idcws/GenericSoapPort</Property>

<!-- Value for user of the document that will be uploaded. -->

<Property name="FileUpload.UCM.User">yourSecuredUCMUserID</Property>

<!-- Value for document type of the document that will be uploaded. -->

<Property name="FileUpload.UCM.DocumentType">Document</Property>

<!-- Value for security group of the document that will be uploaded. -->

<Property name="FileUpload.UCM.SecurityGroup">yourUCMSecurityGroupName</Property>

<!-- Value for author of the document that will be uploaded. -->

<Property name="FileUpload.UCM.DocumentAuthor">yourUploadedDocumentAuthorName</Property>

<!-- Xpath containing the value of the account of the document that will be uploaded. Xpath is relative to head element. -->

<Property name="FileUpload.UCM.DocumentAccount">webUserId</Property>

<!-- Content ID of the UCM file upload folder. This is used in case FileUpload.UCM.UploadFolderName is not specified. -->

<Property name="FileUpload.UCM.UploadFolderID">yourUCMUploadFolderID</Property>

<!-- Content Name of the UCM file upload folder. -->

<Property name="FileUpload.UCM.UploadFolderName">yourUCMUploadFolderName</Property>

<!-- Web folder location of the uploaded file. This is concatenated with the uploaded filename to generate the complete path to the file. -->

<Property name="FileUpload.UCM.UploadFolderWebLocation">yourSecuredUCMWebFolderMappingForUploadDocuments</Property>

<!-- Flag to determine whether uploaded file contents should be forwarded to the back-end system -->

<Property name="FileUpload.RetainContent">false</Property>

The following section describes the needed configuration and values that are needed for this functionality to work properly:

The UploadFolderWebLocation depends on the configuration in UCM the default configuration is described in the following section.

The UploadFolderName is optional.

The UploadFolderID has to be specified and it has to be a Folder ID of a UCM folder created for that environment.

Property: FileUpload.UCM.UploadFolderWebLocation

Log in to the Oracle UCM admin console using the following URL:

http://ucm_host:ucm_port/cs/

Log in as an administrator and go to Administration -> Folder Configuration -> Web Url Mapped Folders.

Enter Folder

Enter URL Mapping

Example Values:

Click Add.

Property: FileUpload.UCM.UploadFolderID

Log in to the Oracle UCM admin console using the following URL:

http://ucm_host:ucm_port/cs/

Log in as an administrator and go to Browse Content -> Contribution Folders

Note: This example uses the Contribution Folders, which was created in the previous section.

To check the folder's ID, you can simply place your mouse over the link to the particular folder to get its ID. It will be identified as CollectionID in the URL. Do this on both the source and target instances.

The following is a different mechanism to retrieve the Folder ID:

Right click on the Contribution Folders folder (left side):

In Internet Explorer, use the Copy Shortcut option (standard right click context menu, example for IE).

Paste the shortcut into a text editor and you should see something similar to the following:

http://ucm_host:ucm_port/cs/idcplg?IdcService=COLLECTION_DISPLAY&

hasCollectionID=true&dCollectionID=825638308519000001

Note: Collection ID is another name for Folder ID in UCM.

Appendix O

- Configuring WebLogic storeUserConfig

Configuring WebLogic storeUserConfig

For information on setting up and configuring a userConfigFile and a userKeyFile when using this option for the installation of PSRMSS, see the WLST Command and Variable Reference (http://docs.oracle.com/cd/E11035_01/wls100/config_scripting/reference.html).

Appendix P

- Oracle Policy Automation

Oracle Policy Automation

Oracle Policy Automation (10.4.4.21) incorporates your business policies into business processes that deliver accurate, consistent, and auditable outcomes.

The product can be downloaded from the Oracle Tech Network site at:

http://www.oracle.com/technetwork/apps-tech/policy-automation/downloads/index.html

Refer to the Oracle Policy Automation Installation Guide for detailed instructions to install and deploy Oracle Determinations Server for Java.

Note:

More current releases of OPA may be available; please check with Oracle Support with compatibility of versions other than the one specified above.

Appendix Q

- Installation Troubleshooting

Installation Troubleshooting

Troubleshooting Tip 1: The ADF Connection strings are not properly configured.

When processing transactions in the ADF Portal Application that have an Integrated flow, and you receive a 401 message, this is an indicator that the ADF Connection strings are not properly configured.

You will need to set the environment variables for the PRODUCT_HOME for the PSRMSS and execute the following command:

./install.sh -k

Note: This option will attempt to link the Web Service Connection with the policies and csf-keys.

Log in into the Oracle Enterprise Manager console at http://WLSAdminHost:WLSAdminServerPort/em with your wlsadminuser/wlsadminpasswd credentials.

Select Application Deployments, choose PSRMSS, then right-click and choose ADF > Configure ADF Connections from the context menu:

Click Apply.

Troubleshooting Tip 2: In the SOA Server log file you receive the following alert:

[2014-05-19T14:52:00.310-07:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: Workmanager: , Version: 0, Scheduled=false, Started=false, Wait time: 0 ms\n] [ecid: 0000KOLVr7vBX7KLIU5Eif1JUZpA000002,0] [APP: soa-infra] File Adapter OTSSReportReconciliationRequestEBF Recovery still not possible after 270 attempts due to BINDING.JCA-11001[[

Invalid Input Directory.

To resolve this issue, see Post-Installation Steps for Integration section in this document.

Troubleshooting Tip 3: When navigating in the ADF Application you receive the following message:

"There were issues detected while processing your request; please contact us for more details."

The following will be seen in the ADF log file:

[2014-05-12T12:06:29.421-07:00] [psrmss_server1] [ERROR] [] [oracle.apps.otss.base.service.util.ServiceUtil] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: anonymous] [ecid: 0000KNlp3eIBX7KLIU5Eif1JSHbu00000V,0] [APP: PSRMSS] [ETPM-SS] getMessageString: Error while attempting to get sequence. JBO-25058: Definition sequence of type Attribute is not found in ViewDeferrorMessage28_655.

[2014-05-12T12:06:29.428-07:00] [psrmss_server1] [ERROR] [] [oracle.apps.otss.serviceRequest.common.ui.bean.IdentificationFormBean] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: anonymous] [ecid: 0000KNlp3eIBX7KLIU5Eif1JSHbu00000V,0] [APP: PSRMSS] [ETPM-SS] submitAction: ERROR OCCURRED - <html> <body><p>There were issues detected while processing your request, please contact us for more details.</p><p>BPE 11001:401</p></body> </html>

To resolve this issue, check to see if the MDS (DVM) is up to date with the PSRM application.

Troubleshooting Tip 4:

For general troubleshooting information for WebCenter Components, see Troubleshooting Oracle WebCenter Portal in the documentation section of the Oracle Technology Network.

Table of Contents

Cover Page

Legal Notices

Installation Overview

Additional Resources

Abbreviations

Roadmap for PSRMSS Installation and Configuration

Software Requirements

PSRMSS Installation

Types of Installation Packages

Pre-Installation Tasks

Installing Integrations

Integration Pre-Installation Tasks

PSRMSS-PSRM (BPEL) Integrated Flows Installation Directory Structure

Completing the Integration Installation

Post-Integration Configuration Tasks

Updating the Worklist Application

Post-Integration Checklist

Verifying Creation of the Outbound Connection Pools

Verifying Creation of the JMS Modules

Verifying Creation of the OTSS-SOADS1 and OTSS-USRACS Data Sources

Verifying Composites in Enterprise Manager

Verifying Worklist Applications Deployment

Verifying Creation of Keys

Accessing the Worklist Application

PSRMSS Installation Directory Structure

PSRMSS Product Installation

Post-Installation Tasks

Verifying the Installation

Verifying ADF Connections for the PSRMSS Application

Verifying the PSRMSS Schema Tables

Verifying Creation of the PSRMSS Server

Verifying the WSSDS Data Source

Verifying the mds-PSRMSSMDS_MDS Data Source

Verifying the PSRMSSFormsAdmin Group

Verifying wasadmin User Creation

Verifying Successful Application Deployment

Verifying Successful Key Creation

Accessing the PSRMSS Application

Configuring UCM for PSRMSS

UCM Configuration: Part 1

UCM Configuration: Part 2

Configuring SSL for a PSRMSS Server

Appendix A

BPEL/SOA installProperties.xml

Appendix B

RCU Database Creation (Sample)

Appendix C

PSRM-SS Sample Domain Creation

Appendix D

Sample Oracle WebLogic Data Sources

Appendix E

Sample Summary of Servers

Appendix F

PSRMSS Installation Properties

Appendix G

Installer Utility Overview

Appendix H

URL Examples

Appendix I

PSRMSS-PSRM Integration Environment Settings Example

Appendix J

PSRMSS Environment Settings Example

Appendix K

Security Notes

Appendix L

Reassociating the Identity Store with an External LDAP (OUD)

Appendix M

Updating BPEL/SOA Configuration Settings (ConfigurationProperties.xml)

Appendix N

UCM and Configuration.Properties

Appendix O

Configuring WebLogic storeUserConfig

Appendix P

Oracle Policy Automation

Appendix P

Installation Troubleshooting