PROCESSIT 7.4 R1
For Oracle Fusion Middleware 11g

PROCESSIT Installation

©2025 Copyright ReadSoft AG (publ). All rights reserved. The contents of this document are subject to change without notice. ReadSoft is a registered trademark of ReadSoft AB. Other product and company names herein may be the trademarks or registered trademarks of their respective owners.
Questions or comments about this document may be emailed to documentation@readsoft.com.

ReadSoft AB (Head office) | Södra Kyrkogatan 4 | SE-252 23 Helsingborg | Sweden | Phone: +46 42 490 21 00 | Fax: +46 42 490 21 20
ReadSoft AG | Falkstrasse 5 | 60487 Frankfurt | Germany | Phone: +49 69 1539402-0 | Fax: +49 69 1539402-13
info@readsoft.com | www.readsoft.com

IntroductionPROCESSIT Architecture OverviewPrerequisitesInstallation computerINVOICES scanningOracle E-Business Suite R12PROCESSIT SOA serverPROCESSIT WebLogic User Interface ServerStandard PROCESSIT installationInstallation wizardLocate directoriesCreate an installation folder and unpack filesEdit the properties fileCopying Configuration Parameter SettingsInstallation Wizard ProcedureWelcome to the PROCESSIT installationHosts filesInstallation PCSOA Suite serverWebLogic serverOracle E-Business Suite serverTNS settingsWebLogic Open Files LimitOracle Enterprise Manager Fusion Middleware Control Partition tasksOracle Enterprise Manager Fusion Middleware Control Configuration tasksDatabase linkTask remindersWebLogic JVM Memory SettingsDatabase connectionsD4_OEBS_APPSDatabase connectionsD4_DB_D4D4_DB_APPSINVOICES_DBIdentity service plugin configurationConfigure the BPEL fault handlerOracleAppsAdapter Outgoing Connection PoolsD4_OEBS_APPSDbAdapter Outgoing Connection PoolsD4_DB_APPSD4_DB_D4D4_OEBS_APPSIncrease SOA Server Timeout LimitEnable Log4j NotificationsWeblogic authentication providerEnable Email notifications

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:

Instance information
DirectoryRelative toInstallation guide reference
SOA Suite databaseDatabase server[db.root]
SOA Suite installation rootSOA server[as.root]
Repository rootSOA server[repository.root]
WebLogic D4 domain rootWebLogic server[domain.root]
SOA Suite instanceSet during SOA installation (usually oc4j_soa)[soa.instance_name]
Installation directoryInstallation PC[inst.root]

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

Oracle Enterprise Manager Fusion Middleware Control Partition tasks

Create the required SOA partitions manually via Oracle Enterprise Manager Fusion Middleware Control

  1. Open the Oracle Enterprise Manager Fusion Middleware Control in a browser: http://${weblogic.adminServerHostName}:${weblogic.adminServerPort}/em
  2. Login to the Oracle Enterprise Manager Fusion Middleware Control with the user weblogic.
  3. Navigate to the SOA section under deployments.
  4. Click on the soa-infra link under the SOA section.
  5. Click the SOA Infrastructure link (upper left hand corner)
  6. Select Manage Partitions from the task list.
  7. Using the Create button, create two additional SOA Partitions core and services.

Oracle Enterprise Manager Fusion Middleware Control Configuration tasks

Set Configuration settings for Oracle Enterprise Manager Fusion Middleware Control

  1. Open the Oracle Enterprise Manager Fusion Middleware Control in a browser: http://${weblogic.adminServerHostName}:${weblogic.adminServerPort}/em
  2. Login to the Oracle Enterprise Manager Fusion Middleware Control with the user weblogic.
  3. Navigate to the SOA section under deployments.
  4. Click on the soa-infra link under the SOA section.
  5. Click the SOA Infrastructure link (upper left hand corner)
  6. Select SOA Administration, Common Properties from the task list.
  7. Verify Capture Composite Instance Stateis checked.

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

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 64-bit JVM:
    USER_MEM_ARGS="-Xms1024m -Xmx3072m -XX:PermSize=256m -XX:MaxPermSize=768m -XX:+CMSClassUnloadingEnabled -XX:+CMSPermGenSweepingEnabled"
    export USER_MEM_ARGS

