After installing Commerce Enabled Portal on the WebSphere Portal machine, you must configure Commerce Enabled Portal.
Note: In order for Commerce Enabled Portal to work, you must complete installation and configuration on both the WebSphere Commerce node and the WebSphere Portal node. This chapter deals only with configuring Commerce Enabled Portal on WebSphere Portal. For more information on the overall installation and configuration order, see Road map for installing and configuring Commerce Enabled Portal.
Prerequisites
Before configuring Commerce Enabled Portal on WebSphere Portal Server machine, ensure you have completed the following:
- Meet the hardware and software requirements outlined in Pre-installation requirements
- Ensure that the WebSphere Application Server global security is enabled on the WebSphere Portal Server machine.
- Installed Commerce Enabled Portal on your WebSphere Commerce machine.
- Ensure that the Web Server is started on the WebSphere Commerce machine.
- Configured the Commerce Enabled Portal on your WebSphere Commerce machine, which includes working with a WebSphere Commerce instance.
- Installed Commerce Enabled Portal on your WebSphere Portal Server machine.
- Started the database for the WebSphere Portal.
- Created a new SSL certificate for SSL. In order for Commerce Enabled Portal to work properly, you must set up the SSL certificate from the WebSphere Commerce HTTP server to the WebSphere Application Server on the WebSphere Portal machine.
- Ensure that you are logged in as root.
Required IDs and information
You will need the following information to configure Commerce Enabled Portal. You may want to use the table below to record all necessary information before starting the configuration....
Configuring Commerce Enabled Portal on WebSphere Portal
To configure Commerce Enabled Portal on WebSphere Portal, do the following:
- Open the Commerce Enabled Portal Configurator from the command line. Go to the WebSphere Commerce install directory (WC_installdir/bin).
Note: The default values for WC_installdir are available in Path variables.
Run the following command to display the Commerce Enabled Portal Configurator:DISPLAY=host_name:0.0 export DISPLAY configPortalServer.sh
where host_name is the fully qualified host name of the machine from which you want to run the installation wizard.Note: configPortalServer.sh should run as root.
configPortalServer.bat
- Ensure that the NetServer (NETSVR) is started on iSeries, if not, run the following command on iSeries command line:
- STRTCPSVR SERVER(*NETSVR)
- Map the iSeries IFS to your windows machine:
- At a command line, type the following: net use * \\iSerieshostname\qibm /user:userid password
Note: The user ID and password must exists on the target iSeries machine with *secofr authority.
- Change the directory to the mapped iSeries IFS driver: driver:\ProdData\CommerceServer56\bin folder.
- Run configPortalServer.bat.
- At a command line, type the following: net use * \\iSerieshostname\qibm /user:userid password
- Ensure that the NetServer (NETSVR) is started on iSeries, if not, run the following command on iSeries command line:
- The Commerce Enabled Portal Configurator displays. Ensure you have completed the steps listed. Click Next.
- On the Logon page, provide the system name where WebSphere Commerce is installed, a user profile that has *SECOFR authority and the password.
- Do the following:
- In the Administrator user ID field, type the ID (use the short name form of the ID) of the Portal server administrator.
- In the Administrator password field, type the password.
- In the Administrator password verification field, retype the password.
- In the WebSphere Portal Server port field, type the port number for the machine where WebSphere Portal Server is installed. The default port number is 9081.
- Click Next. The Select the Specify WebSphere Portal Server Information (Continued) page displays. This page is for WebSphere Application Server information.
- Do the following:
- In the Administrative Console ID field, type your WebSphere Application Server Administrative Console logon ID (for example, wpsbind).
- In the Administrative Console user password field, type your WebSphere Application Server Administrative Console logon password.
- In the Administrative Console user password verification field, retype the password.
- In the WebSphere Application Server profile name field, type your WebSphere Application Server profile name.
In the WebSphere Application Server profile path field, specify the WebSphere Application Server profile location (for example, /qibm/UserData/WebSphere/AppServer/V6/ND/profiles/profile_name)
- Click Next. The Specify Single Signon Settings page displays.
- Do the following:
- In the Single sign-on domain for WebSphere Application Server security field, type the domain name used for single signon on WebSphere Application Server.
- In the LTPA key password field, type the Lightweight Third Party Authentication password used to encrypt and decrpyt the LTPA key. The LTPA key password must be the same one that you used when you installed Commerce Enabled Portal on your WebSphere Commerce machine.
- In the LTPA key password verification field, retype the password.
- Click Next. The Specify SSL Certificate page displays.
- In the SSL certificate path and file field, type the full path and file name for your SSL certificate, or click Browse and navigate to it. By default this certificate is named cert.arm. When you received this SSL certificate file, you should have copied it to your WebSphere Commerce and WebSphere Portal Server.
- Click Next. The Select the Business Model page displays.
- From the Business model list, select the business model to be used in this instance.
Notes:
- Commerce Enabled Portal supports the consumer direct and B2B direct business models.
- Click Next.
- The Confirm Configuration Settings page displays. Review the information you have selected. If you want to make any changes, click Back until you reach the page with the settings you want to change.
- When you have confirmed your settings, click Next. Your settings will be configured.
- Once the configuration has completed successfully, the Post configuration steps page displays and lists the necessary post-configuration steps. These steps are as follows
- Review the configuration log file. The location of the log file will display on this page.
- Review the information on Publishing stores after configuring Commerce Enabled Portal.
- To verify that your configuration worked correctly, do the following:
- On the WebSphere Portal node, navigate to WC_installdir/logs, where
WC_installdir is the WebSphere Commerce installation directory. - Check the WCPconfig_wps.err.log file for any errors.
- Check the WCPconfig_wps.log file for any errors.
- On the WebSphere Portal node, navigate to WC_installdir/logs, where
Viewing your portal store
After you have configured the Commerce Enabled Portal on your WebSphere Portal Server machine, you should be able to view your portal store. The portal store was published when you configured the Commerce Enabled Portal on WebSphere Commerce, however, it was not fully functional as a portal store until Commerce Enabled Portal was configured on your WebSphere Portal Server machine.
To view your portal store, do the following:
- In a browser, type the following URL: http://hostname:port/wps/portal The WebSphere Portal page displays. The port number is typically 9081.
- Click Log in. The Log in page displays.
- In the User ID field, type your user ID.
- In the Password field, type your password.
- Click Log in.
- You should see a MyStore tab in the header. If you do not see a MyStore tab, click the arrows in the header to scroll through all items in the header.
- Click MyStore to view your store.
Notes:
If you published a B2B Direct sample portal store (ToolTech) you will also see Buyer Organization and Seller Organization tabs. If you are logged on as the administrator you will see all views and the view in the MyStore tab will include all of the portlets for both the Buyer Organization and the Seller Organization tabs.
Publishing stores after configuring Commerce Enabled Portal
Publishing store archives after installing Commerce Enabled Portal: If you choose to publish a starter store after installing and configuring the Commerce Enabled Portal, you must make the following changes before publishing:
- Save a copy of the store archive file.
- Delete all the contents of WC_installdir/Portals/config/work/sar
- Open the store archive file and extract it to the following directory: WC_installdir/Portals/config/work/sar
- In a command window, navigate to the following directory: WC_installdir/Portals/config
- If you are using an Active Directory or Domino LDAP server, type:
WCSconfig.sh action-process-sar-ad-domino.
WCSconfig.bat action-process-sar-ad-domino.
If you are using another LDAP server, type:
WCSconfig.sh action-process-sar-default
WCSconfig.bat action-process-sar-default
- Repackage the store archive as a zip file in the following directory: WC_installdir/Portals/config/work/sar