You will need the following details about your environment for the installer to successfully deploy the RIB applications. Depending on the options you select, you may not see some screens.
Field Title | Which install phases do you wish to run? |
---|---|
Field Description |
Used by the installer's build.xml to determine which phases to run during the install. Each install phase will run a different command-line tool. Preparation Phase: check-version-and-unpack.sh Assembly Phase: rib-app-compiler.sh Deployment Phase: rib-app-deployer.sh -deploy-rib-func-artifact-war and/or rib-app-deployer.sh -deploy-rib-app-ear rib-<app> |
Destination |
|
Example |
|
Notes |
Field Title | Configure JMS topics for RIB? |
---|---|
Field Description |
Used by the installer's build.xml to determine whether to configure the JMS topics. Will run the command-line tool: rib-app-deployer.sh -prepare-jms |
Destination |
|
Example |
|
Notes |
Screen: Provide Inputs to Installer?
Fields on this screen
Field Title | Generate new config file? |
---|---|
Field Description |
Used by the installer to determine whether to prompt user for inputs needed to generate the rib-deployment-env-info.xml file. Also used by the installer's build.xml to determine whether or not to actually generate the new file. |
Destination |
|
Example |
|
Note |
Screen: JMS Server Configuration
Fields on this screen:
Field Title | JMS Server Configuration |
---|---|
Field Description |
Used by the installer to determine how many sets of JMS server inputs should be collected from the user. |
Destination |
|
Example |
|
Notes |
Screen: Number of JMS Servers
Fields on this screen:
Field Title | Total Number of JMS Servers |
---|---|
Field Description |
Used by the installer to determine how many sets of JMS server inputs should be collected from the user. |
Destination |
|
Example |
2 |
Notes |
Screen: JMS Server 1
Note: The installer will request inputs for as many JMS servers as were chosen on the previous screen. There will be one input screen for each JMS server. |
Fields on this screen:
Field Title | JMS Server ID |
---|---|
Field Description |
The name of the JMS server. |
Destination |
rib-deployment-env-info.xml |
Example |
jms1 |
Notes |
Screen: JMS Server 1 Details
Note: The installer will request inputs for as many JMS Servers as were chosen on the previous screen. There will be one input screen for each JMS server. |
Fields on this screen:
Field Title | AQ1 JMS Server Home |
---|---|
Field Description |
|
Destination |
rib-deployment-env-info.xml |
Example |
oracle@myhost:/u01/oradata |
Notes |
Field Title | AQ1 JMS URL |
---|---|
Field Description |
|
Destination |
rib-deployment-env-info.xml |
Example |
single instance thin client: jdbc:oracle:thin:@myhost:1521:mydb |
Notes |
Field Title | AQ1 JMS Port |
---|---|
Field Description |
|
Destination |
rib-deployment-env-info.xml |
Example |
1521 |
Notes |
Field Title | AQ1 JMS User |
---|---|
Field Description |
|
Destination |
rib-deployment-env-info.xml |
Example |
RIB_AQ |
Notes |
Field Title | AQ1 JMS Password |
---|---|
Field Description |
|
Destination |
rib-deployment-env-info.xml |
Example |
|
Notes |
Screen: Number of Oracle AS Installations
Fields on this screen:
Field Title | Total Number of Application Server Installations |
---|---|
Field Description |
How many different Oracle Application Servers will your rib-<app> applications be installed to? The installer uses this information to determine how many App Servers it needs to request inputs for. |
Destination |
|
Example |
1 |
Notes |
Screen: App Server <X> Details
Note: The installer will request inputs for as many Application Servers as were chosen on the previous screen. There will be one input screen for each App Server. |
Fields on this screen:
Field Title | App Server Instance Name |
---|---|
Field Description |
Your App Server's instance name can be found in this file:$ORACLE_HOME/config/ias.propertiesIn the ias.properties file, it is called "IASname." |
Destination |
rib-deployment-env-info.xml |
Example |
1013AS_1.my_server.my_domain.com |
Notes |
Field Title | App Server Home |
---|---|
Field Description |
The format should be:<user>@<host>:<ORACLE_HOME>where<user> is the user who owns the files in the ORACLE_HOME<host> is the name or IP address of the server where the App Server is installed<ORACLE_HOME> is the filesystem path to the ORACLE_HOME |
Destination |
rib-deployment-env-info.xml |
Example |
myuser@myhost:/path/to/oracle/home |
Notes |
Field Title | OPMN Request Port |
---|---|
Field Description |
The request port can be found in this file: $ORACLE_HOME/opmn/conf/opmn.xml <port local="6100" remote="6200" request="6003"/> |
Destination |
rib-deployment-env-info.xml |
Example |
6003 |
Notes |
Field Title | OHS HTTP Port |
---|---|
Field Description |
The HTTP port can be found in this file: $ORACLE_HOME/Apache/Apache/conf/httpd.conf |
Destination |
rib-deployment-env-info.xml |
Example |
7777 |
Notes |
Field Title | Java Home |
---|---|
Field Description |
The JDK in the ORACLE_HOME. It can be found here: $ORACLE_HOME/jdk |
Destination |
rib-deployment-env-info.xml |
Example |
/path/to/oracle/home/jdk |
Notes |
Screen: Choose Apps to Install
Fields on this screen:
Field Title | Install rib-<app> |
---|---|
Field Description |
Used by the installer's build.xml to determine which applications to deploy during the Deployment Phase. This screen may also be shown if you have chosen not to run the Deployment Phase, but have chosen to generate a new rib-deployment-env-info.xml file. In this case, it is used by the installer to determine which inputs to request from the user to create the rib-deployment-env-info.xml file. |
Destination |
rib-deployment-env-info.xml |
Example |
|
Notes |
Screen: Choose App Server for rib-<app>
Note: The screenshot above is for rib-sim. There will be a similar screen for rib-func-artifacts and for each other rib-<app> that you have chosen to install. |
Fields on this screen:
Field Title | Select the App Server where rib-<app> will be nstalled |
---|---|
Field Description |
Used by the installer's build.xml to determine which application server to associate the rib-<app>'s OC4J instance with. Note: The installer will request this information for rib-func-artifact, even if you have chosen not to install rib-func-artifact at this time. The reason is because the rib-func-artifact inputs are required to exist in the rib-deployment-env-info.xml file in order to deploy any rib-<app>. |
Destination |
rib-deployment-env-info.xml |
Example |
|
Notes |
Screen: Set Email Defaults
Fields on this screen:
Field Title | Email server host (SMTP) |
---|---|
Field Description |
If you are going to use the same email host for multiple rib-<app> applications you can enter it here. |
Destination |
|
Example |
smtp.mycompany.com |
Notes |
Field Title | Email server port |
---|---|
Field Description |
If you are going to use the same email port for multiple rib-<app> applications you can enter it here. |
Destination |
|
Example |
25 |
Notes |
Field Title | From email address |
---|---|
Field Description |
If you are going to use the same email originator address for multiple rib-<app> applications you can enter it here. |
Destination |
|
Example |
rib@mycompany.com |
Notes |
Field Title | To email address(es) |
---|---|
Field Description |
If you are going to use the same email recipients list for multiple rib-<app> applications you can enter it here. |
Destination |
|
Example |
name1@mycompany.com, name2@mycompany.com |
Notes |
Screen: rib-<app> OC4J Details
Note: The screenshot above shows the OC4J details input screen for rib-sim. Depending on which rib-<app> applications you are installing, the installer may display one or more input screens for each rib-<app>. |
Fields on this screen:
Field Title | rib-<app> OC4J Instance Name |
---|---|
Field Description |
The name of the OC4J instance where the rib-<app> will be deployed. |
Destination |
rib-deployment-env-info.xml |
Example |
rib-sim-oc4j-instance |
Notes |
Field Title | rib-<app> OC4J Instance Home |
---|---|
Field Description |
The format should be as follows: <user>@<host>:<ORACLE_HOME>/j2ee/<oc4j-instance> where: <user> is the user who owns the files in the ORACLE_HOME <host> is the name or IP address of the server where the App Server is installed <ORACLE_HOME> is the filesystem path to the ORACLE_HOME <oc4j-instance> is the OC4J instance name |
Destination |
rib-deployment-env-info.xml |
Example |
myuser@myhost:/path/to/oracle/home/j2ee/rib-sim-oc4j-instance |
Notes |
Field Title | rib-<app> OC4J User |
---|---|
Field Description |
|
Destination |
rib-deployment-env-info.xml |
Example |
oc4jadmin |
Notes |
Field Title | rib-<app> OC4J Password |
---|---|
Field Description |
|
Destination |
rib-deployment-env-info.xml |
Example |
|
Notes |
Screen: <app> Details
Note: The screenshot above shows the Details screen for SIM. Depending on which rib-<app> applications you are installing, you will see different details input screens. For some of the Oracle Retail applications, these inputs may appear on separate installer screens rather than all on one screen. |
Fields on this screen:
Field Title | <app> database URL |
---|---|
Field Description |
JDBC URL for the database |
Destination |
rib-deployment-env-info.xml |
Example |
single instance thin client: jdbc:oracle:thin:@myhost:1521:mydb |
Field Title | <app> database schema User |
---|---|
Field Description |
Database user where the <app> database schema was installed |
Destination |
rib-deployment-env-info.xml |
Example |
SIM_USER |
Notes |
Field Title | <app> database schema password |
---|---|
Field Description |
Password for the <app> database schema user |
Destination |
rib-deployment-env-info.xml |
Example |
|
Notes |
Field Title | <app> JNDI URL |
---|---|
Field Description |
URL which will be used by rib-<app> to connect to the <app> application. |
Destination |
rib-deployment-env-info.xml |
Example |
opmn:ormi://myhost:6003:sim-oc4j-instance/sim |
Notes |
Field Title | <app> JAAS User |
---|---|
Field Description |
When rib-<app> authenticates to the <app> JNDI naming service through the URL in the previous field, it will provide this user name. |
Destination |
rib-deployment-env-info.xml |
Example |
oc4jadmin |
Notes |
Field Title | <app> JAAS Password |
---|---|
Field Description |
The password for the <app> JAAS user |
Destination |
rib-deployment-env-info.xml |
Example |
|
Notes |
Screen: rib-<app> Email Notification Details
Note: The screenshot above shows the Email Notification Details screen for rib-sim. The installer may show similar screens for other rib-<app>, depending on which rib-<app> applications you are currently installing. |
Fields on this screen:
Field Title | Email server host (SMTP) |
---|---|
Field Description |
The SMTP server that will be used to send notification emails from the RIB |
Destination |
rib-deployment-env-info.xml |
Example |
smtp.mycompany.com |
Notes |
Field Title | Email server port |
---|---|
Field Description |
The port for outgoing emails |
Destination |
rib-deployment-env-info.xml |
Example |
25 |
Notes |
Field Title | From address |
---|---|
Field Description |
The email address that the rib-<app> email notifications will originate from. |
Destination |
rib-deployment-env-info.xml |
Example |
rib@mycompany.com |
Notes |
Field Title | To address(es) |
---|---|
Field Description |
List of recipients for rib-<app> email notifications |
Destination |
rib-deployment-env-info.xml |
Example |
name1@mycompany.com, name2@mycompany.com |
Notes |