Database connections

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

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 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 Services header on the home page.
  4. Click Lock & Edit in the change center box.
  5. Click New, Generic Data Source 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 and later.
  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, processit_cluster, and soa_cluster checkboxs.
  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.

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_DB_APPS

  • JNDI name: jdbc/D4_DB_APPS
  • Database URL: ${db.jdbc.d4apps.url}
  • Database user: ${db.jdbc.d4apps.username}
  • Database password: ${db.jdbc.d4apps.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 Services header on the home page.
  4. Click Lock & Edit in the change center box.
  5. Click New, Generic Data Source 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 and later.
  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, processit_cluster, and soa_cluster checkboxs.
  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.

Identity service plugin configuration

  1. Edit the file ${weblogic.server.d4DomainDir}/lib/Identity.xml on the Weblogic server.
  2. Change all properties to reflect your environment. Service URLs should already be correct.
  3. Copy the file ${weblogic.server.d4DomainDir}/lib/Identity.xml to the Domain lib directory for each managed server.
  4. Copy the file ${weblogic.server.d4DomainDir}/IdentityServicePlugin.properties to the Domain directory for each managed server.

Configure the BPEL fault handler

  1. Edit the file ${weblogic.server.d4DomainDir}/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.

OracleAppsAdapter Outgoing Connection Pools

The Outbound Connection Pools listed below must be created in the WebLogic console if they don't exist already.

D4_OEBS_APPS

  • JNDI name: eis/Apps/D4_OEBS_APPS
  • Datasource Name: jdbc/D4_OEBS_APPS

Follow these directions to configure the above connection:

  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 Deployments link under Your Deployed Resources on the home page.
  4. Click on the OracleAppsAdapter under the list of Deployments. You may have to click Next several times to find it in the list, or customize the table to increase the number of rows displayed per page.
  5. Click Configuration followed by Outbound Connection Pools.
  6. Click Lock & Edit in the change center box.
  7. Click New above the Outbound Connection Pool Configuration table.
  8. Select the javax.resource.cci.ConnectionFactory and click next.
  9. Add the JNDI Name listed above and click Finish.
    • For instance, for D4_OEBS_APPS, the JNDI name should be eis/Apps/D4_OEBS_APPS
  10. Click the name for the connection just created to enter the settings page for the connection.
  11. Within the Properties Tab, enter the dataSourceName as shown above.
    • For instance, for D4_OEBS_APPS, the dataSourceName should be jdbc/D4_OEBS_APPS
    • Hit enter after entering the text.
  12. Make sure the xADataSourceName property Value is empty.
  13. Click Save.
  14. The first time you create a Connection Pool you will receive a message that you have made changes that need to be stored in a new deployment plan.
    • Modify the suggested path to include a subdirectory called plan and another that is the name of the adapter you are configuring. These directories will need to exist on the server.
    • For instance, while modifying the OracleAppsAdapter, the path would be /oracle/middleware/Oracle_SOA1/soa/connectors/plan/OracleAppsAdapter/Plan.xml.
    • Click save and you should receive a message that the new Deployment plan was successfully created.
  15. If this is not the first connection pool you have created, you should receive a message that the Deployment plan has been successfully updated.
  16. click Activate Changes
  17. When these steps have been successfully completed, the Outbound Connection Pools page Groups and Instances table should show the added connection pools.

Update the deployment plan on OracleAppsAdapter:

  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 Deployments link under Your Deployed Resources on the home page.
  4. Click Lock & Edit in the change center box.
  5. Place a checkmark in front off the OracleAppsAdapter under the list of Deployments. You may have to click Next several times to find it in the list, or customize the table to increase the number of rows displayed per page.
  6. Click Update at the top of the list of deployments.
  7. Select Update this application in place with new deployment plan changes. (A deployment plan must be specified for this option)
  8. Verify the Deployment plan path is the matches what you just created, or change the path to select it.
    • For instance, the path for the OracleAppsAdapter is listed as /oracle/middleware/Oracle_SOA1/soa/connectors/plan/OracleAppsAdapter/Plan.xml
  9. Click Next and review your settings.
  10. Click Finish
  11. Click Activate Changes

DbAdapter Outgoing Connection Pools

The Outbound Connection Pools listed below must be created in the WebLogic console if they don't exist already.

D4_DB_APPS

  • JNDI name: eis/DB/D4_DB_APPS
  • Datasource Name: jdbc/D4_DB_APPS

D4_DB_D4

  • JNDI name: eis/DB/D4_DB_D4
  • Datasource Name: jdbc/D4_DB_D4

D4_OEBS_APPS

  • JNDI name: eis/DB/D4_OEBS_APPS
  • Datasource Name: jdbc/D4_OEBS_APPS

Follow these directions to configure 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 Deployments link under Your Deployed Resources on the home page.
  4. Click on the DbAdapter under the list of Deployments. You may have to click Next several times to find it in the list, or customize the table to increase the number of rows displayed per page.
  5. Click Configuration followed by Outbound Connection Pools.
  6. Click Lock & Edit in the change center box.
  7. Click New above the Outbound Connection Pool Configuration table.
  8. Select the javax.resource.cci.ConnectionFactory and click next.
  9. Add the JNDI Name listed above and click Finish.
    • For instance, for D4_DB_APPS, the JNDI name should be eis/DB/D4_DB_APPS
  10. Click the name for the connection just created to enter the settings page for the connection.
  11. Within the Properties Tab, enter the dataSourceName as shown above.
    • For instance, for D4_DB_APPS, the dataSourceName should be jdbc/D4_DB_APPS
    • Hit enter after entering the text.
  12. Make sure the xADataSourceName property Value is empty.
  13. Click Save.
  14. The first time you create a Connection Pool you will receive a message that you have made changes that need to be stored in a new deployment plan.
    • Modify the suggested path to include a subdirectory called plan and another that is the name of the adapter you are configuring. These directories will need to exist on the server.
    • For instance, while modifying the DbAdapter, the path would be /oracle/middleware/Oracle_SOA1/soa/connectors/plan/DbAdapter/Plan.xml.
    • Click save and you should receive a message that the new Deployment plan was successfully created.
  15. If this is not the first connection pool you have created, you should receive a message that the Deployment plan has been successfully updated.
  16. click Activate Changes
  17. When these steps have been successfully completed, the Outbound Connection Pools page Groups and Instances table should show the added connection pools.

Once all connection pools have been added, Update the deployment plan on DbAdapter:

  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 Deployments link under Your Deployed Resources on the home page.
  4. Click Lock & Edit in the change center box.
  5. Place a checkmark in front off the DbAdapter under the list of Deployments. You may have to click Next several times to find it in the list, or customize the table to increase the number of rows displayed per page.
  6. Click Update at the top of the list of deployments.
  7. Select Update this application in place with new deployment plan changes. (A deployment plan must be specified for this option)
  8. Verify the Deployment plan path is the matches what you just created, or change the path to select it.
    • For instance, the path for the DbAdapter is listed as /oracle/middleware/Oracle_SOA1/soa/connectors/plan/DbAdapter/Plan.xml
  9. Click Next and review your settings.
  10. Click Finish
  11. Click Activate Changes

Increase SOA Server Timeout Limit

Follow these directions to configure the Timeout:

  1. Open the Oracle Enterprise Manager Fusion Middleware Control in a browser: http://${weblogic.adminServerHostName}:${weblogic.adminServerPort}/em
  2. Login to the Oracle Enterprise Manager Fusion Middleware Control with the user weblogic.
  3. Navigate to the SOA section under deployments.
  4. Click on the soa-infra link under the SOA section.
  5. Click the SOA Infrastructure link (upper left hand corner)
  6. Select Soa Administration, BPEL Properties from the task list.
  7. Click the More BPEL Configuration Properties... link
  8. Under the Application Defined MBeans: BPELConfig:bpel attributes, change the value for SyncMaxWaitTime from 45 to 300

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
    image
  3. Click on Admin Server link.
    image
  4. Navigate to the Logging tab.
    image
  5. Scroll to the bottom of the page and expand the Advanced section.
    image
  6. Change the logging implementation from JDK to Log4J.
    image
  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.
  13. Repeat steps 3-9 for each managed server in the Processit_Cluster.
  14. Copy the log4j.xml file edited in step 12 to the Domain Directory for each managed server.

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:

Configure Email Driver Properties

  1. Open the Oracle Enterprise Manager Fusion Middleware Control in a browser: http://${weblogic.adminServerHostName}:${weblogic.adminServerPort}/em
  2. Login to the Oracle Enterprise Manager Fusion Middleware Control with the user weblogic.
  3. Navigate to the User Messaging Service section under Fusion Middleware.
  4. Click on the usermessagingdriver-email link under the User Messaging Service section.
  5. Click the User Messaging Email Driver link (upper left hand corner)
  6. Select Email Driver Properties from the task list.
  7. Set values for the following outgoing Mail settings as appropriate for your environment.
    • OutgoingMailServer: mailserver.yourdomain.com
    • OutgoingMailServerPort: 25
    • OutgoingMailServerSecurity: None
    • OutgoingDefaultFromAddr: processit@yourdomain.com
  8. Click the Apply button.
  9. Replace the parameter values shown in italics with values appropriate to your environment. PROCESSIT does not support incoming e-mail approval, so incoming server setup is not currently required.

Enable Notification Mode

  1. Open the Oracle Enterprise Manager Fusion Middleware Control in a browser: http://${weblogic.adminServerHostName}:${weblogic.adminServerPort}/em
  2. Login to the Oracle Enterprise Manager Fusion Middleware Control with the user weblogic.
  3. Navigate to the SOA section under Deployments.
  4. Click on the soa-infra link under the SOA section.
  5. Click the SOA Infrastructure link (upper left hand corner)
  6. Select SOA Administration, Workflow Properties from the task list.
  7. Set the Notification Mode to Email
  8. Set values for the following Notification Service settings as appropriate for your environment.
    • Email : From Address processit@yourdomain.com
    • Email : Actionable Address: processit@yourdomain.com
    • Email : Reply To Address: no.reply@yourdomain.com

    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 /oracle/middleware/Oracle_SOA1/soa/modules/oracle.soa.ext_11.1.1/ReadSoftNotificationService.xml on the Weblogic server.
    5. Modify log file location to a temporary folder on the Weblogic 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

    Configure Notification Service

    1. Open the Oracle Enterprise Manager Fusion Middleware Control in a browser: http://${weblogic.adminServerHostName}:${weblogic.adminServerPort}/em
    2. Login to the Oracle Enterprise Manager Fusion Middleware Control with the user weblogic.
    3. Navigate to the SOA section under Deployments.
    4. Click on the soa-infra link under the SOA section.
    5. Click the SOA Infrastructure link (upper left hand corner)
    6. Select SOA Administration, Workflow Properties from the task list.
    7. Click the More Workflow Notification Configuration Properties...
    8. Under Application Defined MBeans: HWFMailerConfig:human-workflow, click the Operations tab
    9. Click the setCustomNSDriverPropertyValue and set the following property values
      • propertyName: Email
      • propertyValue: com.readsoft.processit.notification.ReadSoftNotificationService
    10. Click the Invoke button

    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;

    Copy Recurring Invoice Templates to Managed Servers

    When running in a clustered High Availability environment you must copy the Recurring Invoice Templates from the Admin Server to each of the Managed Servers.

    1. Log in as oracle on the first WebLogic server
    2. Navigate to the ${weblogic.server.d4DomainDir}/processit/templates/Invoice directory
    3. Copy the contents to the managed server domain location such that the directory structure resembles the Admin Server Structure. e.g. /u01/app/oracle/admin/d4/mserver/d4/processit/templates/Invoices
    4. Repeat steps above for each Managed Server.

    Copy Shared Libraries to Managed Servers

    When running in a clustered High Availability environment you must copy the Shared Libraries from the Admin Server to each of the Managed Servers.

    1. Log in as oracle on the first WebLogic server
    2. Navigate to the ${weblogic.server.d4DomainLibDir} directory
    3. Copy the contents to the managed server domain lib location such that the directory structure resembles the Admin Server Structure. e.g. /u01/app/oracle/admin/d4/mserver/d4/lib
    4. Repeat steps above for each Managed Server.

    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 SOA Managed Server with the command ./stopManagedWebLogic.sh soa_server1
    4. Stop PROCESSIT Managed Server with the command ./stopManagedWebLogic.sh processit_server1
    5. Stop Admin Server with the command ./StopWebLogic.sh
    6. Start Admin Server with the command nohup ./startWebLogic.sh > ~/logs/weblogic.log 2>&1 &
    7. Start PROCESSIT Managed Server with the command nohup ./startManagedWebLogic.sh processit_server1 > ~/logs/processit_ms.log 2>&1 &
    8. Start SOA Managed Server with the command nohup ./startManagedWebLogic.sh soa_server1 > ~/logs/soa_ms.log 2>&1 &

      9. Installation Complete

      The PROCESSIT installation process is complete.

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