JR51392: disableSecurityPort fails during feature enablement

APAR status

• Closed as program error.

Error description

• While enabling the foundation feature on a federated
  environment, the enablement fails with the following error in
  the logs:
  WASX7017E: Exception received while running file
  "/WebSphere/CommerceServer/components/foundation/subcomponents/s
  earch/deploy/scripts/disableSecurityPort.jy"; exception
  information:
  com.ibm.websphere.management.cmdframework.InvalidParameterValueE
  xception: ADMF0003E: Invalid parameter value
  WebSphere:_Websphere_Config_Data_Id=cells/name_search_cell/nodes
  /name_search_node/servers/solrServer|server.xml#TransportChannel
  Service for parameter target for command listChains.
  
  
  BUILD FAILED
  
  /WebSphere/CommerceServer/components/common/xml/enableFeature.xm
  l:96: The following error occurred while executing this line:
  /WebSphere/CommerceServer/components/common/xml/enableFeature.xm
  l:190: The following error occurred while executing this line:
  /WebSphere/CommerceServer/components/common/xml/applicationTasks
  .xml:39: The following error occurred while executing this line:
  /WebSphere/CommerceServer/components/common/xml/applicationTasks
  .xml:136: The following error occurred while executing this
  line:
  /WebSphere/CommerceServer/components/foundation/xml/custom/custo
  mAction.xml:81: The following error occurred while executing
  this line:
  /WebSphere/CommerceServer/components/foundation/subcomponents/se
  arch/deploy/deploySearch.xml:63: The following error occurred
  while executing this line:
  /WebSphere/CommerceServer/components/foundation/subcomponents/se
  arch/deploy/deploySearch.xml:1178: Java returned: 105
  

Local fix

• Before feature enablement:
  -- find file in
  <WC_installdir>\components\foundation\subcomponents\search\deplo
  y\deploySearch.xml, around line#63, comment out:
   <antcall target="disableSecurityPort"/>
  <project name="deploySearch" default="deploy" basedir=".">
  
          <target name="deploy" depends="setSearchVariables,
  inputValidation">
                  <antcall target="prepareSolrHomeAndSearchEAR"/>
                  <antcall target="CreateSearchProfile"/>
                  <antcall target="CreateSearchServer"/>
                  <antcall target="PrepareWASEnvironment"/>
                  <antcall target="deploySearchApplication"/>
                  <antcall target="configSearchBinding" />
                  <antcall target="updateSearchProperties" />
                  <antcall target="ConfigWebserver"/>
                  <antcall target="GeneratePlugin"/>
  <antcall target="disableSecurityPort"/>
                  <antcall target="PropagateKeyring"/>
                  <antcall target="AddSolrService"/>
                  <antcall target="configSolrWebServer"/>
                  <antcall target="importWASChainedCertificate"/>
                  <antcall target="configSSLforIHS" />
                  <antcall
  target="createSearchObjectCacheInServer" />
          </target>
  
  Save the changes
  
  After feature enablement:
  
  1. Login to the search server WAS Admin Console:
  http://hostname.torolab.ibm.com:<port#>/ibm/console
  
  2. From the left navigation menu, select:
  Servers -> Server Types ->WebSphere Application Servers
  
  Select the search server name,
  
  3. From search server page, in the Configuration tab, find
  Communications and click Ports
  
  4. From the Ports page, find Port Name - "WC_defaulthost_secure"
   with Port#9444, click "View associated transports"
  
  5. Click each link, inside of each content page, uncheck the
  "Enabled" option,
  
  Save the changes
  
  Make sure to disable both secure items,
  
  6. Copy the file:
  <solrProfilePath>/config/cells/<SearchCellName>/nodes/<SearchNod
  eName>/servers/<searchWebserverName>/plugin-cfg.xml
  and replace
  <searchPluginInstallLocation>/config/<searchWebserverName>/plugi
  n-cfg.xml
  
  Ensure that the file owner, owner group and file permissions are
   the same as the other files in the same directory after
  applying the above changes.
  

Problem summary

• USERS AFFECTED:
  WebSphere Commerce users on v7 who use Solr in a federated
  environment.
  
  PROBLEM ABSTRACT:
  disableSecurityPort fails during feature enablement.
  
  BUSINESS IMPACT:
  Feature Enablement is not possible.
  

Problem conclusion

• In federated environment, server cellname and node should not be
   hard coded in the scripts. By passing the true search server
  cellname and nodename into disableSecurityPort.jy from
  deploysearch.xml during foundaiton enablement, generate the
  correct chainsID and disable the 9444 port.
  -------------------------------------------------------------
  The latest available maintenance information can be obtained
  from the Recommended Fixes for WebSphere Commerce technote:
  http://www.ibm.com/support/docview.wss?rs=3046&uid=swg21261296
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WC BUS EDITION

• Fixed component ID

  5724I3800

Applicable component levels

• R700 PSY

     UP