Environment Transition

Environment Transition Preparation tasks Change INVOICES Configuration Re-Point the PROCESSIT Plug-in Required PROCESSIT changes Data source on BPEL server in SOA EBSAdapter.xml on BPEL Server in SOA Restart Oracle SOA Suite Update WebLogic JDBC Connection Pool Restart WebLogic Recreate the DBLINK Update the Oracle E-Business Suite Packages Cleanup PROCESSIT database script Cleanup the dehydration store

Environment Transition

This section describes how to ensure a smooth cutover when transitioning the ReadSoft PROCESSIT solution from one environment to another, for example from Test to Production environments.

ReadSoft customers who have licensed ReadSoft INVOICES for invoice data capture, and ReadSoft PROCESSIT for invoice process management must ensure that the proper configuration is in place to determine the SOA environment that the INVOICES application sends invoice images and data to, and the respective Oracle E-Business Suite environment that the PROCESSIT application is interfaced with.

This section covers the necessary changes to the INVOICES configuration to re-point it to a newly installed PROCESSIT environment, and also the changes required to reference the new PROCESSIT application to the appropriate Oracle E-Business Suite R12 environment.

Preparation tasks

All reference instances in brackets [...] in this section correspond to the location values described in this table. These values are defined in the PROCESSIT properties file, which must be edited during the re-pointing procedure.

Directory	Relative to	Installation guide reference
SOA Suite database	Database server	[db.root]
SOA Suite installation root	SOA server	[as.root]
Installation directory	Installation PC	[inst.root]

Change INVOICES Configuration

Re-Point the PROCESSIT Plug-in

Open the INVOICES MANAGER module
Select the menu Plugins.
Select Configure InvoiceIT.
The configuration dialogue opens. This facilitates re-pointing the INVOICES application to a new PROCESSIT environment.
These settings in the General tab must be changed to reflect the new environment:
- Oracle Service Name: Entry from your tnsnames.ora file in ORACLE_HOME, for example soadb. Note that this is not necessarily the database service name.
- Oracle Applications Username: User name for PROCESSIT Plugin User: APPS
- Oracle Application Password: Password for PROCESSIT Plugin User. The default password is APPS
- Oracle Schema Name: Schema created within the Oracle SOA suite database. The schema must be named XXIT3.
Click Test Database Connections to confirm that the connection details are correct.

For more details on configuring the PROCESSIT plugin, refer to PROCESSIT Plugin Guide.

Required PROCESSIT changes

Data source on BPEL server in SOA

Connect to the server hosting the Oracle SOA database as the user oracle.
Modify data-sources.xml with the details of the new Oracle E-Business Suite R12 environment. From the command line enter this command: vi [as.root]/j2ee/oc4j_soa/config/data-sources.xml

Update the xml tag for the connection pool D4_OEBS_APPS_POOL with the correct server name, port number, SID, username and password for the apps schema in the new Oracle E-Business Suite R12 environment:


		<connection-pool name="D4_OEBS_APPS_POOL">
		<connection-factory factory-class="oracle.jdbc.pool.OracleDataSource" user="APPS"
		password="<yourpassword>"
		url="jdbc:oracle:thin:@<your.servername.com>:<your port number>:<yoursid>"
		commit-record-table-name=""/>
		</connection-pool>

Save the changes and close the file.

EBSAdapter.xml on BPEL Server in SOA

Connect to the server hosting the SOA database as the user oracle.
Modify the file EBSAdapter.xml with the details of the new Oracle E-Business Suite R12 environment. From the command line enter this command: vi [as.root]/j2ee/oc4j_soa/applib/EBSAdapter.xml

Update xml tag with correct server name, port, SID, user name and password


		<?xml version="1.0" encoding="UTF-8"?>
		<properties>
		 <property Name="log.file" Value="/usr/tmp/EBSAdapter.log"/>
		<property Name="database.drv" Value="oracle.jdbc.driver.OracleDriver"/>
		<property Name="database.url" Value="jdbc:oracle:thin:@ <your.servername.com>:<your port number>:<yoursid>"/>
		<property Name="database.usr" Value="apps"/>
		<property Name="database.pwd" Value="<yourpassword>"/>
		<property Name="cache.InactivityTimeout" Value="600"/>
		<property Name="cache.AbandonedTimeout" Value="900"/>
		<property Name="cache.PropertyCheckInterval" Value="900"/>
		</properties>

Save the changes and close the file.

Restart Oracle SOA Suite

Connect to the server hosting the SOA Suite Software as user oracle
In the command line enter: sudo service soa stop
Ignore the errors
When SOA is stopped, enter the command: sudo service soa start

