1. Enable basic authentication on Broker Server by setting a user directory system and configuring the authentication mechanism in the basic authentication configuration file. For information about how to enable basic authentication on a Broker Server, see Enabling Basic Authentication.

2. Configure basic authentication identity (user name and password) for a Broker Server. Broker Server uses this identity to identify itself to other Brokers in a territory or cluster, or to a Broker at the other end of a gateway. For information about configuring the basic authentication identity for a Broker Server, see Configuring Basic Authentication Identity for a Broker Server .

3. Configure basic authentication identity for the Broker user interface component to administer an ACL protected Broker Server. For information, see Configuring a Basic Authentication Identity for the Broker User Interface Component.

4. Assign ACLs to the Broker Server so that only authorized users can access its administrative functions, such as viewing Broker Server's identity, creating Brokers, enabling basic authentication, stopping the Broker Server, re-configuring Brokers, and disabling basic authentication. You need to set the administrator identity for the client. For more information, see Broker Server ACLs.

5. Assign ACLs to client groups, territories, clusters, and gateways. For more information, see Client Group ACLs, Territory ACLs, Cluster ACLs, Territory Gateway ACLs, and Cluster Gateway ACLs.

6. Configure basic authentication identity for Java clients, JMS clients, C clients, C# clients, or other Broker Servers to connect to an ACL protected Broker Server. For information, see Managing Clients, webMethods Broker Administration Java API Programmer’s Guide, webMethods Broker Client Java API Programmer’s Guide, webMethods Broker Messaging Programmer’s Guide, and webMethods Broker Client C API Programmer’s Guide.