Creating self-signed certificates for testing IBM Digital Analytics for IBM WebSphere Commerce

Use a self-signed or third-party certificate for testing IBM Digital Analytics, formerly known as Coremetrics Analytics in a staging or test environment.

Procedure

Log on as the WebSphere Commerce instance owner
or example, "wasuser".
Log on as a system administrator
Set the environment by running the following command:
- WAS_profiledir/bin/setupCmdLine.sh
- WAS_profiledir\bin\setupCmdLine.bat
Create your own store key database file by using ikeyman utility:
- WAS_profiledir/bin/ikeyman.sh
- WAS_profiledir\bin\ikeyman.bat
his sample uses the following values:

Key Database File

New

Key Database type

JKS

File Name

mykeyfile.jks

Note the Location - You require this information later.

A password prompt displays. Note the password as you require it later. This example uses "ssl4you".
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>