This chapter helps you get started with Oracle User Messaging Service (UMS). It discusses how to install and upgrade UMS. It also discusses the procedures needed for achieving high availability and moving from a test to a production environment.
This chapter includes the following sections:
For detailed information about installing and configuring UMS, see Oracle Fusion Middleware Installing and Configuring the Oracle Fusion Middleware Infrastructure. The installation of UMS includes the following main procedures:
Running the Repository Creation Utility (RCU) to create the database schemas
When running the RCU, select User Messaging Service in the list of components. For information about creating the database schemas, see Configuring your Oracle Fusion Middleware Infrastructure Domain in Oracle Fusion Middleware Installing and Configuring the Oracle Fusion Middleware Infrastructure.
Extending your domain using the UMS template
The UMS templates are located at ORACLE_HOME
/oracle_common/common/templates/wls. For more information about UMS templates, see Oracle Fusion Middleware Domain Template Reference. In the WebLogic Server Configuration Wizard, extend the domain using
oracle.ums.basic_template.jar to set up the UMS JDBC properties and target the UMS server along with the chosen drivers to your managed servers or clusters. The Oracle User Messaging Service Basic template is a quick start template that defines the managed server,
ums_server1, and targets all UMS components to that server.
Note:The UMS Client API is packaged in a shared library that an UMS client application must reference. The shared library is available where the UMS Server and the JRF template has been installed. However, when the client application is running on a managed server other than UMS, and uses the UMS Web Services API, and if the JRF template is not used then the client shared library must be deployed explicitly. This can be achieved by extending the domain where the client application is deployed with the UMS Client API template available at
$ORACLE_HOME/common/templates/wls/oracle.ums.client_template.jar.The UMS Client API shared library is called oracle.sdp.client.
For detailed information about upgrading to UMS 12c, see Oracle Fusion Middleware Upgrading to the Oracle Fusion Middleware Infrastructure.
UMS provides a Schema Upgrade plug-in and a Config Upgrade plug-in to the Oracle Fusion Middleware Upgrade Assistant. The config upgrade plug-in handles the change from application level configuration in 11g to domain level configuration in 12c. This includes copying the application configuration from remote managed servers to the Administration Server and merging it into the UMS domain level configuration file. For more information, refer to Appendix A, "Upgrading User Messaging Service from 11g to 12c". For information about upgrading from 11g to 12c using Upgrade Assistant, see Oracle Fusion Middleware Upgrading with the Upgrade Assistant.
You can achieve a highly scalable environment for UMS. To achieve high scalability, UMS scales horizontally by adding new identically configured nodes. This means, the same type of drivers and UMS applications are deployed on each node. This gives UMS linear scalability up to the point where the scalability of JMS or the scalability of data storage becomes the limiting factor.
Since the WS-UMS Server application component is deployed on the UMS node, it scales the same way as UMS does. On the other hand, since the WS-UMS Client application is deployed on separate machines, the scalability is up to the design of that component.
UMS supports the following deployment scenarios for scaling up your environment:
Instances of UMS deployed in a domain are configured identical and deployed identical. No limitation on the number of servers or how the domain/clusters are set up.
Instances of UMS deployed in a domain that have different configuration (server and/or driver) must be deployed in separate clusters.
For detailed information about scaling up your environment, see Oracle Fusion Middleware Administering Oracle Fusion Middleware.
Whole Server Migration is a key High Availability feature that UMS supports. For more information about Whole Server Migration, see Oracle Fusion Middleware Administering Clusters for Oracle WebLogic Server.
High availability for UMS can be achieved through the following ways:
Automatic reconnects to external gateways
Message resends and failover chains
Persistence layer recovery handling database connections problems
For detailed information about high availability, see Oracle Fusion Middleware High Availability Guide.
This framework eases the moving of Oracle Fusion Middleware components from a test environment to a production environment. For details about the procedures used for moving Oracle Fusion Middleware from a test environment to a production environment, see Oracle Fusion Middleware Administering Oracle Fusion Middleware.
Most configuration in a test environment is handled automatically by this framework. Components that require custom actions implement these in the T2P plug-ins. UMS provides a T2P plug-in to this framework. Some User Preferences data is stored in a database and requires the T2P plug-in to move that data from a test database to a production database. Also, the T2P plug-in extracts preselected driver configuration properties, like host names and ports to the
moveplan.xml file so that the settings can be prepared for the production environment before the production system is started.
For detailed information about moving from a test to a production environment, see Oracle Fusion Middleware Administering Oracle Fusion Middleware.