When you create a new connector, you must specify which Connector Server hosts it. By default, the Java connector server already exists, and new connectors are automatically associated with it.
If for any reason whatsoever, the connector server role has been deleted, you are prompted to create a new one when adding the new connector.
Several connectors, however, require a separate connector server. For example:
• Some connectors must run as a 32-bit process, for example, old versions of the ENOVIA connector. For such cases, you need to deploy a new connector server.
• Some connectors must use C# connector servers, for example the MS SharePoint connector.
Deploy a Connector Server
1. In the Administration Console, go to Deployment > Roles and click Add Roles.
2. In the list of roles, select the Connector Server and click Accept.
3. In the new Connector server box, complete the fields:
◦ Select the Type.
◦ For Instance, enter a unique name. For example, java1.
◦ To run this connector server as a 32-bit process, select 32-bit.
4. Click Apply.
Define the Target Push API Server
Exalead CloudView can use several Push API servers to index data. When adding a connector, you must select the target Push API server that will store its data. Default is Build groupbg0.
1. On the Administration ConsoleHome page, under Connectors, click the connector name.
2. Go to the Deployment tab.
3. For Push to PAPI server, select the appropriate Push API server from the list.
4. Click Apply.
Configure HTTPS
You may need to use HTTPS to secure your connector server.
1. Edit Deployment.xml in <DATADIR>/config.
2. Add the following in the <Role name="ConnectorServer"> section and replace HTTPS_PORT with your HTTPS port: