Migrating an existing secure bus to multiple domain security
Use this task to migrate a secured service integration bus from the global security domain to a cell-level or custom security domain.
Before you begin
- Review the information in Service integration security planning and Messaging security and multiple security domains.
- All the bus members must be at WebSphere® Application Server Version 7.0 or later; use of multiple domain security is not supported for earlier versions of the product.
- Ensure that there are no indoubt transactions on the messaging engine because incomplete transactions cannot be recovered after the bus is secured. For more information, see Resolving indoubt transactions.
- Stop all servers on which the SIB Service enabled. This ensures that the bus security configuration is applied consistently when the servers are restarted. For more information, see Stopping an application server.
About this task
- The global security domain which a bus uses by default.
- A cell level security domain which the bus might inherit from the administrative cell.
- A custom domain which might contain security settings that are unique to the bus.