Software AG Products 10.7 | Integrating On-Premises and Cloud Applications | Universal Messaging | Using Command Central to Manage Universal Messaging | Using the Command Line to Manage Universal Messaging | JNDI Destinations Configuration
 
JNDI Destinations Configuration
 
Create Destinations
Get Destination Data
Delete Destinations
Create Destinations
Creates a JNDI destination for a Universal Messaging server instance. You can create topic and queue destinations.
Important:
Updating a JNDI destination, using the command-line interface, is not supported.
Syntax
sagcc create configuration data nodeAlias Universal-Messaging-instanceName
UM-JNDI-DEST {--input|-i} file.xml
Arguments and Options
nodeAlias
Required. The alias name of the installation in which the Universal Messaging server instance is installed.
Universal-Messaging-instanceName
Required. The ID of the Universal Messaging server instance for which you want to create a JNDI destination.
UM-JNDI-DEST
Required. The ID of the configuration type of which you want to create an instance.
--input|-i file.xml
Required. The absolute path to the XML file that contains configuration information about the destination.
Usage Notes
*The input XML file must have the following format:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<destination>
<name>destination_name</name>
<type>destination_type</type>
<storeName>jms_channel_or_queue_name</storeName>
<autoCreateDest>true|false</autoCreateDest>
</destination>
The name parameter can include upper-case and lower-case alphabetic characters, digits (0-9), a double colon (::), slash (/), and periods (.), for example, destination1. Use a double colon (::) to specify a nested namespace, for example, destination1::destination2. A combination of special characters is not allowed, for example, destination1::destination2/destination3.
The storeName parameter can include upper-case and lower-case alphabetic characters, digits (0-9), a double colon (::), slash (/), and underscores (_), but cannot include periods (.).
*Creating a JNDI connection factory and JNDI destination with the same name is not allowed for a Universal Messaging server instance.
Examples
To create a destination for the server instance with ID "Universal-Messaging-umserver" that is installed in the installation with alias name "sag01", using the "destination.xml" file:
sagcc create configuration data sag01 Universal-Messaging-umserver
UM-JNDI-DEST -i C:\jndi\destination.xml
The XML file contains the following parameters:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<destination>
<name>destination1</name>
<type>Topic</type>
<storeName>topic1</storeName>
<autoCreateDest>true</autoCreateDest>
</destination>