Predefined JMS Connection Aliases
Integration Server includes predefined JMS connection aliases. Integration Server creates the aliases the first time Integration Server starts. If the aliases existed in an Integration Server that was migrated from a previous version, Integration Server keeps the existing aliases. That is, Integration Server does not overwrite the previous alias definition.
Integration Server has the following predefined JMS connection aliases:
JMS Connection Alias | Description |
DEFAULT_IS_JMS
_CONNECTION | A JMS connection alias that defines a connection to Universal Messaging using the predefined JNDI provider alias DEFAULT_IS_JNDI_PROVIDER. Integration Server configures this JMS connection alias when you launch the Integration Server the first time. This connection alias is disabled by default. |
PE_NON
TRANSACTIONAL_
ALIAS | A JMS connection alias for the Process Engine that establishes a connection to Universal Messaging using the predefined JNDI provider alias DEFAULT_IS_JNDI_PROVIDER. Integration Server configures this alias when you launch your Integration Server the first time. Note:Integration Server creates this alias even if the Process Engine is not installed. |
Note:
If you migrated to Integration Server 9.10 or later from an earlier version, you might have the EventBus alias which was a pre-defined JMS connection alias in versions prior to 9.10. This EventBus alias is for the EDA Event Bus server and defines a connection to Universal Messaging using the predefined JNDI provider alias DEFAULT_IS_JNDI_PROVIDER.