Oracle Utilities Work and Asset Management Connector for Enterprise Resource Planning

Installation Guide

Release 2.1.1

E63505-03

August 2016

Oracle Utilities Work and Asset Management Connector for Enterprise Resource Planning Installation Guide for Release 2.1.1

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

Primary Author: Oracle Corporation

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, then 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 about 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 unless otherwise set forth in an applicable agreement between you and Oracle. 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, except as set forth in an applicable agreement between you and Oracle.

Overview

This guide describes the steps that must be completed to install the Oracle Utilities Work and Asset Management Connector for Enterprise Resource Planning.

Audience

This document is intended for anyone implementing the Oracle Utilities Work and Asset Management Connector for Enterprise Resource Planning product (such as Oracle E-Business Suite, PeopleSoft, JD Edwards EnterpriseOne, Fusion Applications or ERP Cloud).

Integration Documentation and Resources

The following additional documentation resources are available for this release:

Resource

Location

Oracle Utilities Work and Asset Management Connector for Enterprise Resource Planning Installation Guide

The same folder as this document, with the distribution for this product.

Oracle Utilities Work and Asset Management Connector for Enterprise Resource Planning Implementation Guide

The same folder as this document, with the distribution for this product.

Oracle Utilities Work and Asset Management Connector for Enterprise Resource Planning Release Notes

The same folder as this document, with the distribution for this product.

Oracle Utilities Work and Asset Management Documentation:

•

Installation Guide

•

Admin Guide

•

Business User Guide

Refer to Oracle Utilities Work and Asset Management documentation located on the Oracle Technology Network.

Oracle Support

Access the support site for the Certification Matrix for Oracle Utilities Products (Doc ID 1454143.1)

Please refer to Bug #23557782 which will accumulate all WAM patches required for the integration.

Visit the My Oracle Support at https://support.oracle.com website at regular intervals to keep apprised of changes.

Training

Visit Oracle University at http://education.oracle.com/pls/

Web Services Security

For more information about Web services security using Oracle Fusion Middleware 12c refer to https://docs.oracle.com/middleware/12211/cross/webservicestasks.htm.

Oracle Fusion Middleware What's New In Oracle WebLogic Server guide

Section: Standards Support, Supported Configurations and WebLogic Server Compatibility, Database Interoperability

For additional information on the type of database to use.

http://docs.oracle.com/middleware/1221/wls/NOTES/whatsnew.htm#NOTES570

Note : The latest versions of these documents are available on the Oracle Utilities Global Business Unit Portal at:http://docs.oracle.com/cd/E72219_01/documentation.html

Abbreviations

This guide includes the following acronyms and abbreviations:

•

OUWAM or WAM - Oracle Utilities Work and Asset Management

•

ERP - Enterprise Resource Planning System

•

SOA - Service Oriented Architecture

•

EBF - Enterprise Business Flow

•

MDS - Metadata Store

•

DVM - Domain value Map

•

ESS - Oracle Enterprise Scheduler Service

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

Installation

The installation of Oracle Utilities Work and Asset Management Connector for Enterprise Resource Planning is placed on top of an Oracle SOA Suite 12c (12.2.1). Enterprise Resource Planning system and Oracle Utilities Work and Asset Management interact with the middleware to initiate the housed services.

The following sections describe the settings and requirements for a successful installation of Oracle Utilities Work and Asset Management Connector for Enterprise Resource Planning:

•

Integration Pack Software Requirements

•

Pre-Installation Tasks

•

Installation Tasks

•

Verify Generated Artifacts

•

Configure the Certificates of the Mail Server

•

Configure the Edge Applications

•

Security Policies

2.1

Integration Pack Software Requirements

Before installing the integration package, verify that the following applications are properly installed and configured.

2.1.1

Participating Applications

The participating applications are:

•

Oracle Utilities Work and Asset Management v2.1.1 + latest patches appliedInstalled on an Oracle database.

•

Enterprise Resource Planning Application

2.1.2

Oracle SOA/WebLogic Server

The server requirements include:

•

WebLogic Server 12.2.1 with Oracle Enterprise Manager 12c

•

Oracle SOA Suite 12.2.1.0.0

•

Oracle Database 12.1.0.1+; 11.2.0.4+Refer to Integration Documentation and Resources for how to find database documentation.

Oracle attempts to support binary and source-level compatibility between WebLogic Server 12c (12.2.1) and versions 10.3, 10.3.x, 12.1.1, 12.1.2, and 12.1.3 in the areas of persistent data, generated classes, and API compatibility. In some cases, it is impossible to avoid incompatibilities. Where incompatibilities arise, they are fully documented in the Upgrading Oracle WebLogic Server guide.

2.2

Pre-Installation Tasks

Before you begin installing the integration package, complete the following tasks:

1.

Ensure that Oracle SOA Suite is installed and running. For more information, refer to the documentation at http://www.oracle.com/technetwork/middleware/soasuite/documentation/index.html.

2.

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

3.

Ensure that the usermessagingdriver-email application is in Active state. If the application is in Installed state, then the application is not targeted to any managed server.

a.

Click Deployments. The summary of deployment opens.

b.

Click the usermessagingdriver-email link.

c.

Click on the Targets tab.

d.

Select the usermessagingdriver-email checkbox and click the Change Targets button.

e.

For standalone environments, select the soa_server1 option. If it is the Clustered environment, select the cluster or all the clusters you wish to target to as soa_Cluster1. Now, Click Yes button.

f.

Click on Activate Changes button.

4.

