Before completing the configuration of your WebSphere Portal machine, you must install
the WebSphere Commerce MVCPortlet application. The MVCPortlet application is an implementation of
the MVC pattern that allows WebSphere Portal administrators to set up one or more portlets, each
with its own configuration, to call various WebSphere Commerce services.
Before you begin
- Ensure that you have completed the following task
Procedure
-
Copy the MVCPortlet.war file from the WebSphere Commerce machine, to a temporary directory on
the machine that you use to access the WebSphere Portal administration console. The default location
of the MVCPortlet.war file is:
- WC_installdir/portal/MVCPortlet/MVCPortlet.war
- WCDE_installdir/portal/MVCPortlet/MVCPortlet.war
-
Because the WebSphere Commerce and WebSphere Portal integration environment involves more than
one cluster, it is necessary to install the MVCPortlet application using Deployment Manager
integrated solutions console. See Deploying portlets common to a cluster for more
information.
The following points should be considered while performing this task:
-
Ensure to map the MVCPortlet application to the Portal cluster.
-
Once the installation is successful and synchronize with all cluster members, move to the
WebSphere Portal server primary node and activate the MVCPortlet application. A sample XMLAccess
script for portlet activation can be found in the
scripts/PublishPortletApplication.xml directory in the MVCPortlet.war file. You
can execute this script either from the command line or through the Portal Administration Console.
Instructions on how to execute this script can be found inside of the script file.
-
From the WebSphere Portal primary node, execute the scripts/DefineWebServiceClientBinding.jacl
JACL script to update the WebSphere Commerce service client bindings for the MVCPortlet
application.
The syntax for executing this script from the command line
is:
wp_profile/bin/wsadmin options -f DefineWebServiceClientBinding.jacl parameters
Where
its command line options are:
- conntype SOAP.
- host hostname where hostname is the fully qualified
hostname of the deployment manager.
- port port where port is the SOAP port of the deployment
manager configuration service.
- user username where username is the WebSphere Application
Server administrative user of the deployment manager.
- password pwd where pwd is the password of this WebSphere
Application Server administrative user.
Its parameters are:
- applicationName
- The name of the portlet application EAR.
- moduleName
- The name of the portlet Web application.
- CommerceHostname
- The fully qualified hostname of the WebSphere Commerce server.
- CommercePort
- The port number for the WebSphere Commerce service end points.
For example, for clustered production
environment:
wsadmin.bat -conntype SOAP -host manager.somedomain.com -port 8879 -user dmuser -password dmpassword
-f <wp_profile_root>\installedApps\cell_name\MVCPortlet_war.ear\MVCPortlet.war\scripts\DefineWebServiceClientBinding.jacl
MVCPortlet_war MVCPortlet.war commerce.somedomain.com 8007
For example, for development environment if you want to redirect all BOD messages to the TCP
monitor that runs on port 81:
wsadmin.bat -conntype SOAP -host localhost -port 10025 -user wasuser -password waspassword
-f DefineWebServiceClientBinding.jacl MVCPortlet_war MVCPortlet.war localhost 81
-
From the WebSphere Portal primary node, run the following task to activate the deployed
portlets and to synchronize the changes across all cluster members: