PROCESSIT Installation

Introduction

This document describes how to install PROCESSIT. A section of the document is devoted to installing PROCESSIT Virtual Appliance. Please refer to the respective installation guides for installing SOA and WebLogic servers separately.

The PROCESSIT Installation Wizard guides you through the installation, but please read this document prior to installation.

This document also highlights how to ensure a smooth cut-over when transferring from one environment to another.

Please refer to standard ReadSoft documentation for DOCUMENTS, INVOICES and REPORTER installation and configuration.

PROCESSIT Architecture Overview

The PROCESSIT solution consists of different components that must be installed individually.

• INVOICES Scanning server with PROCESSIT integration option enabled.
• INVOICES Scanning clients installed.
• PROCESSIT SOA server and WebLogic User Interface server.

PROCESSIT is integrated with Oracle E-Business Suite R12. Anyone performing a PROCESSIT installation is assumed to know the details about the Oracle E-Business Suite database.

Prerequisites

For details regarding PROCESSIT requirements, see PROCESSIT System Requirements.

Installation computer

The computer used to perform the PROCESSIT installation to the SOA and WebLogic servers must have a Windows or Linux operating system, have internet access, and Java JDK version 1.5+ must be installed. Java must be correctly configured with the JAVA_HOME environment variable pointing to the JDK installation directory and the PATH must include $JAVA_HOME/bin.

Java JDK version 1.6 is recommended.

INVOICES scanning

INVOICES is the scanning and interpretation part of the ReadSoft solution. ReadSoft INVOICES scanning server and clients must be installed with PROCESSIT integration enabled. Please follow the instructions in the document ReadSoft_PROCESSIT_installation_Connector.

Oracle E-Business Suite R12

You must be using Oracle E-Business Suite R12 patched to 12.0.6 +.

PROCESSIT SOA server

• Oracle BPEL Process Manager (a component of Oracle SOA Suite) 10.1.3.5 patched to the latest MLR2 level
• Patched to latest MLR# level.
• Use Oracle database 10g or 11g Enterprise Edition. Do not use the embedded light database.
• The SOA database must be configured to use case insensitive logon. This is done automatically by the PROCESSIT Installer.

You can set the system to case insensitive logon manually by running this SQL command as SYSTEM: ALTER SYSTEM SET SEC_CASE_SENSITIVE_LOGON=FALSE

PROCESSIT WebLogic User Interface Server

• Oracle WebLogic version 10.3.2.
• d4 domain.
• Oracle ADF version 11.1.1.2.0 for d4 domain.

Standard PROCESSIT installation

Installation wizard

PROCESSIT is installed using the PROCESSIT Installation Wizard. The wizard guides you through the steps required and provides links directly to the files that require modification.

When you run the installation, follow all Installation Wizard instructions. When you have completed the instructions, click Next to continue to the next page. When the installation procedure is done, the installation wizard notifies that the installation is complete.

Locate directories

Locate the following directory and instance information:

All reference instances in brackets [...] in this document correspond to the located values. These values must be defined in the PROCESSIT properties file.

If you want to encrypt a BPEL data source, refer to security settings.

Create an installation folder and unpack files

1. Create an installation folder for PROCESSIT on the installation computer.
2. Unpack the PROCESSIT software package to the created folder.

The software is packaged as a .zip archive and can be extracted with many archive extraction applications, including unzip, 7zip and winrar. The extracted installation folder is referred to as [inst.root] in this document.

If you run the installation from a linux machine, the command to extract the file is unzip <filename>.

Edit the properties file

The installation reads from the properties file [inst.root]/config/processit.properties

1. Navigate to [inst.root]/config/
2. Edit the file processit.properties
3. Edit the properties in this file to reflect your environment settings. There are explanations for each property as comments above the respective property.

In the properties file, some paths are relative to the installation machine, and some paths are relative to the server where PROCESSIT is being installed. These options are clearly marked in the configuration file as either Relative to INSTALLATION PC or Relative to SOA SERVER. An example of a possible path for the OC4J application server: [as.root] relative to the server: /oracle/as

Please double-check your entries. The entries in the properties file are used by the installation wizard throughout the installation process.

If you want to encrypt the properties file after PROCESSIT is installed, refer to security settings.

Encrypting the properties file is recommended only after the installation is complete.

Copying Configuration Parameter Settings

You can export configuration parameters from one environment and then import them to another. For instance, you can copy the configuration from a test environment to a production environment. The procedure is described in Copy Configuration Parameters.

Installation Wizard Procedure

Welcome to the PROCESSIT installation

Follow the instructions in this wizard to install PROCESSIT.

Hosts files

The hosts file of the installation PC, the SOA Suite Server, the WebLogic Server, and the Oracle E-Business Suite server must have correct entries for the three servers. Without these entries, the servers are not able to communicate. Make sure the hosts files contain valid entries for the following machines:

You may have to log in as root to edit the files.

• SOA Suite server: ${bpel.server}
• Weblogic server: ${weblogic.adminServerHostName}
• E-Business Suite server: ${ebs.server.hostname}
• INVOICES server: ${invoices.server.hostname}

Installation PC

UNIX

Edit the file /etc/hosts on your local machine.

Windows

Edit the file c:/windows/system32/drivers/etc/hosts on your local machine.

SOA Suite server

Edit the file /etc/hosts on the SOA Suite server.

WebLogic server

Edit the file /etc/hosts on the Weblogic Suite server.

Oracle E-Business Suite server

Edit the file /etc/hosts on the EBSDB server.

TNS settings

Edit the file ${db.root}/network/admin/tnsnames.ora on the database server. Copy and paste the TNS entry below into the file. Change the service name, host and port to match the Oracle E-Business Suite machine.

EBSDB =
  (DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = ${ebs.server.hostname})(PORT = ${db.jdbc.ebs.port}))
    )
      (CONNECT_DATA =
       (SERVICE_NAME = ${db.jdbc.ebsapps.servicename})
      )
 )


This edit may require DBA access if the installer does not have access to the DB server for the PROCESSIT database.

WebLogic Open Files Limit

The limit on the number of open files on the WebLogic Server must be increased. Edit the file /etc/security/limits.conf on the Weblogic Suite server. Add the following lines, or modify them if they already exist:

* soft nofile 32767
hard nofile 32767

Repository folders

Create the following directories on the SOA Suite server:

• ${repository.folder.target.config}
• ${repository.folder.target.contracts}
• ${repository.folder.target.schemas}

Apache configuration

Edit the file ${as.root}/Apache/Apache/conf/httpd.conf on the SOA Suite server. Add these lines to the end of the file:

# Include the Oracle configuration file for custom settings
include "${repository.root}/config/apache.conf"

BPEL admin tasks

Create the required BPEL domains manually via BPEL administrator.

1. Open the BPEL administrator in a browser: http://${bpel.server}:${bpel.port}/BPELAdmin
2. Login to the BPEL admin console with the user oc4jadmin.
3. Navigate to the BPEL domains tab. (upper right-hand corner).
4. Select Create New BPEL Domain from the task list.
5. Create the domain core and the domain services.
6. Navigate to the Server Configuration tab.
7. Modify the URLs in these fields to point to ${bpel.server}:${bpel.port}.
   • clusterName
   • soapCallbackUrl
   • soapServerUrl

Database link

The database link connects to the Oracle E-Business Suite database with user ${db.jdbc.ebsapps.username}. It must be changed to reflect the ${db.jdbc.ebsapps.username} password.

1. Edit the file ${inst.root}/database/plugin/databaselink/db_link.sql on the installation machine.
2. Modify it to contain the code below. Specifically regarding connect to ${db.jdbc.ebsapps.username} identified by ${db.jdbc.ebsapps.password}.

declare
l_x varchar2(260) := 'EBSDB';
l_x2 varchar2(260) := 'EBSDB';
l_dummy_cnt pls_integer:=0;
begin
select count(1) into l_dummy_cnt from all_db_links where db_link=l_x;

if l_dummy_cnt =0 then
dbms_output.put_line('database link '||l_x||' not created, will create now.... ');
execute immediate 'create public database link '||l_x||' connect to ${db.jdbc.ebsapps.username} identified by ${db.jdbc.ebsapps.password} using '||''''||l_x2||'''';
else
dbms_output.put_line('database link '||l_x||' is created, will skip ... ');
end if;
end;
/

Oracle E-Business Suite adapter

1. Modify log file location to a temporary folder on the Oracle SOA server.
2. Modify all database properties to reflect your Oracle E-Business Suite database name.

Modifaction Example

<?xml version="1.0" encoding="UTF-8"?>
<properties>
<property Name="log.file" Value="/usr/tmp/EBSAdapter.log"/>
<property Name="database.drv" Value="${db.jdbc.driver}"/>
<property Name="database.url" Value="${db.jdbc.ebsapps.url}"/>
<property Name="database.usr" Value="${db.jdbc.ebsapps.username}"/>
<property Name="database.pwd" Value="${db.jdbc.ebsapps.password}"/>
<property Name="cache.InactivityTimeout" Value="600"/>
<property Name="cache.AbandonedTimeout" Value="900"/>
<property Name="cache.PropertyCheckInterval" Value="900"/>
</properties>


Task reminders

In order to enable human task reminders you must edit the reminder table data sql script located at ${inst.root}/database/seeded_data/d4_reminder_levels_data.sql to reflect your preferences. For example:

DECLARE
BEGIN
--
-- Upload table D4_REMINDER_LEVELS
--
d4_db.upload_set_table(p_table_name => 'D4_REMINDER_LEVELS' ,p_schema_name =>'d4', p_delete_all_rows => TRUE,p_fail_on_missing_table => FALSE,p_unique_violation_ok=>TRUE,p_column_list => 'ORG_ID, REMINDER_GROUP, REMINDER_LEVEL, DAYS, ESCALATION, NEXT_USER_SRC' );
d4_db.upload_data('204,''ACC'',1, 1, ''N'', ''H''');
d4_db.upload_data('204,''ACC'',3, 2, ''Y'', ''H''');
d4_db.upload_data('204,''ACC'',5, 3, ''Y'', ''S''');
d4_db.upload_data('204,''APP'',1, 3, ''N'', ''H''');
d4_db.upload_data('204,''APP'',2, 1, ''Y'', ''H''');
d4_db.upload_data('204,''MPO'',1, 3, ''N'', ''H''');
d4_db.upload_data('204,''MPO'',2, 1, ''Y'', ''H''');
d4_db.upload_data('204,''STD'',1, 3, ''N'', ''H''');
d4_db.upload_data('204,''STD'',2, 2, ''Y'', ''H''');
d4_db.upload_data('204,''HLD'',1, 3, ''N'', ''H''');
d4_db.upload_data('204,''HLD'',2, 2, ''Y'', ''H''');
d4_db.upload_commit_data;
END;
/


WebLogic JVM Memory Settings

The JVM Heap Size on the WebLogic Server should be increased.

Edit the file ${weblogic.server.d4DomainDir}/bin/setDomainEnv.sh on the Weblogic Suite server. Find these lines:

# For additional information, refer to "Managing Server Startup and Shutdown for Oracle WebLogic Server"
# (http://download.oracle.com/docs/cd/E12839_01/web.1111/e13708/overview.htm).
# *************************************************************************


Add these lines below the lines located above:

• For 32-bit JVM:
  USER_MEM_ARGS="-Xms1024m -Xmx1536m -XX:PermSize=256m -XX:MaxPermSize=512m -XX:+CMSClassUnloadingEnabled -XX:+CMSPermGenSweepingEnabled"
export USER_MEM_ARGS
• For 64-bit JVM:
  USER_MEM_ARGS="-Xms1024m -Xmx3072m -XX:PermSize=256m -XX:MaxPermSize=768m -XX:+CMSClassUnloadingEnabled -XX:+CMSPermGenSweepingEnabled"
export USER_MEM_ARGS

SOA Suite JVM Memory Settings

The JVM Heap Size on the SOA Suite Server should be increased.

1. Edit the file ${as.root}/opmn/conf/opmn.xml on the SOA Suite server.
2. Find these lines:
   • <process-type id="oc4j_soa" module-id="OC4J" status="enabled">
   • <module-data>
   • <category id="start-parameters">
3. Edit the data id="java-options" line below it and set the following values:
4. For 32-bit JVM:
-XX:MaxPermSize=512M
-ms512M
-mx1536M
5. For 64-bit JVM:
-XX:MaxPermSize=768M
-ms1024M
-mx4096M

Restart WebLogic

Restart the WebLogic server.

1. Log in as oracle on the WebLogic server
2. Navigate to the ${weblogic.server.d4DomainDir}/bin directory
3. Stop WebLogic with the command ./StopWebLogic.sh
4. Start WebLogic with the command ./StartWebLogic.sh >~/logs/weblogic.log &

Restart SOA Suite

1. Log in as oracle on the SOA server
2. Stop the SOA Suite with the command: $ opmnctl stopall
3. Start the SOA Suite with the command: $ opmnctl startall
4. Check whether all processes are restarted with the command: $ opmnctl status
5. These three process-types must have status alive:
   • OC4J:${soa.instance_name}
   • OC4J:home
   • HTTP_Server

Weblogic database connections

The data sources listed below must be created in the WebLogic console.

D4_OEBS_APPS

• JNDI name: jdbc/D4_OEBS_APPS
• Database URL: ${db.jdbc.ebsapps.url}
• Database user: ${db.jdbc.ebsapps.username}
• Database password: ${db.jdbc.ebsapps.password}

Follow the following directions for each of the above connections to add.

