Administering WebSphere Commerce instances through Configuration Manager

If you have WebSphere Application Server global security enabled, you should perform the following steps in order to properly stop, start, create, or delete WebSphere Commerce or WebSphere Commerce Payments instances using the Configuration Manager:

  1. In the WAS_installdir/properties directory, update the following files and properties to the following values:
    • sas.client.props
      • com.ibm.CORBA.securityEnabled=true
      • com.ibm.CORBA.loginSource=properties
      • com.ibm.CORBA.LoginUserid=validUser
      • com.ibm.CORBA.LoginPassword=validPassword
    • soap.client.props
      • com.ibm.SOAP.loginUserid=validUser
      • com.ibm.SOAP.loginPassword=validPassword
      • com.ibm.SOAP.secrityEnabled=true
  2. From the WAS_installdir/bin directory run the PropFilePasswordEncoder command (on one line) to encode the password in the sas.client.props and soap.client.props files.

    AIXLinuxSun Solaris Operating Environment

    PropFilePasswordEncoder.sh WAS_installdir/properties/
       sas.client.props com.ibm.CORBA.LoginPassword 
    
    PropFilePasswordEncoder.sh WAS_installdir/properties/
       soap.client.props com.ibm.SOAP.loginPassword
    

    i5/OSiSeries

    PropFilePasswordEncoder.sh WAS_userdir/WAS_instance/properties/
       sas.client.props com.ibm.CORBA.LoginPassword 
    
    PropFilePasswordEncoder.sh WAS_userdir/WAS_instance/properties/
       soap.client.props com.ibm.SOAP.loginPassword
    

    Windows

    PropFilePasswordEncoder.bat WAS_installdir\properties\
       sas.client.props com.ibm.CORBA.LoginPassword 
    
    PropFilePasswordEncoder.bat WAS_installdir\properties\
       soap.client.props com.ibm.SOAP.loginPassword
    
  3. Update the config_client script:

    AIXi5/OSiSeriesLinuxSun Solaris Operating Environment Add $CLIENTSOAP $CLIENTSAS to the Java argument list. For example:

    ${JAVA_EXE?} -classpath $CLASSPATH -DIDIR="$WPMDIR" 
    -Djava.security.policy="config.policy" -Djava.version="1.3"   
    -Dwas.install.root="$WAS_HOME " -Dwas.repository.root="$CONFIG_ROOT" 
    -Dcom.ibm.CORBA.BootstrapHost="$COMPUTERNAME" $CLIENTSOAP $CLIENTSAS 
    $PM_ARGS -Xmx128m com.ibm.commerce.config.client.CMClient "$@"
    

    Windows Add %CLIENTSOAP% %CLIENTSAS% to the Java argument list. For example:

    "%JAVA_HOME%\bin\java" %CLIENTSOAP% %CLIENTSAS% %PM_ARGS% "
    -Dwas.install.root=%WAS_HOME%" "-Dwas.repository.root=%CONFIG_ROOT%"
    -Dcom.ibm.CORBA.BootstrapHost=%COMPUTERNAME% 
    -Djava.security.policy="config.policy"
    com.ibm.commerce.config.client.CMClient %*
    
  4. Update the config_server script:

    AIXi5/OSiSeriesLinuxSun Solaris Operating Environment Add $CLIENTSOAP $CLIENTSAS to the Java argument list. For example:

    ${JAVA_EXE?} -classpath $CLASSPATH -DIDIR="$WPMDIR" 
    -Djava.security.policy="config.policy"  
    -Dwas.install.root="$WAS_HOME " -Dwas.repository.root="$CONFIG_ROOT" 
    -Dws.ext.dirs="$WAS_EXT_DIRS" -Dcom.ibm.CORBA.BootstrapHost="$COMPUTERNAME"
    $CLIENTSOAP $CLIENTSAS $PM_ARGS $MAX_HEAP  
    com.ibm.commerce.config.server.CMServerImpl "$@"
    

    Windows Add %CLIENTSOAP% %CLIENTSAS% to the Java argument list. For example:

    "%JAVA_HOME%\bin\java.exe" %CLIENTSOAP% %CLIENTSAS% %PM_ARGS% 
    "-Dwas.install.root=%WAS_HOME%" "-Dwas.repository.root=%CONFIG_ROOT%"
    "-Dws.ext.dirs=%WAS_EXT_DIRS%" -Dcom.ibm.CORBA.BootstrapHost=%COMPUTERNAME% 
    -Djava.security.policy="config.policy" 
    com.ibm.commerce.config.server.CMServerImpl %*
    

Feedback