This section describes how to list the available connectors in your deployment, download connector code, install connectors, and register a connector server. It describes the following topics:
For this release, Waveset is shipping connectors for Active Directory and SPML2 resources. For more information about these connectors, see Chapter 58, Active Directory Connector and Chapter 59, SPML Connector.
Login in to Waveset Administrator Interface as an administrator who has the Resource Administrator capability
Select Resources > Resource Type Actions > Configure Managed Resources. The Resource Connectors area lists all the connectors that Waveset currently recognizes.
You can download additional Waveset-supported identity connectors from https://identityconnectors.dev.java.net.
An Waveset-supported Java connector is distributed as one jar file and one ZIP file. To download successfully, you must:
Copy the jar file binary into the WEB-INF/bundles directory of the Waveset web application
Extract the ZIP file into the Waveset web application.
For a more detailed explanation, see Installing a Java Connector.
An Waveset-supported .NET connector is distributed as two ZIP files. You must
Install one zip file under a remote .NET connector server.
Extract the additional ZIP file into the Waveset web application.
For a more detailed explanation, see Installing a .NET Connector.
A Java connector is delivered as one jar file and one ZIP file.
Stop your Waveset web application.
Copy the connector jar file into the WEB-INF/bundles directory of your Waveset web application.
Extract the connector ZIP file into the your Waveset web application directory.
Start your Waveset web application, and follow any additional connector-specific installation notes.
Your newly installed Java connector should now be visible to Waveset. Log in to the Waveset Administrator interface as an Administrator who has the Resource Administrator capability. Select Resources > Resource Type Actions > Configure Managed Resources, and confirm that the new Java connector is listed (associated in the displayed table with the LOCAL connector server).
(Optional) You may be required to import one or more Exchange files before using the new connector.
Success installation of a .NET connector requires these steps:
Note that before you install the .NET zip files, you must install and register a .NET connector server. A connector server manages one or more .NET bundles, and handles requests between Waveset and the .NET bundles. A .NET connector server is roughly analogous to the Waveset gateway. For more information, see
.NET connector bundles are delivered as two ZIP files.
You must install a .NET connector server before installing the .NET executable connector zip file.
To install the .NET connector's executable zip file:
If the connector server is already installed and running, stop the Connector Server service.
Unzip the ZIP file into the connector server installation directory.
Start the Connector Server service. If the connector server is not yet declared in Waveset, see Registering a Connector Server.
Stop your Waveset web application.
Extract the connector ZIP file into the your Waveset web application directory, and restart your Waveset.
Follow any additional connector-specific installation notes.
(Optional) You may be required to import one or more Exchange files before using the new connector.
After following this procedure, the new .NET connector should now be visible to Waveset. To confirm this, log in to the Waveset Administrator Interface as an administrator who has the Resource Administrator capability. Confirm that the .NET connector is listed in the displayed table with the appropriate connector server by checking Resources > Resource Type Actions > Configure Managed Resources.
You install and run a .NET connector server when using a .NET connector from Waveset. A connector server manages one or more .NET bundles, and handles requests between Waveset and the .NET bundles. A .NET connector server is roughly analogous to the Waveset gateway. However, you can easily extend the .NET connector server (to add additional connectors), and it is coded in .NET.
The minimal requirements for a machine that will run a connector server include:
Windows Server 2003 or 2008
.NET 3.5 or later
To install a connector server on a Windows host, refer to the connector server installation notes on https://identityconnectors.dev.java.net. You must record for later use the following information regarding your connector server installation:
Host name or IP address
Connector server port
Connector server key
whether SSL is enabled
See Registering a Connector Server to declare the newly installed connector server within Waveset.
You must declare within Waveset the connection information needed to communicate with each .NET connector server. If this connection information is not correctly declared, then Waveset will not have access to the .NET connectors deployed within the .NET connector server.
Log on to the Waveset as an administrator who has the Resource Administrator capability.
Select Configuration > Connector Servers.
Click New in the Manage Connector Servers Definitions page.
Complete the required fields in the New Connector Server. See the online help for information about each field.
Click Save. Waveset will display “Available” in the Status column for the new Connector Server definition if Waveset can successfully communicate with the remote connector server.