1. Open the Weblogic console: http://${weblogic.adminServerHostName}:${weblogic.adminServerPort}/console
2. Log in to the Weblogic console with username ${weblogic.userId} and password ${weblogic.password}.
3. Click on Data Sources under the JDBC header on the home page.
5. Click Lock & Edit in the change center box.
6. Click New above the Data Sources table.
7. Fill in the JDBC Data Source Properties with the appropriate data source name and JNDI name from above. Make sure Database Driver is set to Oracle's Driver (Thin) for Instance connections;Versions:9.0.1,9.2.0,10,11.
8. Click Next.
9. Un-check Supports Global Transactions.
10. Click Next.
11. Supply the Connection Properties with the appropriate database name, hostname and port from the database URL.
12. Supply the database username
13. Click Next.
14. Click Test Configuration.
15. You receive a message that the ✔ Connection test succeeded
16. Click Next
17. Check the AdminServer checkbox in the Serves Table for Select targets.
18. Click Finish
19. Click on the name of the connection you just created to enter its settings page.
20. Navigate to the Connection Pool tab.
21. Set the Maximum Capacity to at least 100.
22. Click Save.
23. Click Activate Changes in the change center box.
24. You receive a message that All changed have been activated.

Repository verification

Verify that you can access the repository on the server by opening this link in a browser: http://${bpel.server}:${bpel.port}/repository/contracts/D4_CM_PROCESSIT_1.wsdl

The result should look like this:

<?xml version="1.0" encoding="UTF-8" ?>
- <!-- $Id: D4_CM_PROCESSIT_1.wsdl 7822 2012-02-15 18:55:35Z dmo $
-->
- <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:client="http://www.readsoft.com/D4/CM/D4_PROCESSIT/1" targetNamespace="http://www.readsoft.com/D4/CM/D4_PROCESSIT/1" name="D4_PROCESSIT_1">
- <!-- Imports
-->
- <types>
- <xs:schema>
<xs:import namespace="http://www.readsoft.com/D4/CM/D4_PROCESSIT/1" schemaLocation="../schemas/D4_CM_PROCESSIT_1.xsd" />
</xs:schema>
</types>
- <!-- Messages
-->
- <message name="runRequestMessage">
<part name="payload" element="client:runRequest" />
</message>
- <message name="runResponseMessage">
<part name="payload" element="client:runResponse" />
</message>
- <!-- PortType
-->
+ <portType name="D4_PROCESSIT_1">
- <operation name="run">
<input message="client:runRequestMessage" />
<output message="client:runResponseMessage" />
</operation>
</portType>
- <plnk:partnerLinkType name="D4_PROCESSIT_1_PL">
- <plnk:role name="D4_PROCESSIT_1_Role">
<plnk:portType name="client:D4_PROCESSIT_1" />
</plnk:role>
</plnk:partnerLinkType>
- <!-- Binding
-->
- <binding name="D4_PROCESSIT_1" type="client:D4_PROCESSIT_1">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
- <operation name="run">
<soap:operation soapAction="run" style="document" />
- <input>
<soap:body use="literal" />
</input>
- <output>
<soap:body use="literal" />
</output>
</operation>
</binding>
- <service name="D4_PROCESSIT_1">
- <port name="D4_PROCESSIT_1" binding="client:D4_PROCESSIT_1">
<soap:address location="http://processit:7777/orabpel/default/D4_PROCESSIT_1" />
</port>
</service>
</definitions>


Identity service plugin configuration

1. Edit the file ${as.root}/j2ee/${oc4j.instancename}/applib/Identity.xml on the SOA Suite server.
2. Change all properties to reflect your environment. Service URLs should already be correct.

E-Business Suite adapter configuration

1. Edit the file ${as.root}/j2ee/${oc4j.instancename}/applib/EBSAdapter.xml on the SOA Suite server.
2. Change the database configuration to point to the Oracle E-Business Suite database.

Configure the BPEL fault handler

1. Edit the file ${as.root}/j2ee/home/ProcessITFaultHandler.properties on the SOA Suite server.
2. Change faultMessageRecipient to the email of the person that should receive an email notification if PROCESSIT encounters a fault in a BPEL process. Usually, this is the system administrator.
3. Change from to the email that you want notification emails to appear to come from.
4. Further configuration options are described in the properties file.

Edit server.xml

1. Open the file ${as.root}/j2ee/${oc4j.instancename}/config/server.xml on the SOA Suite server.
2. Find this line: <shared-library name="oracle.bpel.common" version="10.1.3">
3. Insert these lines below the line located above:

<code-source path="${as.root}/j2ee/${oc4j.instancename}/applib/Identity.jar"/>
<code-source path="${as.root}/j2ee/${oc4j.instancename}/applib/FaultHandlerJar.jar"/>
<code-source path="${as.root}/j2ee/${oc4j.instancename}/applib/EBSAdapter.jar"/>


SOA Suite connection pools

Add these connection pools:

• D4_OEBS_APPS_POOL
• D4_DB_D4_POOL
• D4_DB_APPS_POOL

Edit the file ${as.root}/j2ee/${oc4j.instancename}/config/data-sources.xml on the SOA Suite server. Insert this following XML fragment after the last <connection-pool> element:

