You can change the authentication type for storing the security settings.
To configure the Application Server settings
Go to Settings > System Topology.
Do one of the following:
In the System Topology > Grid View, right-click the Application Server component and click Edit Settings.
In the System Topology > Map View, right-click the Application Server component and click Edit Settings.
In the Edit Settings dialog box, click Application Server.
On the Application Server - Basic panel, select one of the following authentication types:
Use controlled delegation of security rights
Select this option if you want to use the Constrained Delegation feature of Windows 2003.
Use Control Compliance Suite to store the password
Select this option if you want to use the built-in storage to store the encrypted password.
On the Application Server - Integration Services panel, provide the following information:
Lets you select the algorithm suite that you want the bridge manager to use. The default algorithm suite for TCP, HTTPS, and HTTP is Basic256. You can also configure the algorithm suite for the following communication layers:
TCP/IP (HTTP, Windows Security)
WS_HTTP (Windows Security)
WS_HTTP over SSL (HTTPS, Windows Security)
WS_HTTP over SSL (HTTPS, Username Security)
Basic HTTP over SSL (HTTPS, Username Security)
The default algorithm suite for the mentioned communication layers is set to Inherited. If you retain the default value, the communication layers inherit the algorithm suite that you select for the bridge manager. However, if you select a different algorithm for the communication layers, then the algorithm selection for the bridge manager is overridden.
Enables the TCP/HTTPS/HTTP protocol if checked.
The field is not editable for the TCP.
Enables the metadata if checked.
You must select the checkbox, if you want to use the Integration Services APIs over TCP or HTTPS or HTTP binding.
Lets you type the port number.
The default port for TCP is 1431.
The default port for HTTPS is 12431.
If you change the port number for the HTTPs, you must use the httpcfg (Windows 2003 support tools) or netsh (Windows 2008) to rebind the certificate to the new port.