JNDIUSER Statement—Specify a JNDI User ID

C-LANG Statements › JNDIUSER Statement—Specify a JNDI User ID

JNDIUSER Statement—Specify a JNDI User ID

The JNDIUSER statement specifies the JNDI user ID in an Entity Bean, Session Bean, and JMS job. This user ID refers to the Application Server within the JNDI framework. If specified, this authentication information is supplied when creating the initial context.

Supported Job Types

This statement is optional for the following job types:

Syntax

This statement has the following format:

JNDIUSER userid

userid

Specifies the JNDI user ID to be used to gain access to the connection factory.

Limits: Up to 128 characters; case-sensitive; it cannot contain delimiters (such as spaces)

Notes:

Each user ID requires a corresponding password. The password is encrypted and stored separately from the user ID. For more information on defining passwords and other security requirements, refer to your scheduling manager's documentation.
JUSER is an alias of JNDIUSER.

Example: Specify a JNDI User ID in a JMS Publish Job

This example publishes the message "this is my message" to the queue named Queue. The Java class of the message is String. The initial context factory supplied by the JNDI service provider is com.ibm.websphere.naming.WsnInitialContextFactory. The service provider's URL is iiop://172.24.0.0:2809, where 172.24.0.0 is the IP address of the WebSphere MQ server and 2809 is the ORB port. The job uses the cyberuser JNDI user ID to gain access to the connection factory named ConnectionFactory.

AGENT APPAGENT
INITIAL_CONTEXT com.ibm.websphere.naming.WsnInitialContextFactory
LOCATION iiop://172.24.0.0:2809
CONNECTION_FACTORY ConnectionFactory
DESTNAME Queue
TOPIC N
MSGCLASS String
JNDIUSER cyberuser
PARAMETER TYPE(java.lang.String) VALUE('this is my message')

Note: The agent does not support JMS messaging on IBM WebSphere. If you have IBM WebSphere MQ, your agent administrator can set up the agent plug-in to run JMS Publish and JMS Subscribe for JMS queues. JMS topics are not supported on IBM WebSphere MQ.