<connection-pool name="D4_OEBS_APPS_POOL">
<connection-factory
factory-class="oracle.jdbc.pool.OracleDataSource"
user="APPS"
password="${db.jdbc.ebsapps.password}"
url="${db.jdbc.ebsapps.url}"/>
</connection-pool>
<connection-pool name="D4_DB_D4_POOL">
<connection-factory
factory-class="oracle.jdbc.pool.OracleDataSource"
user="D4"
password="${db.jdbc.d4.password}"
url="${db.jdbc.url}"/>
</connection-pool>
<connection-pool name="D4_DB_APPS_POOL">
<connection-factory
factory-class="oracle.jdbc.pool.OracleDataSource"
user="APPS"
password="${db.jdbc.d4apps.password}"
url="${db.jdbc.d4apps.url}"/>
</connection-pool>


SOA Suite data sources

Add these data sources:

• D4_OEBS_APPS_DS
• D4_DB_D4_DS
• D4_DB_APPS_DS

Edit the file ${as.root}/j2ee/${oc4j.instancename}/config/data-sources.xml on the SOA Suite server. Insert the following XML fragment after the last <managed-data-source> element:

<managed-data-source connection-pool-name="D4_OEBS_APPS_POOL" jndi-name="jdbc/D4_OEBS_APPS_DS" name="D4_OEBS_APPS_DS"/>
<managed-data-source connection-pool-name="D4_DB_D4_POOL" jndi-name="jdbc/D4_DB_D4_DS" name="D4_DB_D4_DS"/>
<managed-data-source connection-pool-name="D4_DB_APPS_POOL" jndi-name="jdbc/D4_DB_APPS_DS" name="D4_DB_APPS_DS"/>


SOA Suite apps adapter

SOA Suite database adapters

Add these database adapters:

• D4_OEBS_APPS
• D4_DB_D4
• D4_DB_APPS

Edit the file ${as.root}/j2ee/${oc4j.instancename}/application-deployments/default/DbAdapter/oc4j-ra.xml on the SOA Suite server. Insert this XML fragment after the last <connector-factory> element:

<connector-factory location="eis/DB/D4_OEBS_APPS"
connector-name="Database Adapter">
<config-property name="xADataSourceName"
value="jdbc/D4_OEBS_APPS_DS"/>
<config-property name="dataSourceName" value=""/>
<config-property name="platformClassName"
value="oracle.toplink.platform.database.Oracle9Platform"/>
<config-property name="usesNativeSequencing" value="true"/>
<config-property name="sequencePreallocationSize"
value="50"/>
<config-property name="defaultNChar" value="false"/>
<config-property name="usesBatchWriting" value="true"/>
<connection-pooling use="none"/>
<security-config use="none"/>
<connectionfactory-interface>
javax.resource.cci.ConnectionFactory
</connectionfactory-interface>
</connector-factory>


<connector-factory location="eis/DB/D4_DB_D4"
connector-name="Database Adapter">
<config-property name="xADataSourceName"
value="jdbc/D4_DB_D4_DS"/>
<config-property name="dataSourceName" value=""/>
<config-property name="platformClassName"
value="oracle.toplink.platform.database.Oracle9Platform"/>
<config-property name="usesNativeSequencing" value="true"/>
<config-property name="sequencePreallocationSize"
value="50"/>
<config-property name="defaultNChar" value="false"/>
<config-property name="usesBatchWriting" value="true"/>
<config-property name="usesStreamsForBinding" value="true"/>
<config-property name="usesStringBinding" value="true"/>
<connection-pooling use="none"/>
<security-config use="none"/>
<connectionfactory-interface>
javax.resource.cci.ConnectionFactory
</connectionfactory-interface>
</connector-factory>


<connector-factory location="eis/DB/D4_DB_APPS"
connector-name="Database Adapter">
<config-property name="xADataSourceName"
value="jdbc/D4_DB_APPS_DS"/>
<config-property name="dataSourceName" value=""/>
<config-property name="platformClassName"
value="oracle.toplink.platform.database.Oracle9Platform"/>
<config-property name="usesNativeSequencing" value="true"/>
<config-property name="sequencePreallocationSize"
value="50"/>
<config-property name="defaultNChar" value="false"/>
<config-property name="usesBatchWriting" value="true"/>
<config-property name="usesStreamsForBinding" value="true"/>
<config-property name="usesStringBinding" value="true"/>
<connection-pooling use="none"/>
<security-config use="none"/>
<connectionfactory-interface>
javax.resource.cci.ConnectionFactory
</connectionfactory-interface>
</connector-factory>


Increase SOA Server Timeout Limit

1. Edit the file ${as.root}/j2ee/oc4j_soa/config/transaction-manager.xml on the SOA Suite server.
   Set the transaction-timeout to 7200.
