In this lesson, you create a message type for this tutorial
and configure the new message type to point to the sample web service.
Procedure
- Add the new message type to WebSphere Commerce by running
the following SQL statement:
- INSERT INTO MSGTYPES (MSGTYPE_ID, MSGTDIR, NAME, VIEWNAME,
DESCRIPTION) VALUES (1999, 1, 'com.mycompany.commerce.member', '',
'Member PushUser Customization');
- Start or restart the WebSphere Commerce Test Server.
- Activate the web services over HTTP transport.
- Open the WebSphere Commerce Admin Console and logon
to the site.
- Select .
- Select Web services over HTTP.
- Click Change Status.
- Configure the Member PushUser Customization message type.
- Open the WebSphere Commerce Admin Console.
- Select .
- Click New.
- Enter the following information for the message type:
- Select com.mycompany.commerce.member from
the Message Type drop-down list.
- Transport: Web services over (HTTP).
- Device format: webservices
- Click Next.
- URL: http://localhost:81/MyCompanyMemberServices/MyCompanyMemberServices
- If required, enter the user name and password
for use in the service requests.
- Click Finish.
- Add the component invocation file to the WebSphere Commerce
Development server:
- Create the directory WC_eardir\xml\config\com.mycompany.commerce.member-ext
- In the com.mycompany.commerce.member-ext directory,
right-click and select . Name the file SDO.properties
- Open the file for editing. Add the following code to
the file:
#-----------------------------------------------------------------
# Licensed Materials - Property of IBM
#
# WebSphere Commerce
#
# (C) Copyright IBM Corp. 2011 All Rights Reserved.
#
# US Government Users Restricted Rights - Use, duplication or
# disclosure restricted by GSA ADP Schedule Contract with
# IBM Corp.
#-----------------------------------------------------------------
com.mycompany.commerce.member.facade.datatypes.impl.MemberPackageImpl
- Save and close the file.
- In the com.mycompany.commerce.member-ext directory,
right-click and select . Name the file wc-component-client.xml
- Open the file for editing. Add the following code to
the file:
<?xml version="1.0" encoding="UTF-8"?>
<!--
=================================================================
Licensed Materials - Property of IBM
WebSphere Commerce
(C) Copyright IBM Corp. 2011 All Rights Reserved.
US Government Users Restricted Rights - Use, duplication or
disclosure restricted by GSA ADP Schedule Contract with
IBM Corp.
=================================================================
-->
<_config:DevelopmentClientConfiguration xmlns:_config="http://www.ibm.com/xmlns/prod/commerce/foundation/config"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.ibm.com/xmlns/prod/commerce/foundation/config ../xsd/wc-component-client.xsd">
<_config:invocationservice>
<_config:invocationbinding
bindingImpl="com.ibm.commerce.foundation.internal.client.services.invocation.impl.JCAInvocationBindingImpl">
</_config:invocationbinding>
<_config:action name="CreateUser" asynchronous="false">
</_config:action>
<_config:action name="UpdateUser" asynchronous="false">
</_config:action>
</_config:invocationservice>
</_config:DevelopmentClientConfiguration>
- Save and close the file.
- Restart the WebSphere Commerce Server.
What to do next
After you complete these steps, the WebSphere Commerce
messaging system is configured. The next step is to generate the sample
MyCompanyMember member management system.