PROCESSIT 7.4 R1
For Oracle Fusion Middleware 11g

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

Virtual Appliance InstallationVirtual Appliance DeliveryVirtualization ResourcesVirtual Server StandardsRequirements for Virtual ApplianceSoftware requirementsInstallation Machine Hardware RequirementsHard disk requirements detailsJAVA JDK requirement detailsTemporary disk space requirement detailsEnd-user workstation requirementsIntegration with Oracle E-Business SuiteVirtual Appliance InstallationCreate Snapshot After Copying FilesInitial Setup ScriptTest DB link between SOA and EBSCheck SOA config filesSetting Up Remote DesktopSample JDBC connection stringsWith SIDWith Service NameWith RAC

Virtual Appliance Installation

The purpose of this section is to outline the technical components and associated configuration that encompasses the PROCESSIT Virtual Appliance. The pre-packaged virtual appliance is designed to provide ReadSoft customers with a much simplified product implementation, and a high degree of system performance, predictability, and reliability.

You must be using minimum VMware ESX 4.x or VMware ESXi 4.x as operating system for your virtualization host.

Virtual Appliance Delivery

The PROCESSIT Virtual Appliance can be downloaded from ftp.readsoft-us.com, or is delivered via shipment of a hard drive to the customer's site or to the ReadSoft installation consultant who will perform the installation and PROCESSIT configuration.

The Virtual Appliance is delivered as an approximately 10GB zip file. The .zip file includes a thin-provisioned virtual disk. This allows the file for the virtual disk being distributed to only be as large as required to hold the data contained.

Virtualization Resources

PROCESSIT and the bundled Oracle components can be deployed in a virtualized environment. Click her for further information on this topic and the policies for supporting this configuration by VMware and Oracle, or see VMware's reference to the Oracle Support Policy for VMware.

Virtual Server Standards

The PROCESSIT Virtual Appliance is delivered with the following components:

  • Operating System: Oracle Enterprise Linux 5 update level 8
  • Java JDK 1.6 with JAVA_HOME environment variable pointing to the JDK installation directory. (See details below)
  • Oracle Database Version Enterprise Edition 11g
  • Oracle SOA Suite: Oracle BPEL Process Manager (a component of Oracle SOA Suite) 10.1.3.5 patched to the latest MLR2 level
  • Oracle WebLogic Version 10.3.2
  • PROCESSIT Version 7.2

Requirements for Virtual Appliance

Software requirements

VMware operating system VMware ESX 4.x, VMware ESXi 4.x or VMware ESXi 5.x

vSphere Client Compatible with the operating system.

Installation Machine Hardware Requirements

  • Processor: Dual-core 1.5-GHz CPU or greater
  • Accumulated hard disk requirements 1st year: 200GB, 2nd year: 220GB, 3rd year: 240GB (etc.)
  • Min. 12Gb+ RAM. 16GB+ recommended.
  • Temporary Disk Space: 10GB used during component installations

Hard disk requirements details

The hard disk space requirement calculation is based on the following assumptions: A single page invoice is approx 100 kb. 100 invoices a day with 10 concurrent users. Assuming BPEL workflow data is purged on a regular basis, and that the image archive delivered in the standard solution is used.

JAVA JDK requirement details

The Products installation program requires a Java run time environment (JRE) to run. A JRE is bundled in the Windows installation program and in some UNIX installation programs (those with filenames ending in .bin). For other UNIX platforms, the installation program does not install a JDK. Filenames for these installation programs end in .jar. To run the .jar installation programs, you must have the appropriate version of the JDK installed on your system, and include the bin directory of the JDK at the beginning of the PATH variable definition.

It is important that you use a JDK because the installation process assigns values to JAVA_HOME and related variables to point to the JDK directory.

Temporary disk space requirement details

The PROCESSIT Virtual Appliance comes pre-configured. As a convenience to our customers, we make Oracle WebLogic, Oracle SOA Suite, and the Oracle Database installations available, should you ever need to perform a re-installation.

The following information only applies to the situation where you would perform a re-install.