Ensure that the WebLogic Admin Server and the Standalone Managed Servers or Clusters are in the Running status with their Health in OK state.

Perform the following steps to complete the additional pre-installation tasks:

1.

Download the Integration Product zip file from Oracle Software Delivery Cloudhttp://edelivery.oracle.com/.

Note : For specific instructions about installing this integration on non-Windows/ Linux platforms, see Oracle Support Knowledge article ID 1349320.1.

2.

Extract the zip file. The package contains the WAM_ERP.zip files.

3.

Extract the WAM_ERP.zip file.This results in a WAM_ERP folder with subfolders, such as config, MDS- Artifacts, services, and install.

The MDS-Artifacts folder contains the EBOs, the WAM schemas and wsdls, dvm and configuration properties file used for this integration.

4.

Set the environment variables:Note: The syntax for PRODUCT_HOME changes depending on whether you are installing on Linux or Windows. The following sections refer to this as $PRODUCT_HOME/ in Linux and as %PRODUCT_HOME%\ in Windows.Excusing any inadvertent syntax errors in this guide, these conventions should be followed for all commands depending on your operating system. Also, as installation commands and arguments are lengthy, please copy the installation commands in a text file and ensure that the command is formatted correctly without any syntax or formatting errors. Linux

Variable

Example

MW_HOME

XXX/Oracle/Middleware

SOA_HOME

$MW_HOME/soa

ORACLE_HOME

$SOA_HOME

PRODUCT_HOME

Set this to the directory where WAM_ERP_INSTALL_HOME.zip is extracted.

Examples :

•

export MW_HOME=/scratch/Oracle/Middleware

•

export SOA_HOME=$MW_HOME/soa

•

export ORACLE_HOME=$SOA_HOME

Windows

Variable

Example

MW_HOME

XXX\Oracle\Middleware

SOA_HOME

%MW_HOME%\soa

ORACLE_HOME

%SOA_HOME%

PRODUCT_HOME

Set this to the directory where WAM_ERP_INSTALL_HOME.zip is extracted.

Examples :

•

set MW_HOME=C:\Oracle\Middleware

•

set SOA_HOME=%MW_HOME%\soa

•

set ORACLE_HOME=%SOA_HOME%

5.

Set up the following weblogic environment variables:

Linux

source $MW_HOME/wlserver/server/bin/setWLSEnv.sh

Windows

%MW_HOME%\wlserver\server\bin\setWLSEnv.cmd

6.

Identify the type of the Domain where this integration is to be installed.

•

Single Managed Server Domain : Provide the <OHS> element in the InstallProperties.xml file with that of the Managed Server details.

•

Clustered Server Domain : Provide the OHS section in InstallProperties.xml file with that of the host name, port number and all the managed servers that are configured in the conf file with comma separated values.for details on the properties

7.

Modify the $PRODUCT_HOME/config/InstallProperties.xml file and ensure that the values are relevant to the server where the integration product is to be installed. You can log in to the WebLogic console to cross-verify the values being entered for these properties. The build will fail if inappropriate values are added.

Refer to Chapter 5 Installation Properties for a list of the properties available in the deploy.properties file along with descriptions of property usage and default values, where applicable.

Note : Do not delete the WAM_ERP directory. This directory is used as the download location for patches as they are released.

For a Windows installation, when updating any of the properties, add "\" to the path. For example: C:\ WAM_ERP

2.3

Installation Tasks

This section provides guidelines for the following tasks:

•

Installing the Integration

•

Configure Error Notification Rules (Optional)

2.3.1

Installing the Integration

This section describes about the installation of the OUWAMERP integration in the Linux environments or Windows environments.

2.3.1.1

Linux Environments

To install the OUWAMERP integration in the Linux environments, perform the following steps:

1.

Change the directory to the location where the OUWAMERP product has been extracted and go to the bin directory under the product home using the command:

cd $PRODUCT_HOME/bin

2.

Execute the command at the directory to create the database artifacts such as error handling schema, tables and rows:

ant -f InstallBuild.xml installDB -DInstallProperties=$PRODUCT_HOME/config/ InstallProperties.xml -l InstallDB.log

3.

Execute the command at the directory to install all the WebLogic Java resources such as JMS servers, JMS modules, JMS queues:

ant -f InstallBuild.xml installWL -DInstallProperties=$PRODUCT_HOME/config/ InstallProperties.xml -l InstallWL.log

4.

Restart the Managed Servers and Admin Servers from the WebLogic Administration Console to ensure that all Java resources are activated.Note, all Java resources need to be restarted.After the Managed Servers and the Admin Server are restarted complete the following:

5.

Execute the command to create the partitions, update the MDS with artifacts and deploy the composites.

ant -f InstallBuild.xml installSOA -DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml -l InstallSOA.log

6.

Restart the managed servers and admin servers through the WebLogic Administration Console to ensure that all the SOA composites are in healthy state to create the instances.

2.3.1.2

Windows Environments

To install the OUWAMERP integration in Windows environments, perform the following steps:

1.

Change the directory to the location where the OUWAMERP product has been extracted and go to the bin directory under the product home using the command:

cd %PRODUCT_HOME%\bin

2.

Execute the command at the directory to create the database artifacts such as Error handling schema,tables and rows:

ant -f InstallBuild.xml installDB -DInstallProperties=%PRODUCT_HOME%\

config\InstallProperties.xml -l InstallDB.log

3.

Execute the command at the directory to install all the WebLogic Java resources, such as JMS servers, JMS modules, JMS queues:

ant -f InstallBuild.xml installWL -DInstallProperties=%PRODUCT_HOME%\

