Running Business Processes and Composite Applications 10.4 | Running Business Processes and Composite Applications | Universal Messaging Administration Guide | Using Command Central to Manage Universal Messaging | Universal Messaging Cloud Transformation | Universal Messaging Integration with LAR
 
Universal Messaging Integration with LAR
The current on-premise asset deployment model uses a push-model which is supported in Deployer and Command Central Deployer API. On cloud-based deployment, the cloud and container deployments require a pull-model approach for asset deployment rather than push-model.
The pull-model is based on Landscape Asset Repository (LAR) and its change listeners. Universal Messaging needs to integrate with the LAR based update mechanism for deployment of its assets.
Configuration types supported on cloud deployment
The following table lists the configuration types supported on cloud deployments:
Configuration type
Description
JNDI connection factory
On JNDI look up for the connection factory, connection factory URL will be 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 autoCreateDest set to true, so that all the channels or queues are created automatically. The newly created channel or queues will have default Universal Messaging configurations. For more information on JNDI destinations, see JNDI Asset Configuration Commands.
The durables will be created automatically after the Integration Server triggers are started for the first time.
Realm ACLs and Groups. The basic authentication is enabled by default and the default ACL setting will have full privileges.
Common Users. The Universal Messaging users are migrated and the users are created (stored in users.txt file) with custom passwords.
Note: If you want to change the instance name, server name or runtime component ID, you have to manually edit the template.yaml file. The template.yaml file is generated by Designer and contains Universal Messaging configuration.
Copyright © 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release