To configure Commerce Enabled Portal, stop WebSphere Commerce server and Payment server and 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.
Open the setenv.sh file. Ensure the variable DBUSERHOME is pointing to the database user's home directory.
Note:
If you are using Oracle with WebSphere Commerce and the Oracle user is set up to use ksh and the Oracle .profile contains any one line export statements such as export ORACLE_BASE=/opt/oracle/u01/app/oracle, you must change the export statement to use two line statements that set the variable first before exporting it:
ORACLE_BASE=/opt/oracle/u01/app/oracle
export ORACLE_BASE
- Run the following command to display the Commerce Enabled Portal configurator:
DISPLAY=host_name:0.0 export DISPLAY configCommerce.sh
where host_name is the fully qualified host name of the machine from which you want to run the installation wizard.Note:configCommerce.sh should run as root.configCommerce.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\CommerceServer60\bin folder.
- Run configCommerce.bat.
- At a command line, type the following: net use * \\iSerieshostname\qibm /user:userid password
- 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.
- The Specify WebSphere Commerce Information page displays. Do the following:
- In the Instance name field, type the name of the existing WebSphere Commerce instance.
- In the Site Administrator ID field, type the logon ID for the WebSphere Commerce Site Administrator. This ID was created when you installed WebSphere Commerce and created a WebSphere Commerce instance.
- In the Site Administrator password field, type the password for the WebSphere Commerce Site Administrator.
- In the Site Administrator password verification field, retype the password for the WebSphere Commerce Site Administrator.
- From the Business model list, select the business model to be used in this instance.
Notes:
- As part of configuring your settings, WebSphere Commerce will also publish the portal starter store archive that corresponds to the business model you select. For example if you select the consumer direct business model, the consumer direct portal starter store archive will be published, creating a running store when configuration is complete.
- It is recommended that you only configure one store type per instance for use with Commerce Enabled Portal. If you plan to use more than one store type, it is recommended that you create and configure another instance for each additional store type.
- Commerce Enabled Portal supports the consumer direct and
B2B direct business models.
- Click Next. The Specify LDAP Settings page displays.
- Do the following:
- From the LDAP type list, select the type of LDAP. You have the following options:
- IBM Directory Server
- IBM Lotus Domino
- Microsoft Windows 2000 Active Directory
- Sun ONE Directory Server
- In the LDAP host name field, type the fully qualified host name of the LDAP server machine.
- In the LDAP port field, type the port number of the LDAP server. The default LDAP port is 389 for non-SSL ports and 636 for SSL ports.
- In the Base distinguished name field, type the suffix of the distinguished name of the base. For example, dc=ibm, dc=com
- In the Administrator distinguished name field, type the distinguished name of the LDAP server administrator. For example, cn=root.
- In the Administrator password field, type the password.
- In the Administrator password verification field, retype the password.
- Select the LDAP is SSL enabled check box if secure socket communication is enabled on the LDAP server. When enabled, the LDAP Secure Socket Layer settings are used.
- From the LDAP type list, select the type of LDAP. You have the following options:
- Click Next. The Enable WebSphere Application Server Global Security Setting page displays.
- Do the following:
- In the Security user ID field, type the ID that you will use for the security user. This user ID is used to access the WebSphere Application Server Administration Console when security is enabled. This user ID should also be a user ID on the LDAP server.
Note: Use the full distinguished name for the security user ID. It is recommended that you use the WPSBIND ID, uid=wpsbind,cn=users,dc=ibm,dc=com.
- In the Security password field, type the corresponding password.
- In the Security user password verification field, retype the password.
- In the LTPA key password field, type the Lightweight Third Party Authentication password used to encrypt and decrpyt the LTPA key.
- In the LTPA key password verification field, retype the password.
- Click Next.
- In the Security user ID field, type the ID that you will use for the security user. This user ID is used to access the WebSphere Application Server Administration Console when security is enabled. This user ID should also be a user ID on the LDAP server.
- 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. Complete the steps and click Finish.
- 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 correct log will display on the page).
- The WebSphere Commerce server should have been started. In addition, ensure that the WebSphere Commerce Payments server is started. For more information, see Starting or stopping a WebSphere Commerce Payments instance.
- Set up WebSphere Commerce Payments for your store. For more information, see Setting up WebSphere Commerce Payments for your store.
- If you are using a Sun ONE Web server change the encryption back to 128 bit. For more information, see Changing encryption.
- Configure other instances as necessary.
- To verify that your configuration worked correctly, do the following:
- Navigate to WC_installdir/logs.
- Check the WCPconfig_wc.err.log file for any errors.
- Check the WCPconfig_wc.log file for any errors.
- To confirm that the store has published successfully and that you can log on to WebSphere Commerce, do the following:
- Open the WebSphere Commerce Accelerator.
- Access the following Web address in your browser:
https://hostname:8000/accelerator
where hostname is the fully-qualified WebSphere Commerce Web server host name. The host name may be a virtual host name on the Web server
- Access the following Web address in your browser:
- Log onto the WebSphere Commerce Accelerator as follows:
- From the WebSphere Commerce Logon page, type your WebSphere Commerce user name and password. The Select Store and Language page displays.
Note: If only one store, one language, and one or no fulfillment center is defined, then the Select Store and Language page does not display. You go directly from the WebSphere Commerce Accelerator logon page to the home page.
- From the Store name drop-down list, select the name of the store you created (the consumer direct commerce enabled portal is called Winstons and the B2B direct commerce enabled portal is called
ToolTech).
- From the Language to work in drop-down list, select the language in which you want to administer the store. If you are authorized to work with a single language, the language is pre-selected. If you are authorized to work with more than one of the WebSphere Commerce supported languages, the store's default language is pre-selected; however, you can select a different language from this list.
- Click OK.
- From the WebSphere Commerce Logon page, type your WebSphere Commerce user name and password. The Select Store and Language page displays.
- If the store shows up and you can log in, you have configured Commerce Enabled Portal on WebSphere Commerce successfully.
- Open the WebSphere Commerce Accelerator.