config\InstallProperties.xml -l InstallWL.log

4.

Restart the Managed Servers and Admin Servers through the Weblogic Administration Console to ensure that all the Java resources, which need to be restart gets activated.After the Managed Servers and the Admin Server are restarted complete the following:

5.

Execute command to create the partitions, update the MDS with artifacts and deploy the composites:

ant -f InstallBuild.xml installSOA -DInstallProperties=%PRODUCT_HOME%\

config\InstallProperties.xml -l InstallSOA.log

6.

Restart the Managed Servers and Admin Servers through the WebLogic Administration Console to ensure that all the SOA composites are in healthy state to create the instances.

2.3.2

Configure Error Notification Rules (Optional)

The integration uses the Oracle Utilities common integration error handling framework, however if you want to use the SOA Suite 12c error hospital feature, you can implement it using the following guidelines.

Error notification rule(s) can be created on the OUWAMERP partition using the ESS schedule to get the frequency of the error notification rule execution. To create error notification rules at the partition level, perform the following steps:

1.

Right-click on the OUWAMERP partition.

2.

Select Error Notification Rules. The Error Notification Rules page opens.

3.

Click Create to create a new rule and enter the following information:

•

Name

•

Description

•

Schedule Name (Select the schedule created through the scripts OUWAMERPNotificationSchedule )

•

Use the IF-THEN table to define the fault notification rule, and click Apply.This table can be used to set the Fault conditions and also the email notification address for the administrator.

For more information about error hospital and error notifications, see the section "Recovering From Faults in the Error Hospital" in Oracle Fusion Middleware Administering Oracle SOA Suite and Oracle Business Process Management Suite documentation.

2.4

Verify Generated Artifacts

As a result of the installation, the following artifacts are created on the weblogic server instance.

After completing the installation steps, complete the verification tasks to finalize the installation.

•

JMS Server

•

File Store

•

JMS Module

•

Sub Deployment

•

JMS Adapter Outbound Connection Pool

•

JMS Connection Factory

•

Credential Map

•

User Messaging Email Driver

•

ESSAPP Schedules (Optional)

•

SOA Partition

2.4.1

JMS Server

Verify OUWAMERPJMSServer

In the Administration console, under the Domain Structure, expand the Services (by clicking the + sign next to it), expand the Messaging (by clicking the + sign next to it), and then click JMS Servers.

2.4.2

File Store

Verify OUWAMERPFileStore

In the Administration console, under the Domain Structure, expand the Services (by clicking the + sign next to it), and then click Persistent Store.

2.4.3

JMS Module

Verify OUWAMERPJMSModule

In the Administration console, under the Domain Structure, expand the Services (by clicking the + sign next to it), expand the Messaging (by clicking the + sign next to it), and then click JMS Modules.

2.4.4

Sub Deployment

Verify OUWAMERPSubDeployment

In the Administration console, under the Domain Structure, expand the Services (by clicking the + sign next to it), expand the Messaging (by clicking the + sign next to it), and then click JMS Modules. Select the OUWAMERPJMSModule and click on the Subdeployments tab.

2.4.5

JMS Adapter Outbound Connection Pool

Verify eis/wls/OUWAMERPQueue

In the Administration console, under the Domain Structure, expand the Deployments (by clicking the + sign next to it) and find the .rar file name with JmsAdapter_OUWAMERP. Click on it and click on the Configuration tab and in that, click on the Outbound Connection Pools tab.

Expand "oracle.tip.adapter.jms.IJmsConnectionFactory". It should be deployed with "eis/wls/OUWAMERPQueue".

2.4.6

JMS Connection Factory

Verify OUWAMERPConnectionFactory and JMS Queues List

In the Administration console,under the Domain Structure, expand the Services (by clicking the + sign next to it), and then expand the Messaging (by clicking the + sign next to it), and then click JMS Modules. Select the OUWAMERPJMSModule.

2.4.6.1

Request/Response Queues

Ensure that all the listed queues along with the ConnectionFactory as depicted above are created as part of the installation:

Connection Factory: OUWAMERPConnectionFactory

Queues:

Module

Request/Response Queues

Corresponding Error Queues

ERP to WAM Accounting Entry

OUWAMERPAccountingEntryFromERPRequest

OUWAMERPAccountingEntryFromERPResponse

OUWAMERPAccountingEntryFromERPRequestError

OUWAMERPAccountingEntryFromERPResponseError

WAM to ERP Accounting Entry

OUWAMERPAccountingEntryFromWAMRequest

OUWAMERPAccountingEntryFromWAMResponse

OUWAMERPAccountingEntryFromWAMRequestError

OUWAMERPAccountingEntryFromWAMResponseError

ERP to WAM Blanket Purchase Agreement

OUWAMERPBlanketPurchaseAgreementRequest

OUWAMERPBlanketPurchaseAgreementResponse

OUWAMERPBlanketPurchaseAgreementRequestError

OUWAMERPBlanketPurchaseAgreementResponseError

ERP to WAM Chart of Accounts

OUWAMERPChartOfAccountsRequest

OUWAMERPChartOfAccountsResponse

OUWAMERPChartOfAccountsRequestError

OUWAMERPChartOfAccountsResponseError

ERP to WAM Disbursement Payment (Invoice Payment)

OUWAMERPDisbursementPaymentRequest

OUWAMERPDisbursementPaymentResponse

OUWAMERPDisbursementPaymentRequestError

OUWAMERPDisbursementPaymentResponseError

ERP to WAM Invoice

