A RIB Application Installer Screens

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.

Table A-1

Field Title	Which install phase 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

Table A-2

Field Title	Configure Advanced Queuing JMS topics for RIB?
Field Description	Used by the installer's build.xml to determine whether or not 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

Table A-3

Field Title	Generate new config file?
Field Description	Used by the installer to determine whether or not 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: Advanced Queuing JMS Details

Fields on this screen:

Table A-4

Field Title	JMS Server Home
Field Description
Destination	rib-deployment-env-info.xml
Example	oracle@myhost:/u01/oradata
Notes

Table A-5

Field Title	JMS URL
Field Description
Destination	rib-deployment-env-info.xml
Example	single instance thin client: jdbc:oracle:thin:@myhost:1521:mydb
Notes

Table A-6

Field Title	JMS Port
Field Description
Destination	rib-deployment-env-info.xml
Example	1521
Notes

Table A-7

Field Title	JMS User
Field Description
Destination	rib-deployment-env-info.xml
Example	RIB_AQ
Notes

Table A-8

Field Title	JMS Password
Field Description
Destination	rib-deployment-env-info.xml
Example
Notes

Screen: Number of Oracle AS Installations

Fields on this screen:

Table A-9

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:

Table A-10

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

Table A-11

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

Table A-12

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

Table A-13

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

Table A-14

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:

Table A-15

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:

Table A-16

Field Title	Select the App Server where rib-<app> will be installed
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:

Table A-17

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

Table A-18

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

Table A-19

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	[e-mail]
Notes

Table A-20

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	[e-mail], [e-mail]
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:

Table A-21

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

Table A-22

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

Table A-23

Field Title	rib-<app> OC4J User
Field Description
Destination	rib-deployment-env-info.xml
Example	oc4jadmin
Notes

Table A-24

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:

Table A-25

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

Table A-26

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

Table A-27

Field Title	<app> database schema password
Field Description	Password for the <app> database schema user
Destination	rib-deployment-env-info.xml
Example
Notes

Table A-28

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

Table A-29

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

Table A-30

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:

Table A-31

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

Table A-32

Field Title	Email server port
Field Description	The port for outgoing emails
Destination	rib-deployment-env-info.xml
Example	25
Notes

Table A-33

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	[e-mail]
Notes

Table A-34

Field Title	To address(es)
Field Description	List of recipients for rib-<app> email notifications
Destination	rib-deployment-env-info.xml
Example	[e-mail], [e-mail]
Notes