To configure the integration service endpoint

1. Go to Settings > System Topology > Map View and right-click the Application Server.

2. In the Edit Settings dialog box, go to Integration Services.

3. In the Edit Settings- Integration Services Endpoint Configuration configure the TCP/HTTPS/HTTP settings for integration services. You should only check the metadata enabled box during development phase. Otherwise, for security reasons, this option should be unchecked. A restart of the application server is required for the configuration to take effect.

   Fill the following details in the Edit Settings- Integration Services Endpoint Configuration dialog box:

   Enabled	Enables the TCP/HTTPS/HTTP protocol if checked. Note: Symantec recommends the use of the HTTPS protocol for all the APIs for better security.
   Metadata Enabled	Enables the metadata if checked. Note: You must select the checkbox, if you want to use the Integration Services APIs over TCP or HTPPS or HTTP binding.
   Port Number	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 ) or netsh (Windows 2008) to rebind the certificate to the new port. On the Windows 2003, use the following command: httpcfg delete ssl -i 0.0.0.0:<install_port> httpcfg set ssl -i 0.0.0.0:<new_port> -c Symantec_Components -h <certificate_thumbprint> -g <guid> On the Windows 2008, use the following command: netsh http delete sslcert ipport=0.0.0.0:<install_port> netsh http add sslcert ipport=0.0.0.0:<new_port> certstorename=Symantec_Components certhash=<certificate_thumbprint> appid=<application_id> The default port for HTTP is 80.
   Transport Name	The field is not editable. The transport name is populated from the Directory Server.
   Enabled	Enables the Windows Security or the Username Security based on how you want to make the API calls. In case of TCP/IP and HTTP, you can only use the Windows Security. In case of HTTPS, you can use either the Windows Security or Username Security.
   BindingFactory	The field is not editable. The transport name is populated from the Directory Server.
   ClientBindingFactory	The field is not editable. The transport name is populated from the Directory Server.
   UriSuffix	The field is not editable. The transport name is populated from the Directory Server.
   Public Transport	Lets you select from the Yes or No options. If you select Yes, only the public APIs are exposed. If you select No, both the public and the internal APIs are exposed.
   Exception Details In Faults	Lets you select from the Yes or No options. If you select Yes, the internal error details that occur on the Server side also are included in Faults.

4. Restart the Symantec Application Server service.

5. Start using the APIs with the sample code that is provided with each API in the API Reference Guide.

   After the ISS endpoint configuration, you must create clients to use the APIs.

   See Creating SPNs for the Application Server and the Directory Support Service.