OUWAMERPInvoiceFromERPRequest

OUWAMERPInvoiceFromERPResponse

OUWAMERPInvoiceFromERPRequestError

OUWAMERPInvoiceFromERPResponseError

ERP to WAM Item Balance

OUWAMERPItemBalanceRequest

OUWAMERPItemBalanceResponse

OUWAMERPItemBalanceRequestError

OUWAMERPItemBalanceResponseError

WAM to ERP Material Requisition

OUWAMERPMaterialRequisitionRequest

OUWAMERPMaterialRequisitionResponse

OUWAMERPMaterialRequisitionRequestError

OUWAMERPMaterialRequisitionResponseError

ERP to WAM Material Issue

OUWAMERPMatIssueInventoryTxnRequest

OUWAMERPMatIssueInventoryTxnResponse

OUWAMERPMatIssueInventoryTxnRequestError

OUWAMERPMatIssueInventoryTxnResponseError

ERP to WAM Material Return

OUWAMERPMatReturnInventoryTxnRequest

OUWAMERPMatReturnInventoryTxnResponse

OUWAMERPMatReturnInventoryTxnRequestError

OUWAMERPMatReturnInventoryTxnResponseError

ERP to WAM Purchase Order

OUWAMERPPurchaseOrderRequest

OUWAMERPPurchaseOrderResponse

OUWAMERPPurchaseOrderRequestError

OUWAMERPPurchaseOrderResponseError

ERP to WAM Purchase Return

OUWAMERPPurReturnInventoryTxnRequest

OUWAMERPPurReturnInventoryTxnResponse

OUWAMERPPurReturnInventoryTxnRequestError

OUWAMERPPurReturnInventoryTxnResponseError

WAM to ERP Purchase Requisition

OUWAMERPRequisitionRequest

OUWAMERPRequisitionResponse

OUWAMERPRequisitionRequestError

OUWAMERPRequisitionResponseError

ERP to WAM Receipt

OUWAMERPShipmenReceiptRequest

OUWAMERPShipmenReceiptResponse

OUWAMERPShipmenReceiptRequestError

OUWAMERPShipmenReceiptResponseError

ERP to WAM Stock Item

OUWAMERPStockItemRequest

OUWAMERPStockItemResponse

OUWAMERPStockItemRequestError

OUWAMERPStockItemResponseError

ERP to WAM Storeroom

OUWAMERPStoreroomItemRequest

OUWAMERPStoreroomItemResponse

OUWAMERPStoreroomItemRequestError

OUWAMERPStoreroomItemResponseError

ERP to WAM Supplier Party

OUWAMERPSupplierPartyFromERPRequest

OUWAMERPSupplierPartyFromERPResponse

OUWAMERPSupplierPartyFromERPRequestError

OUWAMERPSupplierPartyFromERPResponseError

WAM to ERP Supplier Party

OUWAMERPSupplierPartyFromWAMRequest

OUWAMERPSupplierPartyFromWAMResponse

OUWAMERPSupplierPartyFromWAMRequestError

OUWAMERPSupplierPartyFromWAMResponseError

ERP to WAM Worker

OUWAMERPWorkerRequest

OUWAMERPWorkerResponse

OUWAMERPWorkerRequestError

OUWAMERPWorkerResponseError

2.4.7

Credential Map

Verify OUWAM_01

In the Enterprise Manager console, open the Weblogic Domain and from that select the soa_domain and right-click to open Security > Credentials section and expand the oracle.wsm.security map to find the OUWAM_01 key.

2.4.8

User Messaging Email Driver

Verify usermessagingdriver-OUWAMERP

In the Enterprise Manager console, expand the User Messaging Service. Right-click on the usermessagingdriver-email, and then select the Email Driver Properties option. Now, select the usermessagingdriver-OUWAMERP and click the Edit button.

2.4.9

ESSAPP Schedules (Optional)

Verify OUWAMERPNotificationSchedule

In the Enterprise Manager console, expand the Scheduling Services. Right-click on the ESSAPP, select the Job Requests menu and click Define Schedules. Click the OUWAMERPNotificationSchedule schedule.

2.4.10

SOA Partition

Verify OUWAMERP and SOA Composites

In the Enterprise Manager console, expand the SOA. Click on the soa-infra, select the OUWAMERP partition and check that all the composites are deployed and in up and running state.

2.4.10.1

Composites List

The following table provides a listing of the composites that must be deployed:

Module

Request Processes

Response Processes

ERP to WAM Accounting Entry

SyncAccountingEntryERPReq

ABCSImpl

SyncAccountingEntryOUWAMUtilitiesProv

ABCSImpl

SyncAccountingEntryRespOUWAMUtilitiesReqABCSImpl

WAM to ERP Accounting Entry

SyncAccountingEntryOUWAMUtilitiesReq

ABCSImpl

SyncAccountingEntryRespOUWAMUtilitiesProvABCSImpl

SyncAccountingEntryRespERPReq

ABCSImpl

ERP to WAM Blanket Purchase Agreement

SyncBlanketPurchaseAgreementERPReq

ABCSImpl

SyncBlanketPurchaseAgreementOUWAM

UtilitiesProvABCSImpl

SyncBlanketPurchaseAgreementResp

OUWAMUtilitiesReqABCSImpl

ERP to WAM Chart of Accounts

SyncChartOfAccountsERPReq

ABCSImpl

SyncChartOfAccountsOUWAMUtilitiesProv

ABCSImpl

SyncChartOfAccountsRespOUWAMUtilitiesReqABCSImp

