WAS v8.5 > Secure applications > Secure Service integration > Secure service integrationDisable bus security
If we do not require messaging security, we can choose to disable messaging security. Any new buses added after messaging is disabled are not secured.
- Ensure there are no indoubt transactions on the messaging engine because incomplete transactions cannot be recovered after the bus security is disabled. For more information, see Resolve indoubt transactions.
- Stop all servers on which the SIB Service enabled before you disable bus security. This ensures the bus security configuration is applied consistently when the servers are restarted. For more information, see Stop an application server.
Messaging security is enabled by default, providing administrative security for the cell is enabled. However, there might be circumstances when we do not require messaging security, for example on a development system. In this case, we can use the dmgr console to disable messaging security. To re-enable bus security, see Secure buses.
- 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.
Restart the servers. Start an application server provides more information.
Related
Enable client SSL authentication
Administer authorization permissions
Secure messages between messaging buses
Secure access to a foreign bus
Secure links between messaging engines
Controlling which foreign buses can link to your bus
Secure database access
Secure mediations
Reference:
Security components troubleshooting tips
Related information:
Secure buses
Add unique names to the bus authorization policy
Administer permitted transports for a bus