2. Edit the file ${as.root}/j2ee/${oc4j.instancename}/application-deployments/orabpel/ejb_ob_engine/orion-ejb-jar.xml on the SOA Suite server.
   Set the transaction-timeout to 3600 for each instance of transaction-timeout.
3. Edit the file ${as.root}/bpel/domains/core/config/domain.xml on the SOA Suite server.
   Set the syncMaxWaitTime to 300 for each instance of transaction-timeout.
4. Edit the file ${as.root}/bpel/domains/default/config/domain.xml on the SOA Suite server.
   Set the syncMaxWaitTime to 300 for each instance of transaction-timeout.
5. Edit the file ${as.root}/bpel/domains/services/config/domain.xml on the SOA Suite server.
   Set the syncMaxWaitTime to 300 for each instance of transaction-timeout.

Enable Log4j Notifications

To enable Log4j notifications please follow these instructions:

1. Open the WebLogic console: http://${weblogic.adminServerHostName}:${weblogic.adminServerPort}/console
2. Click Servers under Environment
   
3. Click on Admin Server link.
   
4. Navigate to the Logging tab.
   
5. Scroll to the bottom of the page and expand the Advanced section.
   
6. Change the logging implementation from JDK to Log4J.
   
7. Click Save.
8. Depending on your Weblogic Console preferences, changes may need to be activated. If you see this in the top-left hand corner of the Console page, click Activate Changes.
9. Edit the file ${weblogic.server.d4DomainDir}/bin/setDomainEnv.sh on the Weblogic server.
10. Find this line: if [ "${LOG4J_CONFIG_FILE}" != "" ] ; then
11. Add this line above the line located above: LOG4J_CONFIG_FILE=${weblogic.server.d4DomainDir}/log4j.xml
12. Edit the file ${weblogic.server.d4DomainDir}/log4j.xml on the Weblogic server and change the parameters according to your requirements.

Weblogic database connections

The data sources listed below must be created in the WebLogic console if they don't exist already.

D4_DB_D4

• JNDI name: jdbc/D4_DB_D4
• Database URL: ${db.jdbc.url}
• Database user: ${db.jdbc.d4.username}
• Database password: ${db.jdbc.d4.password}

D4_OEBS_APPS

• JNDI name: jdbc/D4_OEBS_APPS
• Database URL: ${db.jdbc.ebsapps.url}
• Database user: ${db.jdbc.ebsapps.username}
• Database password: ${db.jdbc.ebsapps.password}

soadbDS

• JNDI name: jdbc/soadbDS
• Database URL: ${db.jdbc.url}
• Database user: ${db.jdbc.d4.username}
• Database password: ${db.jdbc.d4.password}

INVOICES_DB

• JNDI name: jdbc/INVOICES_DB
• Database URL: ${db.jdbc.invoices.url}
• Database user: ${db.jdbc.invoices.username}
• Database password: ${db.jdbc.invoices.password}

Follow these directions for each of the above connections:

1. Open the Weblogic console: http://${weblogic.adminServerHostName}:${weblogic.adminServerPort}/console
2. Log in to the Weblogic console with username: ${weblogic.userId} and password: ${weblogic.password}.
3. Click on the Data Sources link under JDBC header on the home page.
4. Click Lock & Edit in the change center box.
5. Click New above the Data Sources table.
6. Fill in the JDBC Data Source Properties with the appropriate data source name and JNDI name for the data connecting you are currently configuring.
   • For instance, for D4_DB_d4, data source name should be D4_DB_D4 and the JNDI Name should be jdbc/D4_DB_D4
7. Make sure Database Driver is set to Oracle's Driver (Thin) for Instance connections;Versions:9.0.1,9.2.0,10,11.
8. As standard, set Database Type to Oracle. For MS SQL Server version of INVOICES, make sure Database Type is set to MS SQL Server and Database Driver is set to Oracle's MS SQL Server Driver (Type 4) Versions: 7.0, 2000, 2005.
9. Click Next
10. Un-check Supports Global Transactions.
11. Click Next
12. Fill in the Connection Properties with the appropriate database name, hostname and port from the database URL for the database connection you are currently configuring.
13. Fill in the database username for the connection you are currently configuring.
14. For MS SQL Server version of INVOICES the Connection Properties should be:
    • Database Name: invoices
    • Host Name: readsoft.invoices
    • port: 1433
    • database User Name: sa
15. Click Next
16. Click Test Configuration
17. The should receive a message saying ✔ Connection test succeeded.
18. Click next
19. Check the AdminServer checkbox.
20. Click Finish
21. Click the name for the connection just created to enter the settings page for the connection.
22. Click on the Connection Pool tab.
23. Set the value for the Maximum Capacity field to at least 150.
24. For MS SQL Server version of INVOICES, the Connection Pool properties should be:
    • URL: jdbc:weblogic:sqlserver://readsoft.invoices:1433
    • Driver Class Name: weblogic.jdbc.sqlserver.SQLServerDriver
    • Properties:
      user=sa
      portNumber=1433
      databaseName=invoices
      serverName=readsoft.invoices