ERP to WAM Disbursement Payment (Invoice Payment)

SyncDisbursementPaymentERPReq

ABCSImpl

SyncDisbursementPaymentOUWAMUtilitiesProv

ABCSImpl

SyncDisbursementPaymentResp

OUWAMUtilitiesReqABCSImpl

ERP to WAM Invoice

SyncInvoiceERPReq

ABCSImpl

SyncInvoiceOUWAMUtilitiesProv

ABCSImpl

SyncInvoiceRespOUWAMUtilitiesReq

ABCSImpl

ERP to WAM Item Balance

SyncItemBalanceERPReq

ABCSImpl

SyncItemBalanceOUWAMUtilitiesProv

ABCSImpl

SyncItemBalanceRespOUWAMUtilitiesReq

ABCSImpl

WAM to ERP Material Requisition

SyncMaterialRequisitionOUWAMUtilitiesReq

ABCSImpl

SyncMaterialRequisitionRespOUWAMUtilitiesProvABCSImpl

SyncMaterialRequisitionRespERPReq

ABCSImpl

ERP to WAM Material Issue

SyncMatIssueInventoryTxnERPReq

ABCSImpl

SyncMatIssueInventoryTxnOUWAMUtilitiesProv

ABCSImpl

SyncMatIssueInventoryTxnResp

OUWAMUtilitiesReqABCSImpl

ERP to WAM Material Return

SyncMatReturnInventoryTxnERPReq

ABCSImpl

SyncMatReturnInventoryTxnOUWAMUtilitiesProv

ABCSImpl

SyncMatReturnInventoryTxnResp

OUWAMUtilitiesReqABCSImpl

ERP to WAM Purchase Order

SyncPurchaseOrderERPReq

ABCSImpl

SyncPurchaseOrderOUWAMUtilitiesProv

ABCSImpl

SyncPurchaseOrderRespOUWAMUtilitiesReq

ABCSImpl

ERP to WAM Purchase Return

SyncPurReturnInventoryTxnERPReq

ABCSImpl

SyncPurReturnInventoryTxnOUWAMUtilitiesProv

ABCSImpl

SyncPurReturnInventoryTxnResp

OUWAMUtilitiesReqABCSImpl

WAM to ERP Purchase Requisition

SyncRequisitionOUWAMUtilitiesReq

ABCSImpl

SyncRequisitionRespOUWAMUtilitiesProv

ABCSImpl

SyncRequisitionRespERPReq

ABCSImpl

ERP to WAM Receipt

SyncShipmentReceiptERPReq

ABCSImpl

SyncShipmentReceiptOUWAMUtilitiesProv

ABCSImpl

SyncShipmentReceiptRespOUWAMUtilitiesReqABCSImpl

ERP to WAM Stock Item

SyncStockItemERPReq

ABCSImpl

SyncStockItemOUWAMUtilitiesProv

ABCSImpl

SyncStockItemRespOUWAMUtilitiesReq

ABCSImpl

ERP to WAM Storeroom

SyncStoreroomItemERPReq

ABCSImpl

SyncStoreroomItemOUWAMUtilitiesProv

ABCSImpl

SyncStoreroomItemRespOUWAMUtilitiesReq

ABCSImpl

ERP to WAM Supplier Party

SyncSupplierPartyERPReq

ABCSImpl

SyncSupplierPartyOUWAMUtilitiesProv

ABCSImpl

SyncSupplierPartyRespOUWAMUtilitiesReq

ABCSImpl

WAM to ERP Supplier Party

SyncSupplierPartyOUWAMUtilitiesReq

ABCSImpl

SyncSupplierPartyRespERPReq

ABCSImpl

SyncSupplierpartyRespOUWAMUtilitiesProv

ABCSImpl

ERP to WAM Worker

SyncWorkerERPReq

ABCSImpl

SyncWorkerOUWAMUtilitiesProv

ABCSImpl

SyncWorkerRespOUWAMUtilitiesReq

ABCSImpl

2.5

Configure the Certificates of the Mail Server

To configure the certificates, perform the following steps:

1.

Import the certificates from the Mail Server and add it to your server trust store.Email Server uses two protocols to send/receive messages:SMTP for sending. POP3 or IMAP for receiving mails. Configure the receiving protocol accordingly. For example, POP3/IMAP.

2.

Get the <Mail Server> certificate:

/usr/bin/openssl s_client -connect <Mail Server>:<Mail Port Number> > smtp.cert

Where <Mail Server> is the SMTP server location and <MailPort Number> is the Mail Server listening port.

Example:

/usr/bin/openssl s_client -connect stxxx.yourcompany.com:425 >smtp.cert

3.

Edit the smtp.cert by removing everything except the following:

--BEGIN CERTIFICATE--

<certificate>

--END CERTIFICATE--

Important : The BEGIN CERTIFICATE and END CERTIFICATE lines must remain in the file.

4.

Import the certificates into a new trust store:

keytool -import -alias <Mail Server> -keystore ${WL_HOME}/server/lib/trusted-certificates.jks -file smtp.cert

Note : You will be prompted to enter a password. Enter <password>.

5.

Edit the setDomainEnv.cmd or setDomainEnv.sh file (located in <WL_HOME>/user_projects/domains/<domain_name>/bin) by replacing the existing javax.net.ssl.trustStore property setting with the following:

Djavax.net.ssl.trustStore=${WL_HOME}/server/lib/trusted-certificates.jks -Djavax.net.ssl.trustStorePassword=<password>

6.

Restart the Admin Server and the Managed Server.

