Create self-signed certificates for testing IBM Digital Analytics for HCL Commerce

Use a self-signed or third-party certificate for testing in a staging or test environment.

Procedure

1. (AIX) (Linux) (IBM i) Log on as the WebSphere Commerce instance owner or example, "wasuser".

2. (Windows) Log on as a system administrator

3. Set the environment.

   • (AIX) (Linux) (IBM i) WAS_profiledir/bin/setupCmdLine.sh

   • (Windows) WAS_profiledir\bin\setupCmdLine.bat

4. Create our own store key database file by using ikeyman utility:

   • (AIX) (Linux) (IBM i) WAS_profiledir/bin/ikeyman.sh

   • (Windows) 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".

5. 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

6. 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>