25. Click Save.
26. Click Activate Changes in the change center box.
27. You receive a message that All changed have been activated.
28. Repeat the steps for all four data sources. When these steps have been successfully completed, the Summary of JDBC Data Sources page Data Sources table should show the added data sources.

Weblogic authentication provider

Modify the security realm for the WebLogic server.

1. Open the Weblogic console: http://${weblogic.adminServerHostName}:${weblogic.adminServerPort}/console
2. Navigate to security realms -> myrealm -> Providers.
3. Click New above the Authentication Providers table.
4. Put IdentityServiceAuthenticationProvider in the Name field.
5. Select IdentityServiceAuthenticator from the Type drop-down list.
6. Click OK
7. Click on the name of the IdentityServiceAuthenticationProvider you just created to edit its settings.
8. Make sure that the Control Flag drop-down list has SUFFICIENT selected
9. Click Save
10. Navigate back to the Providers page.
11. Repeat steps 7 to 9 for the DefaultAuthenticator.

Enable Email notifications

To enable notifications from BPEL being send as e-mails:

1. Edit the file ${as.root}/bpel/system/services/config/ns_emails.xml on the SOA Suite server.
2. Replace NONE with EMAIL for the NotificationMode parameter.
3. Replace the parameter values shown in bold with values appropriate to your environment. PROCESSIT does not support e-mail approval, so incoming server setup is not required.

<EmailAccounts xmlns="http://xmlns.oracle.com/ias/pcbpel/NotificationService"
EmailMimeCharset=" "
NotificationMode="NONE">
<EmailAccount>
<Name>Default</Name>
<GeneralSettings>
<FromName>Oracle BPM</FromName>
<FromAddress>accountId@yourdomain.com</FromAddress>
</GeneralSettings>
<OutgoingServerSettings>
<SMTPHost>yourdomain.com</SMTPHost>
<SMTPPort>25</SMTPPort>
</OutgoingServerSettings>
<IncomingServerSettings>
<Server>yourdomain.com</Server>
<Port>110</Port>
<Protocol>pop3</Protocol>
<UserName>accountId</UserName>
<Password ns0:encrypted="false" xmlns:ns0="http://xmlns.oracle.com/ias/pcbpel/NotificationService">password</Password>
<UseSSL>false</UseSSL>
<Folder>Inbox</Folder>
<PollingFrequency>1</PollingFrequency>
<PostReadOperation>
<MarkAsRead/>
</PostReadOperation>
</IncomingServerSettings>
</EmailAccount>
</EmailAccounts>


1. Edit the file ${as.root}/bpel/system/services/config/wf_config.xml on the SOA Suite server.
2. Remove this XML element section: <worklistApplicationURL>http://soa.readsoft.local:7777/integration/worklistapp/TaskDetails?taskId=PC_HW_TASK_ID_TAG</worklistApplicationURL>

Readsoft Notification Service configuration

Optionally, complete these steps to enable consolidated email notifications.

1. Verify that the property file value for db.jdbc.url contains the correct database server url.
2. Verify that the property file value for db.jdbc.d4.username contains the correct database server d4 username.
3. Verify that the property file value for db.jdbc.d4.password contains the correct database server d4 user password.
4. Inspect the file ${as.root}/j2ee/${oc4j.instancename}/applib/ReadSoftNotificationService.xml on the SOA Suite server.
5. Modify log file location to a temporary folder on the Oracle SOA server.

Modification Example

<?xml version="1.0" encoding="UTF-8"?>
<properties>
<property Name="log.file" Value="/usr/tmp/ReadSoftNotificationService.log"/>
<property Name="database.drv" Value="${db.jdbc.driver}"/>
<property Name="database.url" Value="${db.jdbc.url}"/>
<property Name="database.usr" Value="${db.jdbc.d4.username}"/>
<property Name="database.pwd" Value="${db.jdbc.d4.password}"/>
<property Name="cache.InactivityTimeout" Value="600"/>
<property Name="cache.AbandonedTimeout" Value="900"/>
<property Name="debugFlag" Value="false"/>
</properties>

Verify smtp hostname

Verify that the property file value for smtp.hostname contains the smtp mail server host name.

This value should be the same as the Configuration Manager parameter value for Mail Server Host under the Mail Settings category

1. Open the file ${as.root}/j2ee/${oc4j.instancename}/config/server.xml on the SOA Suite server.
2. Find the line: <shared-library name="oracle.bpel.common" version="10.1.3">
3. Insert this line below the located line: <code-source path="${as.root}/j2ee/${oc4j.instancename}/applib/ReadSoftNotificationService.jar"/>

