Oracle Enterprise Taxation and Policy Management Self Service

Demo Installation Guide

Oracle Corporation

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

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 software or related documentation 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 RIGHTS

Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

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 which 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.

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 Enterprise Taxation and Policy Management Self Service (ETPMSS) integrated with Oracle Enterprise Taxation and Policy Management (ETPM).

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

- Additional Resources

- Abbreviations

- Note for Windows Internet Explorer Users

- Roadmap for ETPMSS Installation and Configuration

- Software Requirements

Additional Resources

For more information on products related to ETPMSS 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 Enterprise Taxation Policy Management v2.3.1 Documentation Library

http://docs.oracle.com/cd/E28126_01/index.htm

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

Abbreviations

ETPMSS

Oracle Enterprise Taxation and Policy Management Self Service

ETPM

Oracle Enterprise Taxation and Policy Management

DDL

Data Definition Language

MDS

Metadata Services

OUI

Oracle Universal Installer

RCU

Repository Creation Utility

EAR

Enterprise Archive

WC

Oracle WebCenter

WLS

Oracle WebLogic Server

ADF

Application Development Framework

SOA

Service Oriented Architecture

BPEL

Business Process Execution Language

MDS

Metadata Services

Note for Windows Internet Explorer Users

If a portion of the web page is blank or does not display correctly in Windows Internet Explorer, refer to the Microsoft article at http://windows.microsoft.com/en-US/windows7/webpages-look-incorrect-in-Internet-Explorer.

Additional information on this issue can be found in BUG 14593433.

Roadmap for ETPMSS Installation and Configuration

Software Requirements

The following software must be installed and configured prior to installation of Oracle ETPM 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

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

- Oracle Enterprise Taxation Policy Management Release 2.3.1

- ETPM Service Pack 1 [BUG: 14713038]

Note: You will only need to install the application server portion of the Service Pack, since the ETPM Demo Data dump file already includes ETPM Service Pack 1.

- Oracle Documaker 12.0.1

- Demo Data for ETPM specifically for ETPM-SS can be downloaded from BUG: 14733541.

Table 1. Software Download Prerequisites and Download Locations

Prerequisite

Reference (Download Site)

Install Oracle WebLogic

http://docs.oracle.com/cd/E23104_01/download_readme_ps4/download_readme_ps4.htm

Install Oracle WebCenter

http://docs.oracle.com/cd/E21764_01/install.1111/e12001/toc.htm

Install Oracle SOA

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

Install Oracle Content Server

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

Install Oracle RCU

http://www.oracle.com/technetwork/middleware/webcenter/portal/downloads/index.html
Note: This link contains the downloads for 11.1.1.5.0.

ETPMSS Installation

- Types of Installation Packages

- Pre-Installation Tasks

- ETPMSS Installation Directory Structure

- Demo Supplemental Contents Overview

- ETPM-SS Product Installation

- Post-Installation Tasks

Types of Installation Packages

Installation Type

Description

Demo Install (described in this document)

Refer to ETPM-SS Bug 14733541 for the latest demo download installation for ETPMSS and the demo components for ETPM.

Initial Install (ETPM-SS and ETPMSS-ETPM Integration)

This type of installation provides the base installation with the integration functionality into ETPM.

Standalone Install (ETPM-SS and ETPMSS-EDGE-PROD Integration)

This type of installation should be used when you are not planning to integrate with ETPM.

Note: Each package has the same basic installation procedure, though when running the Demo installation there are additional steps, as described in this document.

