RIHA JOB AID

Contents

Introduction............................................................................................................................................................3 Purpose of this Document....................................................................................................................................3 Scope of this Document.......................................................................................................................................3 Glossary...................................................................................................................................................................4 Overview.................................................................................................................................................................6 RIHA Installation and Setup.................................................................................................................................7 Logging into RIHA.................................................................................................................................................8 RIB Hospital Message Handling........................................................................................................................11 Search for messages...........................................................................................................................................11 View message.....................................................................................................................................................12 Delete message...................................................................................................................................................14 Edit and Validate message.................................................................................................................................15 Export message to local drive............................................................................................................................16 Import message from local drive.......................................................................................................................16 Appendix...............................................................................................................................................................17

Introduction
Purpose of this Document
Oxygen is a new business venture undertaken by Woolworths Ltd, AU with the intention to launch a new chain of hardware stores similar to the Lowes footprint in the USA. The Oracle Retail application suite was successfully deployed by Logic for Lowes Mexico, and it is our intention to replicate that same delivery model, and achieve an accelerated deployment schedule with minimal risk This document provides an overview of the RIB Hospital Administration, and defines the process required to diagnosis errors that occurrs while processing messages through the Oracle Retail Integration Bus (RIB).

Scope of this Document

The scope of this document includes the following: 1. RIHA installation and setup. 2. Handling RIB Hospitalmessages with RIHA.

Glossary
Glossary Term Attempt Count adapter Custom Flag Delete Pending Glossary Definition The number of times the e*Way and/or process has tried to process the message. An adapter represents one or more threads of control within the adapter that publishes or subscribes to the applicable XML messages. This value is used to signal that the message contains custom data. This is not currently used by the RIB; therefore its value is always set to "F" (false). A 'Yes' means that the message is marked for deletion and will be removed from the RIB Hospital when the retry adapter and/or process checks for messages to be deleted from the RIB Hospital. 'No' means that the message is not pending for deletion. The valid message family to which the message belongs. Each message family contains information specific to a related set of operations on a business entity or related business entities. This is the identifier of a single message in the Hospital database. It is the primary key that associates the message in the RIB_MESSAGE table with its corresponding data in the RIB_MESSAGE_FAILURE, RIB_MESSAGE_ROUTING_INFO and RIB_MESSAGE_HOSPITAL_REF tables. Optional ID string that identifies the message. Composite primary keys require multiple IDs. For example, a line item within a Purchase Order may contain the PO number and line item number as part of the ID. For example: <id>PONumber=12345</id> <id>ItemID=321</id> Messages in the queue are waiting to be reprocessed (Yes) or not being reprocessed presently (No). This ID represents the JMS server that the message is published to during retries from the hospital. The ID also represents the JMS server from which the message was originally published (or from which the message was originally attempted to be published). The format of this field is <JMS host name>:<JMS host port>. The text of the error message that describes why the message failed to process. The adapter name and/or process name. The maximum number of times a message in the RIB Hospital should be re-processed by an application. Each message family contains a set of sub-formats specific to the business event triggering message publication. The term message type embodies this specific sub-format. For

Family

Hospital ID

ID

In Queue JMS Queue ID

Last Error Description Location Max Attempts Message Type

Publish Time Reason Code

RIB Message ID Thread Value

example: a Purchase Order message family can contain message types such as "Create PO Header", "Create PO Detail", "Update PO Header", or "Delete PO Detail". The date/timestamp indicating when the message was published. This value identifies whether an error occurred during publication of the message or during consumption (subscription). The indicators are "JMS", "SUB", and "PUB". The "PUB" reason code is used by RMS to indicate that a reference to a message must be retained in the RIB Hospital. When retried, the adapter must call a special stored procedure (PUB_RETRY) that will publish the message once some specific conditions are met in the RMS application. ID of the Message within the RIB Hospital. This value is set only after the message is checked into the RIB Hospital. The thread value is used for parallel processing of messages within the same family. This value is added to the message during publication to the JMS so that it can routed through a specific adapter and/or process.

Overview
You can use RIB Hospital Administration to diagnosis errors that occurred while processing messages through the Oracle Retail Integration Bus (RIB). You can also use it to retry a message, stop processing a message, edit a message's XML code, or mark a message for deletion from the RIB Hospital. You will find more detailed information about the Oracle Retail Integration Bus and the RIB Hospital in the following publications available in PDF format from Oracle: RIB Integration Guide: An introduction to basic Enterprise Application Integration (EAI) concepts and to the RIB. RIB Operations Guide : Backend information about the Error Hospital, including configuration. RIB Installation Guide: An overview of the hardware, software, and browser requirements needed to run the RIB Hospital. It also provides application installation instruction.

RIHA Installation and Setup

