Installing and configuring

In the sections that follow, WBI_folder refers to the folder containing your current WebSphere ICS installation. All environment variables and file separators are specified in the Windows 2000 or 2003 format. Please make the appropriate changes if running on AIX or Solaris. (for example, WBI_folder\connectors would be WBI_folder/connectors).

Start server and tool

  1. Start WebSphere InterChange Server (ICS) from the shortcut.
  2. Start the WebSphere Business Integration System Manager and open the Component Navigator Perspective.
  3. Register and connect your server as a Server Instance in the Interchange Server view.

Load the sample content

From the Component Navigator Perspective:

  1. Create a new Integration Component Library.
  2. Import the repos file named HTTPSample.jar located in: WBI_folder\connectors\HTTP\samples\WebSphereICS\

Compile the collaboration templates

Using WebSphere Business Integration System Manager:

Configure the connector

  1. If you have not done so already, configure the connector as described in this guide and according to your system.
  2. Using WebSphere Business Integration System Manager, open HTTPConnector in Connector Configurator.
  3. You must also configure HTTPConnector for the protocol you want to use with the sample:

Configuring for the HTTP protocol scenario

This section shows you how to configure the connector for the HTTP sample scenario. As described in the body of this document, the connector includes an HTTP protocol listener and HTTP-HTTPS protocol handler.

In the steps and descriptions that follow, hierarchical connector configuration properties are represented with the -> symbol. For example, A-> B implies A is a hierarchical property, and B is child property of A.

To configure the HTTP protocol listener for this sample:

  1. In Connector Configurator, click on Connector-Specific Properties for the HTTPConnector.
  2. Expand the ProtocolListenerFramework property to display the ProtocolListeners child property.
  3. Expand the ProtocolListeners child property to display the HTTPListener1 child property.
  4. Check the value of HTTPListener1->Host and HTTPListener1->Port properties. Make sure there is no other process running on your host and listening on this TCP/IP port. Optionally, you may want to set the value of HTTPListener1->Host to the machine name on which you will run the connector.

You do not need to configure the HTTP-HTTPS protocol handler for the sample; however, to enable SSL functionality (samples are pre-bundled with SSL dependent components), refer to Configuring for the HTTPS protocol scenario.

Configuring for the HTTPS protocol scenario

This section shows you how to configure the connector for the HTTPS sample scenario. The connector includes an HTTPS protocol listener and HTTP-HTTPS protocol handler.

In the steps and descriptions that follow, hierarchical connector configuration properties are represented with the -> symbol. For example, A-> B implies A is a hierarchical property, and B is child property of A.

Note:
In addition to the pre-install items listed above inBefore you start, you should also have created and tested your keystore and truststore using your Key and Certificate management software.
Configure SSL connector-specific properties

For HTTPS, the connector requires that you configure the SSL connector-specific hierarchical property.

  1. In Connector Configurator, click on the Connector-Specific Properties tab for the HTTPConnector.
  2. Expand the SSL hierarchical property to view all of its children properties. Additionally, check or change the following child properties of the hierarchical SSL connector-specific property.

Note:
Do not forget to save the changes in Connector Configurator.
Configure the HTTPS protocol listener

  1. In Connector Configurator, click on Connector-Specific Properties for the HTTPConnector.
  2. Expand the ProtocolListenerFramework property to display the ProtocolListeners child property.
  3. Expand the ProtocolListeners child property to display the HTTPSListener1 child property. Check the value of the HTTPSListener1->Host and HTTPSListener1->Port properties. Make sure no other processes are running on your host and listening on this TCP/IP port. Optionally, you may want to set the value of HTTPSListener1->Host to the machine name on which you are running the connector.

You need not configure the HTTP-HTTPS protocol handler for the sample.

Setting up KeyStore and TrustStore

You can quickly set up KeyStore and TrustStore to use with the sample scenario. For production systems, you must use third-party software for to set up and manage keystores as well as certificate and key generation. No tool is provided as part of the Adapter for HTTP to set up and manage these resources.

This section assumes that Java Virtual Machine is installed on your system and that you are familiar with the keytool shipped with your JVM (Java Virtual Machine). For more information or for troubleshooting problems with the keytool, please see the documentation that accompanies your JVM.

To set up KeyStore:

  1. You create KeyStore using keytool. You must create a key pair in the KeyStore. To do so, enter the following at the command line:
    keytool -genkey -alias httpadapter -keystore c:\security\keystore
  2. keytool immediately prompts for a password. Specify the password that you entered for the value of SSL->KeyStorePassword connector property.

    Note that in the above example if you specified -keystore c:\security\keystore in the command line, you would enter c:\security\keystore as the value of the SSL->KeyStore property. Also, if you specified -alias httpadapter in the command line, you would enter httpadapter as the value of the SSL->KeyStoreAlias connector property. keytool would then prompt you for the details of the certificate. The following illustrates what you may enter at each of the prompts, but is an example only: always refer, and defer, to keytool documentation.
    What is your first and last name?
         [Unknown]:  HostName
    What is the name of your organizational unit?
         [Unknown]:  myunit
    What is the name of your organization?
         [Unknown]:  myorganization
    What is the name of your City or Locality?
         [Unknown]:  mycity
    What is the name of your State or Province?
         [Unknown]:  mystate
    What is the two-letter country code for this unit?
         [Unknown]:  mycountryIs <CN=HostName, OU=myunit, O=myorganization, 
         L=mycity, ST=mystate, C=mycountry> correct?
         [no]:  yes
  3. Note that for What is your first and last name?, you should enter the name of the machine on which you are running the connector. keytool then prompts you:
    Enter key password for <httpadapter> (RETURN if same as keystore password):
  4. Press Return to use the same password. If you want to use a self-signed certificate, you may want to export the certificate created above. To do so, enter following on the command line:
    C:\security>keytool -export -alias httpadapter -keystore c:\security\keystore 
    -file c:\security\httpadapter.cer
  5. keytool now prompts for the keystore password. Enter the password that you entered above

To set up TrustStore:

  1. To import the trusted certificates into the TrustStore, enter the following command:
    keytool -import -alias trusted1 -keystore c:\security\truststore 
    -file c:\security\httpadapter.cer
  2. keytool now prompts for the keystore password. If you entered -keystore c:\security\truststore, make sure that SSL->TrustStore property is set to c:\security\truststore. Also, set the value of the SSL->TrustStorePassword property to the password you entered above.

Create user project

Add and deploy the project

  1. From the Server Instance view, add the User Project created in Create user projectto WebSphere ICS
  2. Deploy all of the components from this User Project to the ICS.

Reboot ICS

  1. Reboot ICS to ensure that all changes take effect.
  2. Use the System Monitor tool to ensure that all of the collaboration objects, connector controllers, and maps are in a green state.

Copyright IBM Corporation 2003, 2005. All Rights Reserved.