Update WebLogic JDBC Connection Pool

Log in to the WebLogic server administration console: http://<Weblogicserver>:7001/console/login/LoginForm.jsp
Use username weblogic and password weblogic1 to log in.
Click on the Data Sources link
Click the name D4_OEBS_APPS.
Open the Connection Pool tab.
Edit the URL with server name, port and SID for the Oracle E-Business Suite database.
Default server name is readsoft.servers.ebs which works if the WLS hosts file has a readsoft.servers.ebs entry pointing to Oracle E-Business Suite.
In the Properties field, enter the name of the Oracle E-Business Suite database user. This must be apps (or xxd4_apps if you know that this is being used in the environment) and it should be entered in the following format user=apps.
Enter the password for the Oracle E-Business Suite database user apps.
Click Save.
Log out of the WebLogic console.

Restart WebLogic

Connect to the server hosting the WebLogic server as the user oracle.
sudo service weblogic stop
Wait 2-3 minutes
sudo service weblogig start
To confirm that WebLogic is running, you can look in weblogic.log for the status RUNNING or navigate to the WebLogic console via the url http://{PROCESSIT SERVER}:7001/console/login/LoginForm.jsp.

Recreate the DBLINK

The file TNSNAMES.ORA must be modified to include the connection details for the new Oracle E-Business Suite R12 environment.

Connect to the server hosting the Oracle SOA database as the user oracle.
From the command line enter the following command: vi [db.root]/network/admin/tnsnames.ora
Create or modify the alias called EBSDB in the tnsnames.ora file. As an example, it should look like below. The host, port, and service_name must be changed to reflect the Oracle E-Business Suite R12 environment to be pointed to:
```
	EBSDB  =
	  (DESCRIPTION =
		(ADDRESS = (PROTOCOL = TCP)(HOST = <your.servername.com>)(PORT = <yourdatabaseport>))
		(CONNECT_DATA =
		  (SERVER = DEDICATED)
		  (SERVICE_NAME = <yourServiceName>)
	   )
	)
					
```
To create or replace the database link between the PROCESSIT database and the Oracle E-Business Suite database:
Connect to the PROCESSIT database as the user D4 using SQLPlus.

At the SQL> prompt run these three commands:


	DROP PUBLIC DATABASE LINK ebsdb;
	CREATE PUBLIC DATABASE LINK ebsdb
	CONNECT TO apps IDENTIFIED BY <yourpassword>
	USING 'ebsdb';
	EXIT;

Update the Oracle E-Business Suite Packages

The entries in the properties file are used by the installation wizard throughout the installation process.

Configure the file [inst.root]/config/processit.properties file with the properties for the new Oracle E-Business Suite.
Edit the properties in this file to reflect your environment settings. There are explanations for each property as comments above the respective property.
Launch the PROCESSIT EBS Components Installer, using install_processit_ebs_components.sh.
Click Install all.
Restart WebLogic and SOA Suite.

Cleanup PROCESSIT database script

This script should be run to clean out old data before you begin processing invoices against the new Oracle E-Business Suite.

Log in to the PROCESSIT database as the D4 user with a tool such as SQL*Plus, SQLDeveloper, TOAD, or equivalent to execute the following script:


TRUNCATE TABLE D4_INVOICE_LINES_PROJECTS;
	TRUNCATE TABLE d4_invoice_lines;
	TRUNCATE TABLE d4_invoice_lines_match_tmp;
	DELETE d4_invoices;
	TRUNCATE TABLE d4_log;
	TRUNCATE TABLE d4_archive;
	TRUNCATE TABLE D4_DOC_LINES_EVENTS;
	TRUNCATE TABLE D4_DOC_PROCESS_ATTRIBUTES;
	TRUNCATE TABLE D4_DOC_PROCESS_STATUSES;
	TRUNCATE TABLE D4_DOC_PROCESS_TASKS;
	TRUNCATE TABLE D4_DOC_PROCESSES;
	TRUNCATE TABLE PS_TXN;
	TRUNCATE TABLE d4_aa_report_job;
	TRUNCATE TABLE d4_aa_report_job_task;
	TRUNCATE TABLE d4_aa_report_stats;
	TRUNCATE TABLE d4_archive_tag_values;
	TRUNCATE TABLE d4_attachments;
	TRUNCATE TABLE d4_audit_recon_daily;
	TRUNCATE TABLE d4_audit_recon_event;
	TRUNCATE TABLE d4_audit_recon_monthly;
	TRUNCATE TABLE d4_audit_recon_tracking;
	TRUNCATE TABLE d4_descriptive_flex_fields;
	TRUNCATE TABLE d4_doc_change_history;
	TRUNCATE TABLE d4_invoice_lines_temp;
	TRUNCATE TABLE d4_kpi_monthly;
	TRUNCATE TABLE D4_KPI_SUPPLIERS_MONTHLY;
	TRUNCATE TABLE d4_kpi_users_monthly;
	TRUNCATE TABLE d4_po_message;
	TRUNCATE TABLE d4_rns_log;
	TRUNCATE TABLE d4_rns_queue;
	TRUNCATE TABLE d4_search;
	TRUNCATE TABLE d4_user_rule_history;
	TRUNCATE TABLE d4_console_notification;
	TRUNCATE TABLE d4_hold_handled;
	ALTER TABLE D4_INVOICE_LINES_MATCH_TMP DEALLOCATE unused;
	ALTER TABLE D4_INVOICE_LINES_PROJECTS DEALLOCATE unused;
	ALTER TABLE d4_invoice_lines DEALLOCATE unused;
	ALTER TABLE d4_invoices DEALLOCATE unused;
	ALTER TABLE d4_log DEALLOCATE unused;
	ALTER TABLE d4_archive DEALLOCATE unused;
	ALTER TABLE D4_DOC_LINES_EVENTS DEALLOCATE unused;
	ALTER TABLE D4_DOC_PROCESS_ATTRIBUTES DEALLOCATE unused;
	ALTER TABLE D4_DOC_PROCESS_STATUSES DEALLOCATE unused;
	ALTER TABLE D4_DOC_PROCESS_TASKS DEALLOCATE unused;
	ALTER TABLE D4_DOC_PROCESSES DEALLOCATE unused;
	ALTER TABLE PS_TXN DEALLOCATE UNUSED;
	ALTER TABLE D4_AA_REPORT_JOB DEALLOCATE UNUSED;
	ALTER TABLE D4_AA_REPORT_JOB_TASK DEALLOCATE UNUSED;
	ALTER TABLE D4_AA_REPORT_STATS DEALLOCATE UNUSED;
	ALTER TABLE D4_ARCHIVE_TAG_VALUES DEALLOCATE UNUSED;
	ALTER TABLE D4_ATTACHMENTS DEALLOCATE UNUSED;
	ALTER TABLE D4_AUDIT_RECON_DAILY DEALLOCATE UNUSED;
	ALTER TABLE D4_AUDIT_RECON_EVENT DEALLOCATE UNUSED;
	ALTER TABLE D4_AUDIT_RECON_MONTHLY DEALLOCATE UNUSED;
	ALTER TABLE D4_AUDIT_RECON_TRACKING DEALLOCATE UNUSED;
	ALTER TABLE D4_DESCRIPTIVE_FLEX_FIELDS DEALLOCATE UNUSED;
	ALTER TABLE D4_DOC_CHANGE_HISTORY DEALLOCATE UNUSED;
	ALTER TABLE D4_INVOICE_LINES_TEMP DEALLOCATE UNUSED;
	ALTER TABLE D4_KPI_MONTHLY DEALLOCATE UNUSED;
	ALTER TABLE D4_KPI_SUPPLIERS_MONTHLY DEALLOCATE UNUSED;
	ALTER TABLE D4_KPI_USERS_MONTHLY DEALLOCATE UNUSED;
	ALTER TABLE D4_PO_MESSAGE DEALLOCATE UNUSED;
	ALTER TABLE D4_RNS_LOG DEALLOCATE UNUSED;
	ALTER TABLE D4_RNS_QUEUE DEALLOCATE UNUSED;
	ALTER TABLE D4_SEARCH DEALLOCATE UNUSED;
	ALTER TABLE D4_USER_RULE_HISTORY DEALLOCATE UNUSED;
	ALTER TABLE D4_CONSOLE_NOTIFICATION DEALLOCATE UNUSED;
	ALTER TABLE D4_HOLD_HANDLED DEALLOCATE UNUSED;


	--match aliases section
	-- delete D4_ITEM_MAPPING;
	--alter table D4_ITEM_MAPPING deallocate unused;

Cleanup the dehydration store

Access the BPEL Console to clean out all BPEL instances before you begin processing invoices against the new Oracle E-Business Suite.

Open a browser and navigate to http://soa.vm.net:7777/BPELConsole/
Supply username and password
Select default in the Jump To menu (upper right hand corner)
Select the Administration tab
Open the Actions tab beneath the Administration tab
Click Purge all instances. This purges the domain default
Repeat this process for the domains default and services.