| Oracle® Retail Integration Bus Installation Guide Release 13.0.3 |
|
 Previous |
 Next |
Verify that correct URL's to the RIB Functional Artifacts are configured in the Java EE Applications.
Functional Artifact URL
JNDI URL
The RIB Diagnostic and Monitoring Tool (RDMT) kit is a collection of command line tools, written in Unix shell script along with supporting Java classes packaged in jar files. There are various tools to address these areas:
Installation Verification (reports)
Operations (scanning and monitoring)
Production (scanning and quick triage)
Test and Support (scanning and fine grain control)
AQ JMS support and tools
The RDMT Java support classes require Java 5.0. Installation will perform a check and fail if the path is not correct. Before you begin the installation process, verify that your Java version is corrrect.
Determine the location for installation. The recommended location is to put it in rib-home/tools-home directory. There is an empty rdmt subdirectory already there. This is only a placeholder. However, RDMT can be installed under any user in any directory.
Download the tar file (Rdmt13.0.3ForAll13.x.xApps_eng_ga.tar) and extract it. >tar svf Rdmt13.0.3ForAll13.x.xApps_eng_ga.tar.
cd to the rdmt directory and execute the configbuilder.sh script supplied with the toolkit. >./ configbuilder.sh
Once executed, it checks if the rdmt has been extracted under rib-home/tools-home directory. If so, it fetches all the necessary configuration information from rib-deployment-env-info.xml present under rib-home/deployment-home/conf directory and it automatically completes the RDMT installation.
If rdmt was extracted under some other directory with rib-home present on the same server, it prompts for the rib-home path. Provide the same and it fetches all the necessary configuration information from rib-deployment-env-info.xml present under specified rib-home/deployment-home/conf directory and it automatically completes the RDMT installation.
If rdmt was extracted in a remote server, it prompts for RIB configuration values during setup. The installation script will prompt for the configuration settings need to run the tools in the toolkit.
The installation will automatically configure for all the rib-<apps>s depending upon the applications in scope as defined in rib-deployment-env-info.xml. In case of remote installation, answer yes to configure additional rib<-ap>s. It is recommended that you configure all the rib-apps that have been installed in the RIB Installation.
Run the RibConfigReport. This report will run a battery of tests that will validate the RIB components installed.
The following are necessary directory parameters.
| Parameters | Setting |
|---|---|
|
RDMT Home Directory |
Rib1301ForAll13xxApps/rib-home/tools-home/rdmt/ |
|
RDMTLOGS Directory |
Rib1301ForAll13xxApps/rib-home/tools-home/rdmt /RDMTLOGS |
|
Temp Files Directory |
Rib1301ForAll13xxApps/rib-home/tools-home/rdmt /RDMTLOGS/tmp |
|
RIB App Builder rib-home Directory |
/u00/Rib1301ForAll13xxApps/rib-home |
The following are parameters for the JMS provider.
| Parameter | Setting |
|---|---|
|
AQ JMS User ID |
ribaq |
|
AQ JMS Password |
retek |
|
JMS Connection URL |
jdbc:oracle:thin:@host-name:port:sid |
The following are OC4J parameters for JMX functions:
| Parameter | Setting |
|---|---|
|
OC4J/JMX Host |
mspdev72 |
|
JMX Req Port |
6003 |
|
OC4J Instance name |
rib-rms-oc4j-instance |
|
OC4J App Name |
rib-rms |
|
OC4J User Name |
oc4jadmin |
|
OC4J Password |
welcome1 |
The following are parameters for each hospital (RMS, RWMS, SIM, and others).
| Parameter | Setting |
|---|---|
|
User Name |
rms |
|
Password |
retek |
|
Database URL |
jdbc:oracle:thin:@host-name:port:sid |
The RIB Hospital Administration Tool (RIHA) is a Java executable/application provided to perform RIB administration functions in the RIB Hospital database.
The minimum and preferred Java Runtime Engine (JRE) version to use with RIHA is 1.5 This JRE must be installed on the host where RIHA will be installed prior to running the configuration script.
RIHA can be installed on either a PC running a Windows operating system or in a UNIX environment. It is suggested, but not required, that it be installed where RIB13 has already been installed and configured.
Copy the Riha13.0.3ForAll13.x.xApps_eng_ga.tar file to the location where RIHA will be installed.
|
Windows |
C:\RIB_Tools\RIHA |
|
UNIX |
$RIB_HOME/tools-home/riha |
Decompress the tar file with an archive utility (e.g.: WinZip for windows or unzip for UNIX). This will extract all RIHA files into a directory named Riha13.0.3ForAll13.x.xApps_eng_ga.
Downloading Hibernate.
RIHA uses Open Source O-R mapping tool called Hibernate (http://www.hibernate.org). Due to licensing limitation RIHA cannot ship Hibernate along with its package, so hibernate 2.1.8 has to be download by the person installing RIHA. RIHA has been certified with only hibernate 2.1.8, do not download any other Hibernate version.
Download Hibernate (hibernate-2.1.8.zip) and extract the hibernate2.jar file from inside the zip file. Copy the hibernate2.jar to appropriate directory shown in the table below.
|
Windows |
C:\RIB_Tools\RIHA\Riha13.0.3ForAll13.x.xApps_eng_ga\external-lib |
|
UNIX |
$RIB_HOME/tools-home/riha/Riha13.0.3ForAll13.x.xApps_eng_ga/external-lib |
Go to the appropriate "bin" directory and execute the RIHA configuration executable file. This script, located in the path displayed in the table below, will run the rest of the installation and configuration process.
|
Windows |
C:\RIB_Tools\RIHA\Riha13.0.3ForAll13.x.xApps_eng_ga\bin\riha-config.bat |
|
UNIX |
$RIB_HOME/tools-home/riha/Riha13.0.3ForAll13.x.xApps_eng_ga/bin/riha-config.sh |
Create a user login. RIHA provides users with access to information contained in the applications RIB Hospital database. Users can view and modify this data and control the variables that make possible the feedback of messages into the system. Because of this, limiting the accessibility to this tool is imperative. RIHA supports the creation of user logins to guarantee that only designated users can execute this tool.
The following prompts ask the user to enter the credentials to create a new user login for RIHA. More than one user can be created.
Starting RIHA configuration utility... Create a new user login: Enter User Id: dannich Enter User First Name: Daniel Enter User Last Name: Nicholson Enter password: <password not shown> Verify password: <password not shown> User dannich created. Do you want to create another user? (y/n): n Creating hibernate configuration files... You can access multiple Error Hospital databases by setting multiple configuration files (even for the same product). Select [D]one when finished.
After creating the user, it checks if RIHA has been extracted under rib-home/tools-home directory. If so, it fetches all the necessary configuration information from rib-deployment-env-info.xml present under rib-home/deployment-home/conf directory. It configures for RIB hospital for the <app>s depending upon the applications in scope as defined in rib-deployment-env-info.xml.
User dannich created.
Do you want to create another user? (y/n): n
rib home path is detected:\dannich\rib-home\
Application (rib-rms) is in scope. Generating hibernate configuration file ....Loaded the rib-deployment-env-info.xml file successfully.Configuration file is generated successfully
Application (rib-rwms) is in scope. Generating hibernate configuration file ....Loaded the rib-deployment-env-info.xml file successfully.Configuration file is generated successfully
Application (rib-rpm) is in scope. Generating hibernate configuration file ....Loaded the rib-deployment-env-info.xml file successfully.Configuration file is generated successfully
Application (rib-sim) is in scope. Generating hibernate configuration file ....Loaded the rib-deployment-env-info.xml file successfully.Configuration file is generated successfully
Application (rib-tafr) is in scope. Generating hibernate configuration file ....Loaded the rib-deployment-env-info.xml file successfully.Configuration file is generated successfully
Application (rib-aip) is not in scope. Hence hibernate configuration file is not generated.
If RIHA is extracted under some other directory with rib-home present on the same server, it prompts for the rib-home path. Provide the same and it fetches all the necessary configuration information from rib-deployment-env-info.xml present under specfied rib-home/deployment-home/conf directory. It configures for RIB hospital for the <app>s depending upon the applications in scope as defined in rib-deployment-env-info.xml
Do you want to create another user? (y/n): nRib home is not detected.
Is there rib-home directory structure in the system?N/Y: yEnter the path of the rib-home directory: \dannich\rib-home\
Application (rib-rms) is in scope. Generating hibernate configuration file ....Loaded the rib-deployment-env-info.xml file successfully.Configuration file is generated successfully
Application (rib-rwms) is in scope. Generating hibernate configuration file ....Loaded the rib-deployment-env-info.xml file successfully.Configuration file is generated successfully
Application (rib-rpm) is in scope. Generating hibernate configuration file ....Loaded the rib-deployment-env-info.xml file successfully.Configuration file is generated successfully
Application (rib-sim) is in scope. Generating hibernate configuration file ....Loaded the rib-deployment-env-info.xml file successfully.Configuration file is generated successfully
Application (rib-tafr) is in scope. Generating hibernate configuration file ....Loaded the rib-deployment-env-info.xml file successfully.Configuration file is generated successfully
Application (rib-aip) is not in scope. Hence hibernate configuration file is not generated.
If RIHA was extracted in a remote server, the user is presented with a list of standard Retail applications to choose from and configure the database connection where the RIB Hospital of each application resides. It also prompts the user for the server hosting the XSD files for the RIB messages. Once the necessary information is entered, the user is returned to the Retail applications list to either configure a new connection or complete this process. Version 13.0.3 of the RIHA allows users to either enter a standard database JDBC connection string or a RAC database JDBC connection URL.
Standard database connection string setup process:
Please choose a product for configuring database information: 1) AIP - Advanced Inventory Planning 2) SIM - Store Inventory Management 3) RMS - Retail Merchandising System 4) RPM - Retail Price Management 5) RWMS - Retail Warehouse Management System 6) TAFR - TAFR Hospital Tables ([1], [2], [3], [4], [5], [6], [D]one): 3 Please choose the type of database for configuring database information: (1)RAC Database (2)Non-RAC Database ([1], [2]:2 Enter the connection URL [E.g: jdbc:oracle:thin:@mspdev57:1521:orcl ] : jdbc:oracle:thin:@mspdev94:1521:dvolr051 Enter user name: rmsseint121user Enter password: <password not shown> Verify password: <password not shown> Enter name of server hosting xsd files (e.g.: mspdev05.retek.int): http://mspdev85 Enter port number of server hosting xsd files (e.g.: 8080): 7777 Please choose a product for configuring database information: 1) AIP - Advanced Inventory Planning 2) SIM - Store Inventory Management 3) RMS - Retail Merchandising System 4) RPM - Retail Price Management 5) RWMS - Retail Warehouse Management System 6) TAFR - TAFR Hospital Tables ([1], [2], [3], [4], [5], [6], [D]one): D
RAC compatible database connection URL setup process:
Please choose a product for configuring database information: 1) AIP - Advanced Inventory Planning 2) SIM - Store Inventory Management 3) RMS - Retail Merchandising System 4) RPM - Retail Price Management 5) RWMS - Retail Warehouse Management System 6) TAFR - TAFR Hospital Tables ([1], [2], [3], [4], [5], [6], [D]one): 3 Please choose the type of database for configuring database information: (1)RAC Database (2)Non-RAC Database ([1], [2]:1 Enter the connection URL [E.g: jdbc:oracle:thin:@(DESCRIPTION =(ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = mspvip72)(PORT = 1521)) (ADDRESS = (PROTOCOL = TCP)(HOST = mspvip73)(PORT = 1521)) (LOAD_BALANCE = yes))(CONNECT_DATA =(SERVICE_NAME = dvolr02))) ] : jdbc:oracle:thin:@(DESCRIPTION =(ADDRESS_LIST =(ADDR ESS = (PROTOCOL= TCP)(HOST = mspvip94) (PORT = 1521))(ADDRESS = (PROTOCOL = TCP)(HOST = mspvip95)(PORT = 1521))(LOAD_BAL ANCE = yes))(CONNECT_DATA = (SERVICE_NAME = dvolr05))) Enter user name: rmsseint121user Enter password: <password not shown> Verify password: <password not shown> Enter name of server hosting xsd files (e.g.: mspdev05.retek.int): http://mspdev85 Enter port number of server hosting xsd files (e.g.: 8080): 7777 Please choose a product for configuring database information: 1) AIP - Advanced Inventory Planning 2) SIM - Store Inventory Management 3) RMS - Retail Merchandising System 4) RPM - Retail Price Management 5) RWMS - Retail Warehouse Management System 6) TAFR - TAFR Hospital Tables ([1], [2], [3], [4], [5], [6], [D]one): D
Finally the user is prompted to enter the full path for the Web browser to use when displaying the online help.
RIHA is configured and ready. Execute the RIHA start executable file to start using the RIB Hospital Administration tool.
| Windows | C:\RIB_Tools\RIHA\Riha13.0.3ForAll13.x.xApps_eng_ga\bin\riha.bat |
| UNIX | $RIB_HOME/tools-home/riha/Riha13.0.3ForAll13.x.xApps_eng_ga/bin/riha.sh |
|
 Copyright © 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|