The following sections install, configure, and tests a scenario that provides a round trip between the WebSphere Commerce Server and a simulated back-end.
Use the following steps to install the sample scenario:
CORBA[]
OAPORT=16000
%SAMPLE_FOLDER%/WC_PortConnector.in
repos_copy -iWC_PortConnector.in -s <ICS_Server_Name>.
Use repos_copy to load the business objects contained in the file
%SAMPLE_FOLDER%/WC_BODefinition.in
repos_copy -s<InterChangeServerName> -u<UserName> -p<password> -iWC_BODefinition.in
If the repo is successfully loaded, a confirmation message saying "Repository Loaded" appears.
Use repos_copy to load the template contained in the file
%SAMPLE_FOLDER%/WC_CollabTemplate.in
repos_copy -s<InterChangeServerName> -u<UserName> -p<password> -iWC_CollabTemplate.in.
Copy
%SAMPLE_FOLDER%/CollaborationClasses/*.class
to folder
%CROSSWORLDS%/collaborations/classes/UserCollaborations
Use repos_copy to load the collaborations contained in the file %SAMPLE_FOLDER%/WC_CollabObj.in.
For example, from a command prompt, type:
repos_copy -s<InterChangeServerName> -u<UserName> -p<password> -iWC_CollabObj.in
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
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 |
To use the business objects, the connector must first support them.
Name=MO_WebSphereCommerceConfig
Name=MO_DataHandlerDefault
Name=MO_DataHandlerDefault
Name=WCS_Create_WCS_Customer
Name=WCS_Report_NC_PurchaseOrder
Click the "AgentSupport" checkbox for each object and the PortConnector.
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 |
Reboot the WebSphere InterChange server to instantiate all changes.
If the collaborations and connectors do not start immediately, start them right-click menu and choosing Start.