The installation program uses a temporary directory into which it extracts the files necessary to install the software on the target system. During the installation process, your temporary directory must contain sufficient space to accommodate the compressed Java Run-time Environment (JRE) bundled with the installation program, and an uncompressed copy of the JRE that is expanded into the temporary directory. The extracted files are deleted from the temporary directory at the end of the installation process. The files in the temporary directory require approximately 2.5 times the space that is ultimately required for the installation. If you do not have enough temporary space to run the installation program, you are prompted to specify an alternate directory or exit the installation program. By default, the installation program uses the following temporary directories:

  • Windows: Directory referenced by the TMP system variable
  • UNIX: System-dependent temporary directory

End-user workstation requirements

Processor
Intel® Pentium® based 1.5-GHz CPU or greater
Supported browsers
Firefox 3.6+, Internet Explorer 7+, Chrome 11+, Apple Safari 5+
Display Resolution
1280 x 800, min, 8-bit (256) Color
Network
TCP/IP 100 MB LAN connection
E-mail Transport Support
SMTP and POP3. E-mail client with SMTP/POP3 support is required for notificaitons.

Integration with Oracle E-Business Suite

Oracle E-Business Suite
Version R12 version 12.0.6 or newer; or 11i versions 11.5.9 or 11.5.10
Modules
  • Oracle Accounts Payable
  • Oracle General Ledger
  • Oracle Purchasing (optional)
  • Oracle Project Accounting (optional)
  • Oracle Human Resources (optional)
Employee creation
Employees can be created either via Oracle Purchasing or via Oracle Human Resources, and assigned to Oracle FND_USER

Virtual Appliance Installation

  1. Open a vSphere client for VMware Application deployment.
  2. Open the File menu
  3. Select Deploy OVF. This opens a deployment wizard
  4. In Source, select PROCESSIT.ovf
  5. Click Next
  6. OVF Template Details gives an overview of the deployment size, approximately 400GB.
  7. Click Next
  8. In Name and Location, specify the application name PROCESSIT and the virtual machine location for the application deployment. You must select the location by browsing.
  9. Click Next after supplying location and name.
  10. In Host / Cluster, specify the host IP address for the deployment by selecting an IP address from the list of available addresses.
  11. Resource pool lets you select the resource pool for the deployment.
  12. Click Next.
  13. Datastore shows the available space on the selected machines. You must select a location to store the VM files.
  14. Click Next
  15. In Disk Format specify how to format the data storage.
    • Select Thin provisioned format to begin with the minimum required disk space and let it grow in size over time. This is the recommended choice.
    • Select Thick provisioned format to make all storage space available immediately, which uses approximately 400 Gb.
  16. Click Next
  17. Ready to Complete shows a summary of the deployment settings. When you are satisfied with the settings, click Finish to start copying files.
  18. This deployment process takes approx. 2 hours to complete.

Create Snapshot After Copying Files

When the deployment is complete and all files are copied, ReadSoft recommends to snapshot the virtual machine. This way, you can always reset to a clean environment. You can power off your VM prior to taking the snapshot, which limits the snapshot to approx. 1GB.

  1. In vSphere client, right-click the PROCESSIT deployment machine.
  2. Select Snapshot
  3. Select Take Snapshot.
  4. Specify a name and a description for the snapshot, for example baseline snapshot.

Initial Setup Script