Pre-Installation Tasks

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

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 ETPM-SS.

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 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 ETPMSS (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 (can be installed into separate domain)

The installation utility uses delivered libraries and applications from these servers; they do not need to be running for the installation.

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 Admin Server is running, and you are able to access the console:

http://weblogichost:weblogicadminport/console

ETPMSS Installation Directory Structure

This folder includes a subfolder hierarchy as shown in the following image. 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. 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

ETPM-SS-InstallProperties.xml

Installation parameters file.

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

- Log contains the log for the installation utility.

Demo Supplemental Contents Overview

ETPMSS-Demo-Supplemental.zip includes the following files:

- ETPMSS_V1.0.0_MDS.zip. This is the MDS archive file.

- WSSPortalOverrideBundle_en.xlf. This is the Application Override Bundle file. It is provided for informational purposes only, since it is also included in the MDS archive file.

- etpmss_v1.0.0_demo_ucm.zip. This is the UCM content archive file.

Additional information on these files can be found in the topic, Additional Installation Instructions for ETPM-SS Demo, later in this document.

ETPM-SS Product Installation

This procedure describes the basic installation procedure for ETPMSS.

1. Download ETPM-SS-Demo-Installation.jar from the Bug: 14733541 and unzip into a target installation directory:

Example: jar –xvf <ETPM-SS-ProductInstall-<Install-Type>>.jar

Linux example:

/etpm-ss/ETPM-SS-ProductInstall

Windows example:

D:\etpm-ss\ETPM-SS-ProductInstall

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

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

Linux example:

export PRODUCT_HOME=/etpm-ss/ETPM-SS-Release-V1.0.0

echo $PRODUCT_HOME

echo should return PRODUCT_HOME as the location of the top-level directory of the installation media, e.g., /etpm-ss/ETPM-SS-Release-V1.0.0.

Windows example:

SET PRODUCT_HOME=D:\ETPM-SS\ETPM-SS-Release-V1.0.0

echo %PRODUCT_HOME%

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

See Appendix J for an ETPM-SS 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.

UNIX/Linux example:

source /etpm-ss/weblogic-10.3.5/wlserver_10.3/server/bin/setWLSEnv.sh

Windows example:

run D:\weblogic-10.3.5\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/ETPM-SS-InstallProperties.xml file with values appropriate to your environment (see Appendix F for a sample ETPM-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 /etpm-ss/weblogic-10.3.5/wlserver_10.3/server/bin/setWLSEnv.sh

On Windows:

cd %PRODUCT_HOME%\bin

Important: Before proceeding to the final step, ensure that the Admin server is up and running.

6. Run the installation script to install ETPMSS (see Appendix G, "Installer Utility Overview", for additional information regarding the installer).

On Linux:

/install.sh i

Note: You will need to change the permissions on install.sh to chmod 755.

On Windows:

install.cmd i

Note:

The following message will be shown on a successful installation of ETPM-SS:

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

Installation of ETPM-SS V1.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

- Configuring ADF Connection for the ETPMSS Application

- Configuring UCM for ETPMSS

- Verifying the Installation

Configuring ADF Connection for the ETPMSS Application

To configure and verify that the ETPMSS application wsd's are correctly tokenized:

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

2. Select Application Deployments, choose WSSPortal_application1 (etpm_ss), then right-click and choose ADF > Configure ADF Connections from the context menu as shown in the following images:

3. Under Web Service Connections, each connection name has a corresponding SOA WSDL URL. Click on each connection name (e.g., TSGetConfirmationInformation), click Advanced Connection Configuration, and select WSDL URL.
Example:

The connection URL, http://soahostname:soaportno/soa-infra/services/OTSS-ETPM/OTSSRequestStatusInquiryEBF/otssrequeststatusinquirybpelprocess_client_ep

On the Configuration tab (which is not the default tab when the screen first appears), check under General for the correct Endpoint Address for the SOA Server.

Enter the HTTP User Name and HTTP User Password for the SOA Admin Server to allow the ETPMSS application to access the web services that are deployed in SOA.

Repeat Step 3 for all remaining connections to confirm that detokenization has been completed for all web services and URL connections.

Configuring UCM for ETPMSS

- UCM Configuration: Part 1

- UCM Configuration: Part 2

UCM Configuration: Part 1

After the installation process is completed 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 ETPSS 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:

If working with 11.1.1.5:

- In the Admin Server window, select the Component Manager category in the navigation area, then select the All Features radio box. Browse down the list of components and make sure that the following are checked:In the Admin Server window, select the Component Manager category in the navigation area, then select the All Features radio box. Browse down the list of components and make sure that the following are checked:

- FolderStructureArchive, Folders_g

- WebCenterConfigure

If working with 11.1.1.6:

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, then click Enable, then Save.

3. In the Admin Server window, select the Component Manager category in the navigation area, then select the All Features radio box. Browse down the list of components and make sure that the following are checked:

- Webcenter Configure

- Inbound Refinery Support

- Dynamic Converter

5. Restart the UCM Server once more.

UCM Configuration: Part 2

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

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:

If working with 11.1.1.5:

1. Choose Content Management > Universal Content Management > Content Server , then select Oracle Universal Content Management.

2. Right-click and select Configuration.

If working with 11.1.1.6:

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 *.*.*.*

4. Restart the UCM_Server.

Verifying the Installation

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

- Verifying the ETPMSS Schema Tables

- Verifying the ETPMSS Server was Created

- Verifying the WSSDS Data Source

- Verifying the mds-OTSSMDS_MDS Data Source

- Verifying wasadmin User Creation

- Verifying Successful Application Deployment

- Accessing the ETPMSS Application

Verifying the ETPMSS Schema Tables

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

2. Verify that the following tables exist by executing the query select table_name from user_tables order by table_name;

- TS_CONFIGURATION

- TS_FIELD

- TS_FIELD_L

- 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_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_SERVICE_REQUEST_DEFN

- TS_SERVICE_REQUEST_DEFN_L

- TS_SERVICE_REQUEST_FIELD

- TS_SERVICE_REQUEST_FIELD_L

- TS_VALIDATION_RULE

- TS_VALIDATION_RULE_L

Verifying the ETPMSS Server was Created

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

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

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

Verifying the WSSDS Data Source

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

2. Select the <etpm-ss-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-OTSSMDS_MDS Data Source

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

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

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

Verifying wasadmin User Creation

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

2. Select etpm-ss_domain > Security Realms > myrealm > Users and Groups .

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

Verifying Successful Application Deployment

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

2. Select the <etpm-ss-domainname>, then expand Summary of Deployments.

The list of deployments should include a shared library, as shown in the following image:

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

Accessing the ETPMSS Application

To access the ETPMSS application after a successful installation:

User

http://<weblogic-Server>:<etpm-ss-server-port>/etpmss/faces/pages_home

Admin

http://<weblogic-Server>:<etpm-ss-server-port> /etpmss/faces/oracle/webcenter/portalapp/pages/login.jspx

Installing ETPM Integrated Flows

This section describes the installation steps for Oracle Enterprise Taxation Policy Management-related integration flows.

- Integration Pre-Installation Tasks

- Integrated Flows Installation Directory Structure

- Completing the Integration Installation

- Post-Integration Checklist

Integration Pre-Installation Tasks

The following tasks should be completed before you install ETPMSS-ETPM integrated flows:

- Extract the ETPM-SS 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 aditional 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 ETPM V2.3.1 SP1 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.

- 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. 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).

Note: PRODUCT_HOME refers to the location where the ETPM_SS BPEL installation media are located.

The syntax for Product Home depends on whether you are installing on Linux or Windows. On Linux, the variable is $PRODUCT_HOME. On Windows, it is %PRODUCT_HOME%.

2. Set the following environment variables (see Appendix I for an ETPMSS-ETPM 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 ETPMSS-ETPM product installation home.

Linux Example:

PRODUCT_HOME=/etpms/ETPM-SS/BPEL-Release-V1.0.0-Release-InitialInstall/OTSS-ETPM

Windows Example:

PRODUCT_HOME=D:\etpms\ETPM-SS\BPEL-Release-V1.0.0-Release-InitialInstall\OTSS-ETPM

3. 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

4. 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

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

Note: The following ant command should be entered on one line. Also note that no output will be echoed to the screen; refer to the logfile to check progress.

On UNIX/Linux:

cd $PRODUCT_HOME/bin

ant -f InstallBuild.xml -DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml

-l installBPEL-ETPMSS.log

On Windows:

cd %PRODUCT_HOME%\bin

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

After running the command, examine installBPEL-ETPMSS.log 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.

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

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

On UNIX/Linux:

cd $PRODUCT_HOME/bin

ant -f $PRODUCT_HOME/bin/DeployUndeployUtility.xml

-DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml DeployMDS

On Windows:

cd %PRODUCT_HOME%\bin

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

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

7. Restart both the WebLogic Admin server and the SOA server to activate the installation processes and ensure that all artifacts are successfully installed.

Post-Integration Checklist

This section describes procedures to verify integration of the ETPMSS-ETPM flows.

- Verifying That the OTSS-SOADS Data Source Has Been Created

- Verifying the JMS Module sas been Created

- Verifying the OTSS-SOADS1 Data Source has been Created

- Verifying the Composites in Enterprise Manager

Verifying That the OTSS-SOADS Data Source Has Been Created

1. Log in to the Oracle WebLogic Server console at http:// WLSHostNamet: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, as shown in the following image:

Verifying the JMS Module sas been Created

1. Log in to the Oracle WebLogic Server console at http:// WLSHostNamet: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 on OTSSETPMJMSModule.

The list of resources should include the following:

- OTSSETPMConnectionFactory

- OTSSPaymentPosting

- OTSSPaymentPostingError

- OTSSPaymentReport

- OTSSPaymentReportError

- OTSSServiceRequest

- OTSSServiceRequestError

Verifying the OTSS-SOADS1 Data Source has been Created

1. Log in to the Oracle WebLogic Server console at http://WLSHostNamet: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, as shown in the following image:

Verifying the Composites in Enterprise Manager

To verify that the ETPMSS-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_soa_domain > soa > soa-infra OTSS-ETPM partition.

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

- OTSSConfirmationIdService

- OTSSGetExternalPaymentCustomService

- OTSSGetExternalPaymentDataEBF

- OTSSIdentifyTaxpayerEBF

- OTSSPaymentEBF

- OTSSPaymentPostingRequestEBF

- OTSSPaymentPostingRequestProvider

- OTSSRefundStatusInquiryEBF

- OTSSReportReconciliationRequestEBF

- OTSSReportReconciliationRequestProvider

- OTSSRequestStatusInquiryEBF

- OTSSServiceRequestJMSConsumer

- OTSSServiceRequestJMSProducer

- OTSSTaxpayerServiceRequestEBF

- OTSSTaxpayerServiceRequestProvider

Additional Installation Instructions for ETPM-SS Demo

The following tasks should be performed after the standard installation process is completed and the portal application is deployed and available:

1. Importing UCM content

2. Importing MDS

- Importing UCM Content for Demo Environment

- Importing MDS for Demo Environment

Importing UCM Content for Demo Environment

This task imports all Demo custom content to the UCM server of your Demo environment. This content can be moved to other environments if needed. For more information about managing UCM content please refer to the "Managing Portal Customization" section in the Customizing the Portal Application chapter of the ETPM-SS Implementation Guide.

Importing content into UCM is done by using the WebCenter Content Server Archiver process.

The export file that should be imported is etpmss_v1.0.0_demo_ucm.zip, which is provided with the demo installation package.

The following document contains the high-level steps for working with the archiver: http://www.oracle.com/technetwork/middleware/webcenter/portal/learnmore/wcp-content-archive-1599310.pdf

Importing MDS for Demo Environment

This task imports all portal customizations for the Demo environment.

The MDS archive file that should be imported is ETPMSS_V1.0.0_MDS.zip, which is provided with the demo installation package.

The import process is performed using Oracle Enterprise Manager. The provided MDS archive file should be imported into the installed Demo environment.

For more information on how to import or export MDS for ETPM-SS, refer to the "Managing Portal Customization" section in the Customizing the Portal Application chapter of the ETPM-SS Implementation Guide.

- Application Override Bundle File

Application Override Bundle File

The WSSPortalOverrideBundle_en.xlf file that is provided with the Demo installation package is provided for reference only. This file is included in the MDS archive file.

The Application Override Bundle includes settings for the portal application, for example:

- The text that appears on the top of the screen below the logo image.

- The custom links and icons that appear at the bottom of each page.

- The copyright message at the bottom of the screen.

- Changes to labels or titles of the portal application.

If you want to make changes to the values provided with the Demo installation, you can change or add content to the Application Override Bundle file, replacing the file in the original MDS archive and re-importing it.

The file can be located inside the MDS archive file under the xliffBundles subdirectory when the archive is expanded.

Integrating Documaker with ETPM

- Online Document Display and Batch Document Integration with Oracle Documaker

- Installing and Integrating Documaker Templates with ETPM

- Oracle Documaker Integration

Online Document Display and Batch Document Integration with Oracle Documaker

Oracle Documaker enables Adobe's Portable Document Format (PDF) to be used for on-line viewing and Internet delivery of online letter documents. This section describes how Oracle Enterprise Taxation and Policy Management can be integrated with Documaker to enable letters to be viewed online.

Documaker can also be used to generate letters using Oracle Enterprise Taxation and Policy Management's batch functionality. To configure this functionality, make sure that the batch job used to produce letters references the appropriate file path as configured by an implementation.

Documaker software must be purchased and installed separately. Documaker can be purchased and licensed from the Oracle Software Delivery Cloud (http:// edelivery.oracle.com/).

- Supported Documaker Versions

- Supported Oracle Documaker Templates

Supported Documaker Versions

At the time of release of this product, Oracle Enterprise Taxation and Policy Management 2.3.1 supports Oracle Documaker Release 12.0 for Windows and 12.0 for Linux.

Supported Oracle Documaker Templates

Oracle Enterprise Taxation and Policy Management includes a sample algorithm to extract data for letters to integrate with Documaker.

Refer to Defining Taxpayer Options > Setting Up Customer Contact Options > Letter Printing in the Oracle Enterprise Taxation and Policy Management Administration Guide online Help for additional information.

Installing and Integrating Documaker Templates with ETPM

Follow this procedure to integrate the supplied Oracle Documaker templates with your ETPM installation, and to configure your system for the integration.

1. Log in to the target server hosting the environment that you are setting up for online image display.

2. Initialize the target environment:

On UNIX:

$SPLEBASE/bin/splenviron.sh -e <SPLENVIRON>

On Windows:

%SPLEBASE%\bin\splenviron.cmd -e <SPLENVIRON>

3. Add the following environmental variables:

Environment Variable

Description

DOCDISPINI

Location of the ini file.

Example value: $SPLEBASE/etc/doc1dirfile.ini

DOCHOSTDIR

The value of DOCHOSTDIR should be set to the location where Documaker has been installed.

Example value: /ouaf/documaker/rel201

DOCPATH

Location where the generated files from the batch are located.

Example value: /ouaf/sploutput/V231_ETPM

You can add these environment variables by using cmenv.sh/cmenv.cmd exit , as documented in the OUAF Technical Best Practices Guide.

Example for UNIX:

$SPLEBASE/scripts/cm

#> cat cmenv.sh

DOCDISPINI=$SPLEBASE/etc/doc1dirfile.ini; export DOCDISPINI DOCHOSTDIR=/ouaf/documaker/rel115; export DOCHOSTDIR DOCPATH=/ouaf/sploutput/V231_ETPM; export DOCPATH

Example for Windows:

%SPLEBASE%/scripts/cm

#> type cmenv.cmd

SET DOCDISPINI=%SPLEBASE%\etc\doc1dirfile.ini

SET DOCHOSTDIR=C:\ouaf\documaker\rel115

SET DOCPATH=C:\ouaf\sploutput\V231_ETPM

4. Run the initialSetup utility for the environment to generate the Oracle Enterprise Taxation and Policy Management related Documaker INI files:

On UNIX:

$SPLEBASE/bin/initialSetup.sh

On Windows:

%SPLEBASE%\bin\initialSetup.cmd

5. Stop and start the environment:

On UNIX:

$SPLEBASE/bin/spl.sh stop/start

On Windows:

%SPLEBASE%\bin\spl.cmd stop/start

6. Copy the file ETPM-<OS>.jar to a temporary folder (referred to hereafter as <TEMPDIR>) on the target server. If you are using FTP to transfer this file to a UNIX server, remember to use the BINARY option for the FTP transfer.

Note: For UNIX, copy the ETPM-Unix.jar. On Windows, copy the ETP-Windows.jar

7. Decompress the file:

cd <TEMPDIR>

jar -xvf ETPM--<OSplatform>.jar

On UNIX:

find . -type f | xargs chmod 750

The ETM folder will be extracted.

8. If one does not already exist, create a folder named etm under the Oracle Documaker host directory <DOCHOSTDIR>. Copy the contents of the appropriate etm folder in the <TEMPDIR> to the etm directory Oracle Documaker host directory on the target application server (see the "Software Requirements" section in the Oracle Enterprise Taxation and Policy Management Installation Guide for the installation location).

It should be at the same level as the fap folder.

Example contents of <$DOCHOSTDIR>/etm:

|-- etm

| |-- data

| |-- deflib

| |-- forlib

| |-- forms

| |-- input

| |   |-- table

9. Ensure that the Oracle Enterprise Taxation and Policy Management Administrator user ID (typically cissys) has execute permissions to all files in the <DOCHOSTDIR>/fap and <DOCHOSTDIR>/etm folders.

Table 1. Sample Directory Structure

Directory

Contents

<DOCHOSTDIR>/FAP

Documaker binaries

<DOCHOSTDIR>/etm

ETPM templates and driver programs

<DOCHOSTDIR>/tax/examples

ETPM example PDFs

Sample Generated Ini File

The following files will be populated during the execution of the initialSetup utility.

Example on UNIX: doc1dirfile.ini

ONLINE DOC HOST=/ouaf/documaker/rel115

ONLINE DOC TEMPLATE=/ouaf/documaker/rel115/etm

DOC EXTRACT PATH=/ouaf/sploutput/V231_ETPM/

DOC IMAGE PATH=/ouaf/V231_ETPM /splapp/letterView/

DOC IMAGE SCRIPT=/ouaf/documaker/rel115/etm/_PrintDoc.sh

URL PREFIX=/ouaf/letterView/

Oracle Documaker Integration

This section describes the ETPM components that are used for displaying letters using Oracle Documaker.

- Oracle Documaker Algorithm

Oracle Documaker Algorithm

The base product provides an installation algorithm plug-in spot called Online Letter Image. This plug-in spot should contain an algorithm that invokes the Create PDF of Letter image by calling Oracle Documaker.

Oracle Enterprise Taxation and Policy Management provides an algorithm type and a corresponding algorithm called C1-LT-DISP, which invokes Oracle Documaker. This algorithm is responsible for calling the letter extract program and passing the letter information flat file to the document image generator script defined in the documentation ini file to create a letter image in PDF format. The URL of this PDF file is then returned back to the client browser, which renders the letter image.

To use the base algorithm, navigate to the Installation Options - Framework, and add an entry to the algorithm collection with an algorithm entity of Online Letter Image and the algorithm C1-LT-DISP.

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.

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

<config>

<OTSS-ETPM>

<modulename>OTSS-ETPM</modulename>

<ETPM>

<ApplicationUsername>SYSUSER</ApplicationUsername>

<ApplicationPassword> </ApplicationPassword>

<AdminServer>

<hostname>AdminServer.us.oracle.com</hostname>

<portnumber>7001</portnumber>

<servername>myserver</servername>

<appcontextroot>ouaf</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>

<hostname>  </hostname>

<portnumber> </portnumber>

<servername> </servername>

<username> </username>

<password> </password>

<domainname> </domainname>

</AdminServer>

<ManagedServer>

<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>OTSSETPMJMSServer</serverName>

<ModuleName>OTSSETPMJMSModule</ModuleName>

<SubDeploymentName>OTSSETPMSubDeployment</SubDeploymentName>

<TargetServerName> </TargetServerName>

<PersitentStoreName>OTSSETPMFileStore</PersitentStoreName>

<PersitentStoreType>FileStores</PersitentStoreType>

<PersistentStoreFilename> </PersistentStoreFilename>

</JMS>

</SOA>

<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>

</config>

InstallProperties Descriptions and Examples

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

Property

Description

Example

<config>

<modulename>

Name of the integration module

Default: OTSS-ETPM

Do not change this value.

<ETPM>

<AdminServer>

Currently not used; leave subelements blank

<hostname>

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

<portnumber>

ETPM port number the admin server is listening to

<servername>

Admin ETPM server name

<username>

User name used to log in as an Admin server administrator

<appcontextroot>

Context root of the ETPM 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>

<AdminServer>

<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

<ManagedServer>

<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

<PersitentStoreType>

JMS persistent store name

FileStores

<PersistentStoreFilename>

JMS persistent store type (FileStores )

<DS>

<dba.dbusername>

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

This database hosts the schema required for the ETPMSS 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 ETPM SS 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 OTSSBPEL schema for ETPM SS 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 ETPMSS 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 (this is case sensitive)

true

<dbhostname>

Database host name used for ETPM SS Direct Flows Integration.

Database.us.oracle.com

<dbportnumber>

Database port number used for ETPM SS Direct Flows Integration.

1521

<dbsid>

Database SID used for ETPM-SS 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 ETPM-SS application.

Required RCU Components

Schema Owner

Metadata Services

<PREFIX>_MDS

Appendix C

- ETPM-SS Sample Domain Creation

ETPM-SS Sample Domain Creation

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

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 (when installing into same domain)

- 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 ETPM-SS:

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 ETPM-SS.

Note: The soa_server1 can be installed into a separate domain.

Appendix F

- Installation Properties

Installation Properties

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

<?xmlversion="1.0"standalone="yes"?>

<config>

<WSS>

<modulename>ETPM-SS-APPLICATION</modulename>

<otss>

<username> </username>

<password> </password>

<AdminServer>

<protocol>t3</protocol>

<hostname> </hostname>

<portnumber> </portnumber>

<servername> </servername>

<username> </username>

<password> </password>

<domainname> </domainname>

<realmName> </realmName>

</AdminServer>

<ManagedServer>

<hostname>  </hostname>

<portnumber> </portnumber>

<servername> </servername>

<machine> </machine>

</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> </servername>

<protocol> </protocol>

</ManagedServer>

</SOA>

</WSS>

</config>

ETPM-SS-InstallProperties.xml Descriptions and Examples

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

XPath

Description

Example

Modulename

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

/config/otss/username

The username used to access the ETPM-SS Application. This will be created during the installation.

/config/otss/password

The password that will be used to access the ETPM-SS 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

t3

/config/otss//AdminServer/ hostname

Hostname of Admin Server of WebLogic domain hosting ETPM-SS application

ETPM-SS-hostname.oracle.com

/config/otss//AdminServer/portnumber

Port Number of Admin Server of WebLogic domain hosting ETPM-SS application

7001

/config/otss//AdminServer/servername

Managed server name for the Admin Server hosting server.

AdminServer

/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/domainname

WebLogic domain name hosting ETPM-SS managed server

base_domain

/config/otss//AdminServer/realmname

Realm name of the embedded WebLogic LDAP configured for WebLogic domain hosting ETPM-SS

myrealm

/config/otss//ManagedServer/hostname

Hostname of Managed server hosting ETPM-SS

Note: Will be utilized during installation process.

ETPM-SS-hostname.oracle.com

/config/otss//ManagedServer/portnumber

Managed server port number.

Note: Will be utilized during installation process. This port number should not be already used by a different process on the server.

/config/otss//ManagedServer/servername

Managed server name hosting ETPM-SS

Note: Will be created during installation process.

etpm-ss

/config/otss//ManagedServer/machinename

Machine name to associate with the managed server name hosting ETPM-SS

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

/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 ETPM-SS specific DB objects

WSSADM

/config/otss//DB/dbuserpassword

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

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

Flag to state whether to create database user or user already exist. Valid values:

true – Create user during the installation of ETPM-SS.

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.

DEV_MDS

/config/otss/mdsconfig/mdsdbuserpassword

Password to connect to 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. The value should be 4444.

4444

/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/protocol

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

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 ETPM-SS

- Validates Installation Properties

- Creates a WebLogic managed server

- Links needed Libraries and applications to the WebLogic managed server

- Creates a MetaData Repository mds-OTSS_MDS

- Creates a Database Source WSSDS

- Deploys ETPM-SS shared library

- Configures and Deploys ETPM-SS ear File

- Creates and Installs a Database Schema for ETPM-SS

d

Full uninstallation of ETPM-SS

- Validates Installation Properties

- Removes a WebLogic managed server

- Removes a MetaData Repository mds-OTSS_MDS

- Removes a Database Source WSSDS

- Undeploys ETPM-SS ear File

- Undeploys ETPM-SS shared library

- Drops a Database Schema for ETPM-SS

Note: You will need to manually drop the ETPMSS Schema that was created.

r

Redeployment of ETPM-SS components

- Validates Installation Properties

- Undeploys ETPM-SS Application ear

- Deploys ETPM-SS Application ear

- Undeploys ETPM-SS shared library

- Deploys ETPM-SS 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

ETPM-SS (Public)

http://<ETPM-SS-HostName: < ETPM-SS-Port Number>/etpmss/faces/pages_home

ETPM-SS (Admin)

http://<ETPM-SS-HostName: < ETPM-SS-Port Number>/etpmss/faces/oracle/webcenter/portalapp/pages/login.jspx

Appendix I

- Integration Environment Settings Example

Integration Environment Settings Example

The following is an example of setting the needed environment variables for the ETPMSS-ETPM Integration.

On Linux:

PRODUCT_HOME=/ouaf/versions/Releases/OTSS/BPEL-Release-V1.0.0-InitialInstall/OTSS-ETPM/;

export PRODUCT_HOME

WL_HOME=/etpm-ss/qa2_middleware1035/; export WL_HOME

SOA_HOME=etpm-ss/qa2_middleware1035/Oracle_SOA1; export SOA_HOME

ORACLE_HOME=/etpm-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\etpm-ss\OTSS-Release-V1.0.0-Initialinstall\OTSS-ETPM

SET WL_HOME=C:\etpm-ss\middleware10.3.5;

SET SOA_HOME=C:\etpm-ss\middleware10.3.5\Oracle_SOA1

SET ORACLE_HOME=C:\etpm-ss\middleware10.3.5\Oracle_SOA1;

run C:\etpm-ss\middleware10.3.5\wlserver_10.3\server\bin\setWLSEnv.cmd

cd %PRODUCT_HOME%\bin

For additional details, see Appendix A.

Appendix J

- ETPM-SS Environment Settings Example

ETPM-SS Environment Settings Example

The following is an example of setting the needed environment variables for the installation of ETPM-SS.

On Linux:

PRODUCT_HOME=/etpm-ss/version/OTSS-Release-V1.0.0-Initialinstall/; export PRODUCT_HOME

WL_HOME=/ etpm-ss /middleware10.3.5; export WL_HOME

SOA_HOME=/ etpm-ss /middleware10.3.5/Oracle_SOA1; export SOA_HOME

ORACLE_HOME=/ etpm-ss /middleware10.3.5/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\etpm-ss\OTSS-Release-V1.0.0-Initialinstall\

SET WL_HOME=C:\etpm-ss\middleware10.3.5;

SET SOA_HOME=C:\etpm-ss\middleware10.3.5\Oracle_SOA1

SET ORACLE_HOME=C:\etpm-ss\middleware10.3.5\Oracle_SOA1;

run C:\etpm-ss\middleware10.3.5\wlserver_10.3\server\bin\setWLSEnv.cmd

cd %PRODUCT_HOME%\bin

Table of Contents

Cover Page

Legal Notices

Installation Overview

Additional Resources

Abbreviations

Note for Windows Internet Explorer Users

Roadmap for ETPMSS Installation and Configuration

Software Requirements

ETPMSS Installation

Types of Installation Packages

Pre-Installation Tasks

ETPMSS Installation Directory Structure

Demo Supplemental Contents Overview

ETPMSS Product Installation

Post-Installation Tasks

Configuring ADF Connection for the ETPMSS Application

Configuring UCM for ETPMSS

UCM Configuration: Part 1

UCM Configuration: Part 2

Verifying the Installation

Verifying the ETPMSS Schema Tables

Verifying That the ETPMSS Server is Created

Verifying the WSSDS Data Source

Verifying the mds-OTSSMDS_MDS Data Source

Verifying wasadmin User Creation

Verifying Successful Application Deployment

Accessing the ETPMSS Application

Installing ETPM Integrated Flows

Integration Pre-Installation Tasks

ETPMSS-ETPM (BPEL) Integrated Flows Installation Directory Structure

Completing the Integration Installation

Post-Integration Checklist

Verifying That the OTSS-SOADS Data Source Has Been Created

Verifying That JMS Modules Have Been Created

Verifying That the OTSS-SOADS1 Data Source Has Been Created

Verifying Composites in Enterprise Manager

Additional Installation Instructions for ETPM-SS Demo

Importing UCM Content for Demo Environment

Importing MDS for Demo Environment

Application Override Bundle File

Integrating Documaker with ETPM

Online Document Display and Batch Document Integration with Oracle Documaker

Supported Documaker Versions

Supported Oracle Documaker Templates

Installing and Integrating Documaker Templates with ETPM

Documaker Integration

Oracle Documaker Algorithm

Appendix A

BPEL/SOA installProperties.xml

Appendix B

RCU Database Creation (Sample)

Appendix C

ETPM-SS Sample Domain Creation

Appendix D

Sample Oracle WebLogic Data Sources

Appendix E

Sample Summary of Servers

Appendix F

ETPMSS Installation Properties

Appendix G

Installer Utility Overview

Appendix H

URL Examples

Appendix I

ETPMSS-ETPM Integration Environment Settings Example

Appendix J

ETPM-SS Environment Settings Example