Network Deployment (Distributed operating systems), v8.0 > Secure applications and their environment > Secure Service integration > Secure service integration
Disable bus security
If you do not require messaging security, you can choose to disable messaging security. Any new buses added after messaging is disabled are not secured.
Messaging security is enabled by default, providing administrative security for the cell is enabled. However, there might be circumstances when you do not require messaging security, for example on a development system. In this case, you can use the admin console to disable messaging security. To re-enable bus security, see Secure buses.
- Ensure that there are no indoubt transactions on the messaging engine because incomplete transactions cannot be recovered after the bus security is disabled. See Resolve indoubt transactions.
- Stop all servers on which the SIB Service enabled before you disable bus security. This ensures that the bus security configuration is applied consistently when the servers are restarted. See Stop an application server.
Procedure
- In the navigation pane, click Service integration -> Buses . A list of buses is displayed.
- Find the bus for which to disable security, and click Enabled in the security column. The security settings for the selected bus are displayed.
- Clear the check box Enable bus security.
- Click Apply.
- Save your changes to the master configuration.
Results
You have disabled security for the selected bus.
What to do next
We must propagate the bus security configuration to all the affected nodes, and restart the servers. See Synchronize nodes using wsadmin.sh and Start an application server.
Related
Security components troubleshooting tips