2.6

Configure the Edge Applications

Configure Oracle Utilities Work and Asset Management Integration and Enterprise Resource Planning system installation according to the guidelines in the Implementation Guide for this integration package.

2.7

Security Policies

When a composite needs to invoke an edge application web service, an appropriate security policy should be attached to the reference web service of the composite.

•

Invoking edge application XAI Service.

When calling an edge application XAI service, the security policy to attach to the reference web service of the composite is oracle/wss_http_token_client_policy.

•

Invoking edge application Inbound Web Service (IWS).

When calling an edge application Inbound Web Service (IWS), the security policy to attach to the reference web service of the composite is dependent on the annotation specified in the IWS wsdl.

•

If a security policy annotation is specified in the edge application’s Inbound Web Service, use the policy specified.

Example 1: The policy defined in the IWS wsdl is UsernameToken, meaning that oracle/wss_username_token_client_policy should be attached to the composite’s reference web service.Example 2: The policy defined in the IWS wsdl is Https-BasicAuth xml meaning that HTTP Basic Authentication over SSL Including Timestamp is required. The oracle/wss_http_token_over_ssl_client_policy should be attached to the composite’s reference web service.

•

If no security policy annotation is specified in the edge application’s Inbound Web Service and the edge application is using Framework 4.3.0.2.0 or higher, a default security policy oracle/wss_http_token_over_ssl_client_policy will be use by the edge application’s Inbound Web Service. The default policy can be changed in the edge application’s Feature Configuration Menu. Refer to the implementation guide for the specific edge application for more information.

•

If the edge application is using Framework 4.2.0, a security policy annotation has to be specified in the edge application’s Inbound Web Service. In this version of framework, there is no default security policy specified. oracle/wss_http_token_client_policy has to be specified in the edge application’s Inbound Web Service security policy annotation.

Individual Composites

This section describes how to deploy/ undeploy individual composites for incremental builds or patches:

•

Deploy the Individual Composites

•

Undeploy Composites

3.1

Deploy the Individual Composites

Perform the following steps to deploy individual composites.

1.

Open a Command prompt and execute the following:

Linux

cd $PRODUCT_HOME/bin

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

Windows

cd %PRODUCT_HOME%\bin

ant -f DeployUndeployUtility.xml -DInstallProperties=%PRODUCT_HOME%\config\

InstallProperties.xml DeployComposite

2.

Validate the following parameters when prompted with the default values during deployment. Press ENTER to use the default prompted value:

a.

Composite Name : The name of the composite to be deployed to the SOA server. This parameter does not have a default value.Enter the composite name to be deployed.For example: SyncSupplierPartyERPReqABCSImpl

b.

Composite Folder Location : The folder name should be an absolute path, beginning with <PRODUCT_HOME>/services/industry/Utilities/<EBF/utility>.For example: If you are planning to deploy the composite from

<PRODUCT_HOME>/services/industry/Utilities/EBF,

then pass

<PRODUCT_HOME>/services/industry/Utilities/EBF

to this property.

The default value for this property is <PRODUCT_HOME>/services/ industry/Utilities/EBF, as most of the business-specific composites reside in this folder.Note: The syntax should be changed depending whether you are using Windows or Linux.

c.

SOA Partition Name : The SOA partition name to which the composite should be deployed.

3.2

Undeploy Composites

Perform the following steps to undeploy individual composites:

1.

Open a Command prompt and execute the following:

Linux

cd $PRODUCT_HOME/bin

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

Windows

cd %PRODUCT_HOME%\bin

ant -f DeployUndeployUtility.xml -DInstallProperties=%PRODUCT_HOME%\config\

InstallProperties.xml UnDeployComposite

2.

Validate the following parameters when prompted with the default values during deployment. Press ENTER to use the default prompted value:

a.

Composite Name : The name of the composite to be undeployed from SOA server.This parameter does not have a default value.Enter the composite name to be un-deployed.For example: SyncSupplierPartyERPReqABCSImpl

b.

Composite Folder Location : The folder name should be an absolute path, beginning with <PRODUCT_HOME>/services/industry/Utilities/<EBF/utility>.For example: If you are planning to undeploy the composite from

<PRODUCT_HOME>/services/industry/Utilities/EBF, then pass

<PRODUCT_HOME>/services/industry/Utilities/EBF to this property.

The default value for this property is <PRODUCT_HOME>/services/ industry/Utilities/EBF, as most of the business-specific composites reside in this folder.Note: The syntax should be changed depending whether you are using Windows or Linux.

c.

SOA Partition Name : The SOA partition name from which the composite should be undeployed.

Metadata Store (MDS) Artifacts

This section describes how to deploy and undeploy individual Metadata Store (MDS) folders for incremental builds or patches:

•

Deploy the MDS Folder

•

Undeploy the MDS Folder

Note: The MDS Folder Name is the name of the folder that can be deployed/undeployed from the MDS repository. This folder name should be a relative path inside the PRODUCT_HOME/MDS-Artifacts, beginning with OUWAMERP.

4.1

Deploy the MDS Folder

Perform the following steps to deploy MDS folder.

Open the Command prompt and execute the following commands:

Linux

cd $PRODUCT_HOME/bin

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

Windows

cd %PRODUCT_HOME%\bin

ant -f DeployUndeployUtility.xml -DInstallProperties=%PRODUCT_HOME%\config\

InstallProperties.xml DeployMDS

4.2

Undeploy the MDS Folder

Perform the following steps to undeploy MDS folder.

Open the Command prompt and execute the following commands:

Linux

