Activation spec optional binding properties
Binding properties that we can specify for activation specifications to be deployed on WAS.
- J2C authentication alias
- If we provide values for user name and password as customer properties on an activation specification, we might not want to have those values exposed in clear text for security reasons. Use WebSphere security to securely define an authentication alias for such cases. Configuration of activation specifications, both as an admin object and during application deployment, enable you to use the authentication alias instead of providing the user name and password.
If we set the authentication alias field, then you should not set the user name and password customer properties fields. Also, authentication alias properties set as part of application deployment take precedence over properties set on an activation spec admin object.
Only the authentication alias is ever written to file in an unencrypted form, even for purposes of transaction recovery logging. The security service is used to protect the real user name and password.
During application startup, when the activation spec is being initialized as part of endpoint activation, the server uses the authentication alias to retrieve the real user name and password from security then set it on the activation spec instance.
- Destination JNDI name
- For resource adapters that support JMS associate javax.jms.Destinations with an activation specification, such that the resource adapter can service messages from the JMS destination. In this case, the administrator configures a J2C Administered Object that implements the javax.jms.Destination interface and binds it into JNDI.
Configure a J2C Administered Object to use an ActivationSpec class that implements a setDestination(javax.jms.Destination) method. In this case, we can specify the destination JNDI name (that is, the JNDI name for the J2C Administered object that implements the javax.jms.Destination).
A destination JNDI name set as part of application deployment take precedence over properties set on an activation spec admin object.
During application startup, when the activation spec is being initialized as part of endpoint activation, the server uses the destination JNDI name to look up the destination administered object then set it on the activation spec instance.
Related concepts
J2C activation spec configuration and use
Message-driven beans - automatic message retrieval