Description of illustration rms_oci_physical_model.png

This image shows the physical model of an RMS implementation on Oracle Cloud Infrastructure.

The main body of the image shows a box representing a corporate date center, with outputs to a number of enterprise retail systems, themselves represented by small boxes. These systems are:

Store systems, such as PoS TLOG distribution systems Supply chain management systems Supplier systems, Financial systems, Banking systems, Science and planning systems, Miscellaneous external systems.

Within the corporate date center are the components that comprise the center, with unidirectional and bidirectional arrows describing the connections between these components and the external systems. The unidirectional arrows have a single arrowhead, the bidirectional arrows have an arrowhead at both ends.

The components illustrated are:

Mirror backup and disk array storage. The disk array storage contains a file system comprising executables, scripts, I/O data, and so on RMS operational database storage, which is annotated to advise that it can also house DB objects and date for RTM, RPM, ReSA, ReIM, allocation, and OID, when ORW is sued. RIB error hospitale database storage. These components are connected bidirectionally by optical fiber channels to both the database batch server and a database wallet. These components will be described later.

The database batch server contains an optional C compiler along with batches for Pro*C (for RMS, ReSA, and RTM), Sql and PVSql (for RMS), RFX (for RETL), RETL (for RMS), Sql Loader, and RETL (for Allocation). The database batch server is fed by a Scheduler server unidirectionally, via LAN.

The Scheduler server contains a database instance and a scheduling application. It also feeds, again unidirectionally, via LAN, an Application Batch Server. This server contains batches for RPM Java, ReIM Java, and Allocation Java. Both the database batch server and the application batch server are connected bidirectionally, via optical fiber channels, to the database wallet.

The application batch server is also connected bidirectionally to another disk array storage component and its mirror backup. This disk array storage communicates bidirectionally to a calculation server that uses the Allocation Calc engine.

The aforementioned database wallet contains a RAC-enabled database server comprising an RMS Oracle database instance and Oracle clusterware. In addition to the previous mentioned connections, the database wallet is also connected for database connections unidirectionally, via optical fiber channels to a RAC-enabled database server and bidirectionally to the aforementioned calculation server. Finally, it is connected bidirectionally to a WebLogic Server.

This WebLogic Server contains an SOA component that uses an Apache HTTP server and a WebLogic component comprising these features: RMS/RTI UI CS Wallet ReIM Java UI RPM Jave UI ReSA Java UI Allocation Java UI Two RIB-RMS Adapters Two RSL-RMS components. The WebLogic Server is connected bidirectionally to the PC client's web browser through a web load balancer.

Finally, there are a collection of Non-MOM components with their own interconnections. These components are: The application batch server, comprising a SIM Java batch, which is connected bidirectionally to a non-MOM disk array storage (which has a mirror backup). An assortment planning application server RPAS application servers A JMS server for RIB, which is also connected bidirectionally by optical fiber channels to the WebLogic server described earlier. Components labeled RA, comprising an RA MDL, and RWMS, comprising an RWMS MDL. The RWMS component is bidirectionally connected to the A JMS server for RIB. All of the non-MOM components except the application batch server are connected bidirectionally to the previously described databas ebatch server. The application batch server is connected over a LAN to the Scheduler Server.