cd $PRODUCT_HOME/bin

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

•

Windows Environment:

cd %PRODUCT_HOME%\bin

ant -f DeployUndeployUtility.xml -DInstallProperties=%PRODUCT_HOME%\config\

InstallProperties.xml UnDeployMDS

Installation Properties

This section includes a listing of applicable installation properties.

Ensure you follow XML editing standards while editing the InstallProperties.xml file. All XML elements need to be closed properly. XML element in the InstallProperties.xml file does not contain any attribute.

Note : If the dbuser.createflag is set to false, the schema needed for integration error handling will not be automatically created by the install and will need to be created manually prior to running the installation. When creating the user manually, grant connect and resource to the user.

The table below lists the properties available in the InstallProperties.xml file along with their usage. The default values are specified wherever applicable.

Property (XPath Representation)

Description

Example

WAM Information

EdgeApplications/OUWAM/Protocol

The protocol on which the application is accessible.

http or https

EdgeApplications/OUWAM/Host

The host name of Oracle Utilities Work and Asset Management application.

xxx.us.mycompany.com

EdgeApplications/OUWAM/Port

The port number of Oracle Utilities Work and Asset Management application.

1961

EdgeApplications/OUWAM/ContextRoot

The context root of the application.

•

ouaf/XAIApp/xaiserver

•

ouaf/webservices for XAI services

•

IWS services (respectively).

EdgeApplications/OUWAM/ApplicationUsername

The login user name of the application.

EdgeApplications/OUWAM/ApplicationPassword

The login password of the application.

EdgeApplications/OUWAM/mapname

The credential map name for Oracle Utilities Work and Asset Management application.

OUWAM_1

EdgeApplications/OUWAM/policy

The security policy that OUWAM accepts.

oracle/wss_http_token_client_policy (XAI services) or for IWS service, refer to section 2.7 Security Policies to determine which security policy to attach.

ERP Information

EdgeApplications/ERP/ApplicationUsername

The user name for Enterprise Resource Planning application.

Uname1

EdgeApplications/ERP/ApplicationPassword

The password for Enterprise Resource Planning application.

Pwd1

SOA Admin Server Information

SOA/AdminServer/hostname

The Admin Server of the SOA application.

xxx.us.oracle.com

SOA/AdminServer/portnumber

The Admin Server of the SOA port number.

7001

SOA/AdminServer/servername

The server name of the Admin Server.

Admin Server

SOA/AdminServer/username

The user name for the Admin Server.

Weblogic

SOA/AdminServer/password

The password of the Admin Server.

xxxxxx

SOA/AdminServer/domainname

The domain name of the SOA Admin Server.

soa_domain

SOA Managed Server Information

SOA/ManagedServer/hostname

The host name

of the SOA Managed Server.

xxx.us.oracle.com

SOA/ManagedServer/portnumber

The port number of the SOA Managed Server.

8001

SOA/ManagedServer/servername

The name of the SOA Managed Server.

soa_server1

SOA/ManagedServer/username

The user name of the SOA Managed Server.

Weblogic

SOA/ManagedServer/password

The password of SOA Managed Server.

xxxx

Oracle HTTP Server Information

SOA/OHS/hostname

The host name of the Oracle HTTP Server.

xxx.us.mycompany.com

SOA/OHS/portnumber

The port number of the Oracle HTTP Server.

7777

SOA/OHS/servernames

The list of server names that are defined as Managed Servers/Clusters.

Soa_cluster (In case of Cluster),soa_server1

(If standalone same as the one

provided in the managedserver)

MDS DB Information

SOA/mdsconfig/mdsdbusername

The DB user name of the MDS configuration.

Xyxxx

SOA/mdsconfig/mdsdbuserpassword

The DB password of the MDS configuration.

****

SOA/mdsconfig/mdsdbhostname

The DB host name of the MDS configuration.

Xyz.us.oracle.com

SOA/mdsconfig/mdsdbportnumber

The DB port number MDS configuration.

1521

SOA/mdsconfig/mdsdbsid

The MDS RCU created SID.

ABCD

JMS Information

SOA/JMS/serverName

The JMS server name.

OUWAMERPJMSServer

SOA/JMS/ModuleName

The JMS module name.

OUWAMERPJMSModule

SOA/JMS/SubDeploymentName

The Subdeployment name.

OUWAMERPSubDeployment

SOA/JMS/JMSServerTarget

The SOA Managed Server Target for JMS server.

soa_server1

SOA/JMS/JMSModuleTargets

The JMS Module targeted SOA managed servers/Clusters.

soa_server1,soa_server2 (OR) soa_cluster1

SOA/JMS/PersitentStoreName

The file store persistence details.

OUWAMERPFileStore

SOA/JMS/PersitentStoreType

FileStores

SOA/JMS/PersistentStoreFilename

The location of the persistence file.

/scratch/Oracle/Product_Homes/OUWAMERP

/OUWAMERPFileStore

SOA/JMS/JMSCFName

The file name of the ConnectionFactory.

OUWAMERPConnectionFactory

SOA/JMS/JMSCFJNDI

The JNDI file name of the ConnectionFactory.

jms/OUWAMERPConnectionFactory

Email Information

SOA/EMAIL/MailAccessProtocol

The protocol of the Mail Access.

IMAP

SOA/EMAIL/OutgoingDefaultFromAddr

The email address from which the outgoing mails are sent.

SOA/EMAIL/OutgoingMailServer

The mail server name from where the mails are sent.

host.yourdomain.com

SOA/EMAIL/OutgoingMailServerPort

