Deployment of Universal Messaging Assets
On-Premise Deployment of Assets
You can deploy Universal Messaging assets on-premise, using the Command Central command-line interface. On-premise deployment is based on a push model. For information about the asset deployment commands, see Asset Deployment.
Asset Deployment in the Cloud
For cloud-based deployment, the cloud and container deployments require a pull-model approach for asset deployment.
The pull model is based on Landscape Asset Registry (LAR) and its change listeners. Universal Messaging needs to integrate with the LAR-based update mechanism for deployment of its assets.
Configuration types supported for cloud deployment
The following table lists the configuration types supported for cloud deployment.
| Configuration type | Description |
|---|---|
| JNDI connection factory | On JNDI look-up for the connection
factory, the connection factory URL is set to the value used while building the
JNDI context (java.naming.provider.url)
|
| JNDI destinations | For native messaging, Integration Server creates the
channel or queue as soon as the publishable document type is created. This would
include the protocol buffer definitions. Only JMS destination deployment is
supported for cloud-based deployment as native ones are created by Integration Server. All the JNDI
destinations are exported with the parameter The durables will be created automatically after the Integration Server triggers are started for the first time. |
| Realm ACLs and groups | Basic authentication is enabled by default, and the default ACL setting has full privileges. |
| Common users | Universal Messaging users are migrated, and the users are created (stored in users.txt file) with custom passwords. |