The steps to install and setup riha: 1. Prerequisite: JDK 5.0 Update 22 is installed - jdk-1_5_0_22-windows-i586p.exe - http://java.sun.com/javase/downloads/index_jdk5.jsp 2. Copy the zip file from <sharepoint?> to your local drive for each environment you are going to manage a. riha_dev2.zip for Development b. riha_systemtest.zip for System Test c. riha_training.zip for Training 3. Extract zip file from step 2 4. Go to <riha_install>\bin folder 5. Create a Shortcut of riha.bat on the Descktop (Right click on riha.bat > Send to > Desktop) 6. Change shortcut name as necessary, RIHA <env> 7. Repeat 2-6 for each zip file per environment you would require

Logging into RIHA

The steps to open, login and selecting the application to prepare RIHA for handling RIB messages. 1. Run the RIHA <environment> shortcut on your Desktop to open the application 2. Login using the username rihauser and password rihauser and click on the Login button. The RIHA application window is displayed.

3. On the Tasks pad, select Hospital Admin Content. The Hospital Admin workspace is displayed.

4. On the Tasks pad and workspace divider, click the red left arrow to maximize the workspace

5. In the Select Application field, select an applicable application (RMS, RPM, SIM, TAFR). The Hospital Admin workspace is displayed populated with the following panes, Search Criteria Hospital Records, Message Viewer, and Hospital Record Details.

10

RIB Hospital Message Handling

Search for messages This procedure explains how to search for a message using the Search Criteria Pane. 1. Select an application. The Hospital Records pane expands. 2. Enter or select the criteria to limit your search in one or more of the following fields. If you would like to list all messages, leave the fields below empty. a. Last Error Date b. Family c. Message Type d. RIB Message ID e. ID f. Free Search Text

3. Click Search button. RIB error messages that match these criteria are displayed in the Hospital Records pane.

4. On the Hospital Records pane, you may filter the messages down

11

View message This procedure explains how view a message. 1. Select an application. The Hospital Records pane expands. 2. Search for a message. (If necessary, see Search for messages.) 3. Select a row that represents a hospital record. View the message. Note: When you select a row with the Load Message Details on selection check box selected, the message data is loaded automatically. If you do not select the Load Message Details on selection check box, you must double-click the row that represents a hospital record in order to load the data. 4. Expand the Message Viewer pane and select one of the following three views: a. Partial Tree View: This view allows you to scroll the message one child node at a time. It provides back and forward buttons to visit each child node, which can be expanded to look at its content.

b. Full Tree View: This view shows all the message's children, each of which you can expand.

12

c. Flat View: This view shows the XML document in its flat format.

5. Expand the Hospital Record Details pane. The pane is populated with data, including a description of the error message in the Last Error Description box.

13

Delete message This procedure explains how to mark a message for deletion from the RIB Hospital. 1. Select an application. The Hospital Records pane expands.
2. Search for messages. (If necessary, see Search for messages.)

3. Select a row that represents a hospital record.

4. Click Delete button. The message is deleted when the hospital retry adapters and/or process checks for messages to be deleted from the RIB Hospital. Note: A message that is in queue (the check box in the In Queue column is selected) cannot be deleted.

14

Edit and Validate message This procedure explains how to edit and validate a message. 1. View a message. (If necessary, see View a message.) 2. Insert the cursor within any portion of the message and make your applicable changes.

3. Click Validate button. The message is validated. 4. Click Apply button. If the message passes validation, the changes are saved to the database. If the message does not pass validation, the changes are not saved to the database. 5. If you click Cancel button instead of Apply button, then changes are rolled back to the previously saved data.

15

Export message to local drive This procedure explains how to save a message locally. 1. View a message. (If necessary, see View a message.)

2. Click Save To File button. The message will be saved to a text file following the specifications in the HospitalEntries.xsd.

Import message from local drive This procedure explains how to retrieve a message from a local location. 1. Select an application. 2. Click Import From File button. Scroll to the applicable message and click Open. The message must be formatted following the specifications in the HospitalEntries.xsd.
RDMT : The RIB Diagnostic and Monitoring Tool Kit (RDMT) is a collection of command line tools, written in UNIX shell script along with supporting Java classes packaged in jar files. RDMT path : /applic/oracle/product/Rib1311ForAll13xxApps/rib-home/tools-home/rdmt Then execute the rdmtmenu.Using RDMT message can be processed,deleted and message dump can be taken manually.

16

Appendix
Reference
RIHA Help Open and Login to RIHA > Help button Hospital Administration User Guide http://download.oracle.com/docs/cd/E12461_01/131/hospital_administration_user_guide/ rib-ha-131-ug.pdf RIB adapter details and the mapping reports (DTD and XSD) present at W deive.

17