Installing the sample scenario

The following sections install, configure, and tests a scenario that provides a round trip between the WebSphere Commerce Server and a simulated back-end.

Note:
References to %SAMPLE_FOLDER% maps to \connectors\WebSphereCommerce\Samples. %CROSSWORLDS% maps to the folder containing the IBM WebSphere InterChange Server installation.

Use the following steps to install the sample scenario:

  1. Create a persistent IOR file.
  2. Check the port connector
  3. Load the business objects into the repository.

    Use repos_copy to load the business objects contained in the file

    %SAMPLE_FOLDER%/WC_BODefinition.in
     
    
  4. Load the template definition into the repository.

    Use repos_copy to load the template contained in the file

    %SAMPLE_FOLDER%/WC_CollabTemplate.in
     
    
  5. Add the template class file.

    Copy

    %SAMPLE_FOLDER%/CollaborationClasses/*.class
     
    

    to folder

    %CROSSWORLDS%/collaborations/classes/UserCollaborations
     
    
  6. Load the collaborations into the repository.

    Use repos_copy to load the collaborations contained in the file %SAMPLE_FOLDER%/WC_CollabObj.in.

    Note:
    You MUST load the template file before loading the collaborations.

    For example, from a command prompt, type:

    repos_copy -s<InterChangeServerName> -u<UserName> 
     -p<password> -iWC_CollabObj.in
     
    
  7. Load the IBM WebSphere Commerce configuration static meta object.

    Use repos_copy to load the collaborations contained in the file %SAMPLE_FOLDER%/MO_WebSphereCommerceConfig.in

    For example, from a command prompt, type:

    repos_copy -s<InterChangeServerName> -u<UserName> 
     -p<password> -iMO_WebSphereCommerceConfig.in
     
    
  8. Configure the connector

    Open System Manager and examine the WebSphereCommerceConnector by double-clicking the "WebSphere Commerce" connector. If you have not done so already, configure the connector as described in the installation guide. Also check and/or change the following connector properties to match the following values.

    Table 19. Configuration properties

    Property Value
    ConfigurationMetaObject MO_WebSphereCommerceConfig
    DataHandlerConfigMO MO_DataHandlerDefault
    DataHandlerMimeType text/xml
    ErrorQueue queue://<queue manager name>/WC_MQCONN.ERROR
    InProgressQueue queue://<queue manager name>/WC_MQCONN.IN_PROGRESS
    ReplyToQueue queue://<queue manager name>/WC_MQCONN.IN_REPLY
    ArchiveQueue queue://<queue manager name>/WC_MQCONN.ARCHIVE
    InputQueue queue://<queue manager name>/WCS_OUTBOUND
    UnsubscribedQueue queue://<queue manager name>/WC_MQCONN.UNSUBSCRIBE
    Hostname Hostname of the computer running WebSphere MQ
    Channel Channel configured for the Queue Manager. Default value is CHANNEL1
  9. Enable support for business objects

    To use the business objects, the connector must first support them.

  10. Ensure app-specific business object support in MO_WebSphereCommerceConfig

    The application specific attributes representing the business objects in MO_WebSphereCommmerceConfig must point to the right output queues. In this scenario, the attribute "WCS_Create_WCS_Customer" should have the following application specific value,

    queue://<queue manager name>/WCS_Serial_Inboud?targetClient=1;OutputFormat=MQSTR
     
    
  11. Restart the WebSphere InterChange Server

    Reboot the WebSphere InterChange server to instantiate all changes.

  12. Start the collaborations and the connector.

    If the collaborations and connectors do not start immediately, start them right-click menu and choosing Start.

Copyright IBM Corp. 1997, 2003