After deploying the virtual application and talking a snapshot, you must specify the initial settings for the application, including setting up the root user, supplying the Oracle E-Business Suite address and setting the basic PROCESSIT properties.

  1. To activate the PROCESSIT machine, right-click the machine in the vSphere client, select Power and Power on.
  2. When turned on, the machine probes for new hardware and starts the Oracle DB, SOA and WebLogic services. The system continues to the console login screen.
  3. Open the console for the PROCESSIT machine.
  4. Log in to the console with user root using the root user password.
  5. Start the PROCESSIT Initial Config script from the console desktop.
  6. Click Run in Terminal from the dialog
  7. Supply a new password for the root unix user. Please remember this password.
  8. Supply the IP address for the Oracle E-Business Database server.
  9. Supply the SID for the Oracle E-Business Database server.
  10. Supply the port number for the Oracle E-Business Database server.
  11. You receive a notification to edit the PROCESSIT properties file. You must edit the properties file before continuing with the script. You may get an error about JAVA_HOME at this point. Ignore it, as the install_OEBA_scripts should be run as user.
  12. The PROCESSIT properties file opens. The file is located in the processit folder on the console desktop for the user oracle.
  13. Update the properties file with values specific to your Oracle E-Business Suite.
  14. Return to the script and press Enter when editing is completed.
  15. The PROCESSIT Installer application launches. From here you must install database objects to the Oracle E-Business Suite Database.
  16. Click Install All in the Installer window
  17. You then receive a notification to configure jdbc data sources in WebLogic. You must do this before continuing with the script.
  18. Open a browser in the console and navigate to the address http://weblogic:7001console
  19. Log in to the WebLogic server administration with user weblogic and password weblogic1
  20. In the WebLogic console, select JDBC data sources.
  21. Select the data source D4_OEBS_APPS.
  22. Navigate to the tab Connection Pool.
  23. Set the data source connection pool url to match your Oracle E-Business Suite settings. Do not change the domain, only the port and SID values.
  24. Click Save and return to the WebLogic console.
  25. Select the data source INVOICES_DB.
  26. Navigate to the tab Connection Pool.
  27. Set the data source connection pool url, properties and password to match your INVOICES database.
  28. Click Save and return to the WebLogic console.
  29. In the WebLogic console, click Activate changes. If the changes are not registered, try clicking Undo All Changes. Close the browser.
  30. Return to the script and press Enter to finish the script.
  31. Restart the machine. Click System - Shut Down - Restart
  32. Process completed. When the machine is restarted, you are ready to start the PROCESSIT application and configure the business rules to match your requirements. Please refer to the PROCESSIT setup guide or PROCESSIT Assistant for further details.

Test DB link between SOA and EBS

  1. On the PROCESSIT machine, open a terminal window and logon as the Oracle user.
  2. Open SQL*Plus sqlplus / as sysdba
  3. Once connected to the SOA database, execute the following SQL statement: select * from dual@ebsdb;
  4. If the above statement returns an error, re-create the database link by performing these steps:
    1. Drop public database link ebsdb;
    2. Create public database link ebsdb
    3. connect to apps identified by [apps pw] using 'EBSDB', where [apps pw] is correct for your environment.
    4. The entry for EBSDB in the file $ORACLE_HOME/network/admin/tnsnames.ora must be edited to be correct for your EBS environment

Check SOA config files

Log on to the SOA applications server and navigate to the following directory where the EBSAdapter.xml file is located:


		grep -i database $ASROOT/j2ee/oc4j_soa/applib/EBSAdapter.xml

Verify the lines contain the correct connection string, user and password

Log on to the SOA applications server and navigate to the following directory where the data-sources.xml file is located.


		view $ASROOT/j2ee/oc4j_soa/config/data-sources.xml

Verify the file contains the correct connection string, user and password.

Setting Up Remote Desktop

The desktop of the PROCESSIT machine can be accessed using VNC by performing the following steps

  1. Run vncserver to create the initial configuration directory: vncserver :1
  2. Edit the ~/.vnc/xstartup file and uncomment the following lines to allow normal desktop: 
    
		#unset SESSION_MANAGER
		#exec /etc/X11/xinit/xinitrc
  3. Stop vncserver: vncserver -kill :1
  4. Generate the VNC Password file: vncpasswd
  5. Restart vncserver: vncserver :1

Sample JDBC connection strings

With SID

jdbc:oracle:thin:@[HOST][:PORT]:SID

With Service Name

jdbc:oracle:thin:@//[HOST][:PORT]/SERVICE

With RAC


		jdbc:oracle:thin:@(DESCRIPTION=(LOAD_BALANCE=on)
		(ADDRESS=(PROTOCOL=TCP)(HOST=host1) (PORT=1521))
		ADDRESS=(PROTOCOL=TCP)(HOST=host2) (PORT=1521))
		CONNECT_DATA=(SERVICE_NAME=service)))