Installation Prerequisites
Purpose
This documents lists the pre-requisites that must be in place prior to beginning an implementation of PROCESSIT at a customer site.
PROCESSIT runs on Oracle Infrastructure Technology Stack, and can be installed ground up or deployed as a Virtual Appliance application for VMware.
Hardware must be made available prior to the visit depending on the agreed upon architectural approach and according to PROCESSIT system requirements (ground up or virtual appliance).
- EBSDB refers to the Oracle E-Business Suite Database.
- SOADB refers to the database used by PROCESSIT as repository, interface for scanned invoices and Dehydration Store.
- VA refers to PROCESSIT Virtual Appliance.
Application Software Download
PROCESSIT Software is available for download at ftp.readsoft-us.com. Access is individual and provided by the ReadSoft Project Manager. Get in touch with your ReadSoft contact to obtain access to the ftp server.
- Oracle Infrastructure Technology Stack Software: ftp://ftp.readsoft-us.com/Software/Oracle/PROCESSIT/Prereqs/
- Latest PROCESSIT release:ftp://ftp.readsoft-us.com/Software/Oracle/PROCESSIT/Latest_Release/
- Virtual Appliance: ftp://ftp.readsoft-us.com/Software/Oracle/PROCESSIT/Virtual_Appliance/
The PROCESSIT VA Software Package is approx. 12GB in filesize. If a ReadSoft consultant is doing a physical visit, the package can be brought on a physical disk or harddrive. If the VA is deployed via remote Access or by the local IT VMware team, the package must be downloaded. Due to the size of the VA download, it is recommended to use an ftp client to connect and download the package, for instance FileZilla.
Environment and date
Requirements Checklist
Site Access | ||
Browser/Java | ||
SQL developer to SOADB | ||
GUI/X client | ||
VMware vSphere Client | ||
VMware name | ||
VA Server IP Address | ||
VA Server DNS Name | ||
EBSDB host IP Address | ||
EBSDB host DNS Name | ||
EBSDB SID | ||
EBSDB Listener Port | ||
APPS password | ||
SYSTEM password | ||
Oracle Login URL | ||
Superuser created | ||
Functional User | ||
Test data Available | ||
Installation Server IP Address | ||
Installation Server DNS Name | ||
Installation Server Operating System | ||
Installation Server Dependencies and patches | ||
Installation Server root password | ||
Installation Server oracle user | ||
Installation Server mount points | ||
Installation Server PROCESSIT software | ||
SOADB Host IP Address | ||
SOADB DNS Name | ||
SOADB SID | ||
SOADB Listener port | ||
SOADB SYS Password | ||
SOADB SYSTEM Password | ||
irca.sh script run | ||
xxd4_apps_oebs.sq run |
Site Access | ||
Browser/Java | ||
SQL developer to SOADB | ||
GUI/X client | ||
VMware vSphere Client | ||
VMware name | ||
VA Server IP Address | ||
VA Server DNS Name | ||
EBSDB host IP Address | ||
EBSDB host DNS Name | ||
EBSDB SID | ||
EBSDB Listener Port | ||
APPS password | ||
SYSTEM password | ||
Oracle Login URL | ||
Superuser created | ||
Functional User | ||
Test data Available | ||
Installation Server IP Address | ||
Installation Server DNS Name | ||
Installation Server Operating System | ||
Installation Server Dependencies and patches | ||
Installation Server root password | ||
Installation Server oracle user | ||
Installation Server mount points | ||
Installation Server PROCESSIT software | ||
SOADB Host IP Address | ||
SOADB DNS Name | ||
SOADB SID | ||
SOADB Listener port | ||
SOADB SYS Password | ||
SOADB SYSTEM Password | ||
irca.sh script run | ||
xxd4_apps_oebs.sq run |
General Requirements (functional and technical)
Minimum requirements for both functional and technical ReadSoft PROCESSIT consultants are:
- Customers site access, physical or virtual.
- Browser access to the installed version of PROCESSIT.
- Browser and Java access to the Oracle E-Business Suite.
- Secure Shell (SSH) (putty) access to PROCESSIT server(s).
- SQLDeveloper access to PROCESSIT Database (SOA Server).
- Internet access for troubleshooting, downloads and mail access.
- Ports 7001 and 7777 must be open from the client network to the network where the PROCESSIT (Weblogic / SOA Server) resides. Without this, PRCOCESST is not accessible from a client browser.
Initial Application Configuration (functional)
Prior to technical setup, PROCESSIT must be installed and connected to an Oracle E-Business Suite at the customer site.
To setup and configure the application:
- DNS Name of the PROCESSIT WebLogic user interface server. Required to configure various URLs in PROCESSIT Configuration Manager. If no DNS name is available, the IP address is required.
- Access to an Oracle E-Business Suite super user. This super user is utilized by PROCESSIT to receive notifications about document discrepancies, and is required for any workflow process.
Testing document workflows (functional)
- Url to Oracle E-Business Suite login page
- Access to and login credentials for an Oracle EBS FND user connected to employee.
- Access to these responsibilities in Oracle E-Business Suite modules:
- System Administrator
- AP
- HR
- PO
Invoice Test Data
- Organization ID
- Vendor number for a valid vendor
- Vendor Site name
- Currency
- Valid GL accounting string to account a standard GE invoice
- PO data
VA Deployment (technical)
Access to a VMware Console with VMware vSphere client from a Windows operating system to deploy the machine. This can be done by the ReadSoft consultant or by the local VMware IT Team.
After deployment, this information is neccessary for the deployed machine:
- DNS Name
- IP Address
VA Initial Configuration (technical)
Prior to configuration, the local DBA must run the script xxd4_apps_oebs.sql
provided by ReadSoft on the Oracle E-Business Suite to create the user XXD4_APPS and give this user grants on the EBS database. Alternatively, provide the ReadSoft consultant with access to and login credentials for for SYSTEM and APPS in the EBS Database
After deployment of PROCESSIT VA to VMWARE, the consultant requires:
- GUI (X) access to the console. Preferably via access to the VMware Console using VMware vSphere Client Software. Only access to the deployed machine(s) is required.
- Access to the deployed VA as root and the user oracle. Both users are included in VA.
- Access to the seeded SOADB named orcl on PROCESSIT server with SQLDeveloper. This is For troubleshooting and testing purposes.
- It must be allowed to download software to the PROCESSIT server. This ensures that the latest version of PROCESSIT can be downloaded, since it might not be included in the deployed VA version. For fastest download access, an ftp client should be installed.
- Information for the Oracle E-Business Database connected with PROCESSIT:
- SID
- listener port
- DNS Name
- IP Address (EBSDB host). This is required because PROCESSIT refers to the alias readsoft.servers.ebs.
PROCESSIT Upgrade (technical)
- Prior to performing the upgrade, the latest release of PROCESSIT must be downloaded.
- The latest release must be available at the PROCESSIT install server. This requires access with SFTP to the server as user oracle.
- Access the PROCESSIT install server with using a GUI (X-based) tool, for example VNC Viewer, VMware Console or Xming. This is due to the upgrade being performed with a Java based installer.
- Secure Shell (SSH) (putty) access to PROCESSIT server(s) as user oracle.
- Access to PROCESSIT DB with SQLDeveloper. This is required for troubleshooting purposes.
Ground-Up install including Oracle Technology Stack and RDBMS (technical)
Prior to performing a full ground Up install of PROCESSIT, including Oracle Technology Stack (SOA, WebLogic and RDBMS) and creating a Database (Dehydration Store), the server(s) must be installed and configured with an Operating System.
Required dependencies and patches must be installed.
- The Oracle Infrastructure Technology Stack Software and latest release of PROCESSIT must be downloaded and available.
- The JAVA JDK Installation kit 1.6+ must be available. PROCESSIT is not certified with Java JDK 1.7 or JRockit.
- User oracle (or equivalent) must be created.
- IP Addresses and DNS Names of the server(s).
- Access as root. This can be directly or via sudo su.
- Installation of Oracle Software requires X Windows (GUI).
- Direct access to login to X (GUI) as user oracle. This is required to run the installer.
Ground-Up install, including Oracle Technology Stack, excluding RDBMS (technical)
The requirements listed in this section is in addition to the requirements listed in the section above.
This installation is assumed to be run on a pre-installed database SOADB.
Prior to the install, the script irca.sh
must be run as SYS on the SOADB. The script creates the users ORAPBEL, ORAESB and ORAWSM. Login credentials for these users must be available to the consultant. Our recommendation is to use default passwords.
If the local DBA does not want ORAESB and ORAWSM schemas to have SYSTEM as default tablespaces, appropriate tablespaces for those users should be created and all install scripts modified accordingly. Refer to this Oracle Support Entry for more information: https://support.oracle.com/epmos/faces/DocumentDisplay?id=577741.1
- IP Address and DNS Name of the SOADB Host.
- SID and listener PORT of the SOADB.
- SYS and SYSTEM login credentials including passwords.
- An entry in $ORACLE_HOME/network/admin/tnsnames.ora (or other $TNS_ADMIN/tnsnames.ora) must be made for EBSDB pointing to Oracle E-Business Suite Database. In PROCESSIT, EBSDB is referred to as the name of the Database Link between SOADB and EBSDB.
First-time PROCESSIT install
- The script
xxd4_apps_oebs.sql
must be run on the Oracle E-Business Suite by the customer DBA prior to installation. Otherwise passwords for SYSTEM and APPS in the EBS Database is required for the initial install. - A full Oracle Infrastructure Technology Stack.
- EBSDB Host IP Address
- EBSDB Host DNS Name
- EBSDB SID
- EBSDB Listener port.
- It is necessary to launch the installer in a GUI/X session, since the PROCESSIT installer uses Java.
- Secure Shell (SSH) (putty) access to PROCESSIT server(s).
- SQLDeveloper access to the SOADB.