Reference > Analytics for IBM WebSphere Commerce > Integrate a store with Coremetrics for IBM WebSphere Commerce
Create self-signed certificates for testing Coremetrics for IBM WebSphere Commerce
Use a self-signed or third party certificate for testing Coremetrics for IBM WebSphere Commerce in a staging or test environment.
Procedure
- Log on as the WebSphere Commerce instance owner, for example, "wasuser".
- Log on as a system administrator
- Set the environment...
- PROFILE_HOME/bin/setupCmdLine.sh
- PROFILE_HOME\bin\setupCmdLine.bat
- Create the own store key database file by using ikeyman utility:
- PROFILE_HOME/bin/ikeyman.sh
- PROFILE_HOME\bin\ikeyman.bat
his sample uses the following values:
Note the Location - You will need this later. A password prompt displays. Note the password as we will need it later. This example uses "ssl4you".
- Key Database File
- New
- Key Database type
- JKS
- File Name
- mykeyfile.jks
- Click Create > New self-signed certificate to create a self-signed certificate. Use the following values:
- keylabel
- mykey
- version
- X509V3 (default)
- key size
- 1024 (default)
- common name
- localhost
- organization
- IBM
- Repeat step 4 and 5 to create trust file "mytrustfile.jks". The WebSphere Commerce configuration file should look like this:
<store enabled="true" storeId="10001"> <configuration transmitClassName="com.ibm.commerce.bi.events.transmit.CMWebServiceTransmitter" transmitEnabled="true" cmClientID="xxxxxxxx" username="xxxxxxxx" password="xxxxxxxx" serviceURL="https://wscreceiver-prodqa.coremetrics.com/Receiver/sendEventData" sslKeyPassphrase="ssl4you" sslKeyStore="/opt/IBM/WebSphere/AppServer/profiles/demo/etc/mykeyfile.jks" sslTrustPassphrase="ssl4you" sslTrustStore="/opt/IBM/WebSphere/AppServer/profiles/demo/etc/mytrustfile.jks" /> </store>