The machine on which you are running JMSAdmin must be equipped with the appropriate classes for your JNDI provider.

JMSAdmin must have read and write authorization to the JNDI or LDAP store on the JNDI or LDAP server.

JMSAdmin must have administrator permissions; that is, the application must have Broker administrator permissions (that is, belong to the admin client group; for more information, see Administering webMethods Broker).

If you are using an LDAP server, that server must have the Java object schema installed or be running with schema validation turned off.

If you are using webMethods Broker as a JMS provider with a JNDI properties file, that file must exist containing the properties necessary to establish a connection with your JNDI provider.

If you will be executing commands that create structures on the Broker, the machine running JMSAdmin must have Broker access.

If your Broker Server is enabled with the basic authentication mechanism, a client identity (username and password for basic authentication) is required to access the Broker Server. In addition, the client identity must match an Access Control List (ACL) that permits administrative access to the Broker Server.

If your Broker Server is SSL-enabled, the client on which JMSAdmin is installed must have a valid digital certificate in a keystore, trust store, and password. In addition, the client identity (distinguished name and authenticator's distinguished name) must match an Access Control List (ACL) that permits administrative access to the Broker.