Make sure that you have set the properties required by your deployment in the

16-26 Oracle Fusion Middleware Developers Guide for Oracle Identity Manager ■ Configuring the .NET Connector Server ■ Configuring Trace Settings ■ Running the .NET Connector Server ■ Installing Multiple Connectors on a .NET Connector Server

16.5.2.1 Installing the .NET Connector Server

The minimum requirements to run a .NET Connector Server are: ■ Microsoft Windows Server 2003 or 2008 ■ Microsoft .NET Framework 3.5 or higher Refer to the particular .NET identity connector documentation to determine if there are additional requirements. To install the .NET Connector Server, execute the ServiceInstall.msi file and follow the instructions displayed in the Installation Wizard. Upon completion of the installation, the Connector Server will be installed as a Windows Service.

16.5.2.2 Configuring the .NET Connector Server

Follow this procedure to configure the .NET Connector Server. Common configurations include port, trace and SSL settings as well as the Connector Server key. 1. Start the Microsoft Services Console. 2. Check to see if the Connector Server is currently running. If yes, stop it. 3. Set the key for the Connector Server using the command prompt. This key is required by any client that connects to this Connector Server. a. Change to the directory in which the Connector Server was installed. By default: \Program Files\Identity Connectors\Connector Server b. Execute the following command: ConnectorServer setkey NEWKEY where NEWKEY is the value for the key. 4. Configure additional properties by inspecting the settings in connectorserver.exe.config. The connectorserver.exe.config file contains information about the Connector Server. The port, SSL configuration and trace settings are most commonly changed. Port and SSL settings are in a tag called AppSettings as follows: add key=connectorserver.port value=8759 add key=connectorserver.usessl value=false add key=connectorserver.certificatestorename value=ConnectorServerSSLCertificate add key=connectorserver.ifaddress value=0.0.0.0 The port can be set by changing the value of connectorserver.port. To use SSL, set the value of connectorserver.usessl to true, and set the value of connectorserver.certifacatestorename to the name of your certificate store. The listening socket can be bound to a particular address, or can be left as 0.0.0.0. For more information about configuring the Connector Server with SSL, see Section 16.5.1.5, Using SSL to Communicate with a Connector Server. For Understanding the Identity Connector Framework 16-27 information on trace setting configurations, see Section 16.5.2.3, Configuring Trace Settings.

16.5.2.3 Configuring Trace Settings

The Connector Server uses the standard .NET trace mechanism. Trace settings are defined in the connectorserver.exe.config configuration file. Example 16–33 illustrates how they are defined. Example 16–33 Defined Trace Settings system.diagnostics trace autoflush=true indentsize=4 listeners remove name=Default add name=myListener type=System.Diagnostics.TextWriterTraceListener initializeData=c:\connectorserver2.log traceOutputOptions=DateTime filter type=System.Diagnostics.EventTypeFilter initializeData=Information add listeners trace system.diagnostics The default settings are a good starting point but you may change these settings as follows. ■ For less tracing, change the filter types initializeData setting to Warning or Error. ■ For more verbose logging, set the value to Verbose or All. Any configuration changes require that the Connector Server be stopped and restarted.

16.5.2.4 Running the .NET Connector Server

The best way to run the .NET Connector Server is as a Windows Service. During installation, the Connector Server is installed as a Windows service. If this is not adequate for your environment, the Connector Server may be installed or uninstalled as a Windows Service by using the install or uninstall arguments at the command prompt. To run the Connector Server interactively, issue the command ConnectorServer run.

16.5.2.5 Installing Multiple Connectors on a .NET Connector Server

To install new identity connectors, change to the directory where the Connector Server was installed, extract the new identity connector ZIP into it, and restart the Connector Server. Caution: The amount of logging performed has a direct effect on the performance of the Connector Servers. Note: For more information about the tracing options, see Microsoft .NET documentation for System.Diagnostics. 16-28 Oracle Fusion Middleware Developers Guide for Oracle Identity Manager