1. Open the file ${as.root}/bpel/system/services/config/pc.properties on the SOA Suite server.
2. Insert the following two lines into the file:
# Workflow Notification Email Service Fails Periodically with ORABPEL-10328 and Timeout waiting for client
oracle.tip.pc.services.notification.email.transportCacheDuration = 2000;

1. Open the file ${as.root}/bpel/system/services/config/ns_iaswconfig.xml on the SOA Suite server.
2. Find the line: <CustomNotificationService>
3. Insert this line between the Email tags: <Email>com.readsoft.processit.notification.ReadSoftNotificationService<Email>

To receive consolidated email notifications from the Readsoft Notification Service:

1. Open the PROCESSIT Configuration Manager.
2. Go to the Mail Settings category.
3. Find the parameter Consolidated Email Schedule.
4. Enter a schedule by site, organization or user in the form FREQ=[DAILY|WEEKLY|IMMEDIATE]; {BYDAY=[MON,TUE,WED,THU,FRI];} BYHOUR=[0-23]; {BYMINUTE=[0-59]};
5. To receive consolidated notifications each day at 7:00am: FREQ=DAILY; BYHOUR=7;
6. To receive consolidated notifications each day at 5:30pm: FREQ=DAILY; BYHOUR=17; BYMINUTE=30
7. To receive consolidated notifications each Tuesday and Thursday at 6:00am: FREQ=WEEKLY; BYDAY=TUE,THU; BYHOUR=6;

SOA Suite Enterprise Manager Autostart

By default OC4J Enterprise Manager does not start automatically. To ensure that Enterprise Manager starts with SOA Suite:

Home Instance

1. Open the file ${as.root}/j2ee/home/config/server.xml on the SOA Suite server.
2. Find this line: <application name="ascontrol" path="../../home/applications/ascontrol.ear" parent="system" start="false"/gt;
3. Change start="false" to start="true"
4. Save the file.
5. Open the file ${as.root}/j2ee/home/config/default-web-site.xml on the SOA Suite server.
6. Find this line: <web-app application="ascontrol" name="ascontrol" load-on-startup="false" root="/em" ohs-routing="false"/gt;
7. Change load-on-startup="false" to load-on-startup="true"
8. Change ohs-routing="false" to ohs-routing="true"
9. Save the file.

${oc4j.instancename} Instance

1. Open the file ${as.root}/j2ee/${oc4j.instancename}/config/server.xml on the SOA Suite server.
2. Find this line: <application name="ascontrol" path="../../home/applications/ascontrol.ear" parent="system" start="false"/gt;
3. Change start="false" to start="true"
4. Save the file.
5. Open the file ${as.root}/j2ee/${oc4j.instancename}/config/default-web-site.xml on the SOA Suite server.
6. Find this line: <web-app application="ascontrol" name="ascontrol" load-on-startup="false" root="/em" ohs-routing="false"/gt;
7. Change load-on-startup="false" to load-on-startup="true"
8. Change ohs-routing="false" to ohs-routing="true"
9. Save the file.

SOA Suite Log Rotation Settings

The log files the SOA Suite Server should be set to rotate to prevent log files from filling the hard drive of the server.

1. Edit the file ${as.root}/opmn/conf/opmn.xml on the SOA Suite server.
3. Find these lines:
   • <process-type id="oc4j_soa" module-id="OC4J" status="enabled">
   • <module-data>
   • <category id="start-parameters">
4. Edit the data id="java-options" line below the located lines. Add the following values: -Dstdstream.rotatetime=23:59
-Dstdstream.filenumber=30
5. Add the following line below the line you have just edited: <data id="oc4j-options" value="-out $ORACLE_HOME/opmn/logs/default_group~oc4j_soa~default_group.log -err $ORACLE_HOME/opmn/logs/default_group~oc4j_soa~default_group.log"/>

Restart WebLogic

Restart the WebLogic server.

1. Log in as oracle on the WebLogic server
2. Navigate to the ${weblogic.server.d4DomainDir}/bin directory
3. Stop WebLogic with the command ./StopWebLogic.sh
4. Start WebLogic with the command ./StartWebLogic.sh >~/logs/weblogic.log &

Restart SOA Suite

1. Log in as oracle on the SOA server
2. Stop the SOA Suite with the command: $ opmnctl stopall
3. Start the SOA Suite with the command: $ opmnctl startall
4. Check whether all processes are restarted with the command: $ opmnctl status
5. These three process-types must have status alive:
   • OC4J:${soa.instance_name}
   • OC4J:home
   • HTTP_Server

Installation Complete

The PROCESSIT installation process is complete.

Click here to launch the PROCESSIT Console: http://${weblogic.adminServerHostName}:${weblogic.adminServerPort}/processit/faces/Console