For each Instant Messaging instance in your solution, you must input values that configure the instance to interoperate with the other components in the solution. Use Table 3–13 to help you choose configuration values. For detailed information on the input values, see Chapter 1, “Configuring Instant Messaging after Installation,” in Sun Java System Instant Messaging 7 2005Q1 Administration Guide.
Table 3–13 Key Configuration Values for Instant Messaging
Input Field |
Choosing a Value for Your Solution |
---|---|
Sun Java System Instant Messaging Server, Sun Java System Instant Messaging Resources, Sun Java System Access Manager Instant Messaging Service |
Select the subcomponents specified in the deployment architecture. For more information, see Analyzing a Deployment Architecture and Distributed Subcomponents. |
Runtime User ID, Runtime Group, HTTP Port, Document Root Directory |
Use these fields to specify the Web Server instance in which Instant Messaging client resource runs. |
Are you planning to leverage an Access Managerdeployment for SSO? and Are you planning to leverage an Access Manager deployment for Policy? |
Use these fields to specify how Instant Messaging interacts with Access Manager. |
Domain Name, IM Server Port, Multiplexor Port, Disable Server, Remote IM Host Name |
Domain name is the mail domain that your solution is using. It was established when Messaging Server was configured. For more information, see Table 3–9. |
LDAP Host Name, LDAP Port Number, Base DN, Bind DN, Bind Password |
Specify the Directory Server instance used for user and group data. Bind DN and Bind Password are the directory manager account and password. Base DN is the LDAP organization for Instant Messaging user data. If the solution also includes Messaging Server, Base DN is the email domain LDAP organization created by Messaging Server configuration. For more information see Table 3–9. If your solution uses load-balanced Directory Server instances, type the logical URL for the load-balanced directory service. |
SMTP Server |
Specify the computer running Messaging Server. If your solution uses load-balanced or clustered Messaging Server instances, use the logical URL for the load-balanced messaging service. |
Instant Messenger Resources Codebase |
Specify the location from which users will download Instant Messenger client resources. |
Assign IM Service to Existing Users |