Example: Enabling and disabling global security with a profile

The securityon procedure is available by default so that you can enable global security using a LocalOS registry as the repository of users. You can use other registries with global security, including Lightweight Directory Access Protocol (LDAP) and custom user registries. The LocalOS registry is the easiest to configure, but can only be used in a single node environment, with the exception of z/OS and Windows domain controllers. To send secure requests from one node to another, consider configuring a centralized registry such as LDAP or custom user registries.

You can use the securityoff procedure to disable security for any registry type. Use this procedure to recover from problems configuring and enabling security.


Related concepts
Lightweight Directory Access Protocol
Related reference
Custom user registries



Searchable topic ID:   rxml_enabledisable
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/ae/rxml_enabledisable.html

Library | Support | Terms of Use | Feedback