The port number of the outgoing mail server.

465

SOA/EMAIL/OutgoingMailServerSecurity

The security for the outgoing mail server.

SSL

SOA/EMAIL/OutgoingUsername

The user name of the outgoing email.

SOA/EMAIL/Outgoingpassword

The password of the outgoing email.

SOA/EMAIL/IncomingMailServer

The mail server name where mail is received.

host.yourdomain.com

SOA/EMAIL/IncomingUserIDs

Incoming user IDs.

SOA/EMAIL/IncomingUserPasswords

Incoming passwords

SOA/EMAIL/applicationName

The application for which the UMS configuration is considered.

WAMERP

Workflow Notification Properties

SOA/WorkFlow.Notification/from.emailid

xyz@yourcompany.com

SOA/WorkFlow.Notification/mode

EMAIL

Error Handling Database Information

EH/dba.dbusername

User name to log in as a database administrator (DBA). This database hosts the schema required for the integration.

System

EH/dba.dbuserpassword

Password to log in as a database administrator (DBA). This database hosts the schema required for the integration.

EH/dbusername

User name to log in to the error handling schema for the integration. integration. This User can be automatically created by the install (set dbuser.createflag to true) or manually outside the install process.

WAMERP_User

SOA/dbuserpassword

Password to log in to the error handling schema for the integration.

EH/dbuser.createflag

If set to true, the db user can be automatically created by the install.

If this value is set to false, the schema needed for integration error handling will not be automatically created by the install and will need to be created manually prior to running the installation. When creating the user manually, grant connect and resource to the user.

true

EH/dbhostname

The DB Hostname of the error handling schema for the integration.

EH/dbportnumber

The DB Port of the error handling schema for the integration.

EH/dbsid

The DB SID of the error handling schema for the integration.

Troubleshooting

This chapter describes issues that may arise during installation.

6.1

Password Expiry for Database

If a password is expired or changed, then credential issues may arise with Meta Data Store (MDS) or Error Handling (EH) Data Store or integration specific database. To fix this issue, perform the following steps:

1.

Reset or unlock the password for the corresponding database (MDS, EH database or integration specific database).

2.

Change the password for the data source for which the password is changed/or locked from the Weblogic Administration Console.

3.

Change the password in the InstallationProperties.xml for the database instance (this helps only while reinstalling).

4.

Perform the following steps to find the adf-config.xml file that is generated during installation. The file is generally located at $PRODUCT_HOME/install/config/adf/META-INF.

a.

Identify the correct "metadata-store-usage" from the "meta-data-namespaces" element by the path mentioned above.

b.

In the "metadata-store-usage" element, find the element property with the attribute value as "jdbc-password" for the "name" attribute.

c.

Change the password for the value attribute in the property element.

Uninstalling

This section provides steps for:

•

Uninstalling Linux Environments

•

Uninstalling Windows Environments

•

Uninstalling the UsageMessagingDriver-Email

7.1

Uninstalling Linux Environments

To uninstall in a Linux environment:

1.

Change the directory to the location where the OUWAMERP product has been extracted and navigate to the bin directory under the product home using the command:

cd $PRODUCT_HOME/bin

2.

Execute the command to remove the MDS artifacts and undeploy the composites and delete the SOA partition:

ant -f UnInstallBuild.xml uninstallSOA -DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml -l UnInstallSOA.log

3.

Execute the command at the directory to uninstall all the WebLogic Java resources such as JMS servers, JMS modules, JMS queues:

ant -f UnInstallBuild.xml uninstallWL -DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml -l UnInstallWL.log

4.

Execute the command at the directory to delete the database artifacts such as Error handling schema,tables and rows.

ant -f UnInstallBuild.xml uninstallDB -DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml -l InstallDB.log

5.

Restart the Managed Servers and Admin Servers through the WebLlogic Administration Console to ensure that all the artifacts are deleted/unmounted.

7.2

Uninstalling Windows Environments

To uninstall in a Windows environment:

1.

Change the directory to the location where the OUWAMERP product has been extracted and go to the bin directory under the product home using the command:

cd %PRODUCT_HOME%\bin

2.

Execute the command to delete the MDS artifacts and undeploy the composites and delete the partition:

ant -f UnInstallBuild.xml unInstallSOA -DInstallProperties=%PRODUCT_HOME%\

config\InstallProperties.xml -l UnInstallSOA.log

3.

Execute the command at the directory to uninstall all the WebLlogic Java resources such as JMS Servers, JMS modules, JMS queues:

ant -f UnInstallBuild.xml uninstallWL -DInstallProperties=%PRODUCT_HOME%\

config\InstallProperties.xml -l UnInstallWL.log

4.

Execute the command at the directory to create the database artifacts such as Error handling schema,tables and rows:

ant -f UnInstallBuild.xml uninstallDB -DInstallProperties=%PRODUCT_HOME%\

config\InstallProperties.xml -l InstallDB.log

5.

Restart the Managed Servers and Admin Servers through the WebLlogic Administration Console to ensure that all the artifacts are deleted/unmounted.

7.3

Uninstalling the UsageMessagingDriver-Email

To uninstall the UsageMessagingDriver:

1.

Open the Enterprise Manager console.

2.

Expand the Usage Message Service.

3.

Right-click on the usermessagingdriver-email.

4.

Select the Email Driver Properties menu item.

5.

In the Email Driver Properties table, find the row with the instance set as "usermessagingdriver-OUWAMERP".

6.

Click Delete.

7.

Click Yes in the confirmation dialog box.