Home

Commerce Issues

 

+

Search Tips   |   Advanced Search



Contents

  1. Opening PMRs
  2. Quick configuration search
  3. Nov 03 - WCS 7UP UAT2.0 - Ratings and Reviews - Ratings are not being displayed as required in the VDS
  4. Oct 16 - Order confirmation mail is not received for QT Deliv Environment
  5. Oct 10 - Unable to localize to all stores in QT Delivery
  6. Sep 22, 2011 - AD Stage - SSL Handshake exception
  7. Sep 15, 2011 - AD Stage - Node Agent sync errors
  8. Sep 14, 2011 - AD Stage - SSL HANDSHAKE FAILURE during startup
  9. Aug 15, 2011 - QA Live Cell2 SSL issues
  10. Aug 10, 2011 - QA Live Cell1 node "Not synchronized"
  11. Jul 30, 2011 - Unable to deploy OnlineCatalogEE.ear
  12. Jul 21, 2011 - Slow start
  13. Jul 14, 2011 - Scheduled jobs not running
  14. Jul 14, 2011 - Stage Prop APAR
  15. Jul 1, 2011 - App distribution
  16. Jun 29, 2011 - Cannot browse to a PLP
  17. Jun 29, 2011 - ST Stage DCTM issue
  18. Jun 27, 2011 - CMC Preview Functionality Not Working
  19. Jun 27, 2011 - wsadmin credential errors
  20. Jun 20, 2011 - OutOfMemory
  21. Jun 15, 2011 - ST STAGE (s1st6a) data source
  22. May 28, 2011 - checkEnablementStatus.sh issue on qa9a
  23. May 23, 2011 - Management Center in AD Deliv not working
  24. May 14, 2011 - QA Live s1qa9a deployment issues
  25. May 12, 2011 - QA Live s1qa8a deployment issues
  26. May 11, 2011 - ST Stage s1st6a
  27. May 6, 2011 - Feature Pack 2 enablement - QA Live s1qa9a
  28. May 5, 2011 - Feature Pack 2 enablement - QA Live s1qa8a
  29. May 5, 2011 - QA Live s1qa8a
  30. May 3, 2011 - APAR 25595
  31. May 2, 2011 - IHS and Plugin fixes not installing
  32. Apr 28, 2011 - QA Live ConfigureDatabase issue
  33. Apr 19, 2011 - ST Delivery federation
  34. ST1Live Site Admin login/password
  35. ST1Live instance creation issue
  36. DB2 tablespace issue (Fixed)
  37. Credentials issue
  38. adminctl bad user name



Opening PMRs

If you need to contact IBM Support to open a PMR online, or open a PMR using IBM's phone support: 800IBMSERV.

MyCo's IBM Customer Number: 1111111



Quick configuration search

Script to do a quick config file search...

cd $WC_PROFILE

if [ -d $WC_PROFILE/installedApps ]
then
    cd $WC_PROFILE/installedApps
else
    echo "$WC_PROFILE/installedApps does not exist"
fi

if [ "$1" != "" ]
then
   xpr=$1
   echo "Searching for $xpr"
else
   echo "Usage: fconfig.sh search_string"
   exit
fi

z=""
for i in `find . -name \*.xml`
do
    z=`grep -l $xpr $i 2>/dev/null`
    if [ -n "$z" ]
    then
        echo "$z"
    fi
    z=""
done



Nov 03 - WCS 7UP UAT2.0 - Ratings and Reviews - Ratings are not being displayed as required in the VDS



Oct 16 - Order confirmation mail is not received for QT Deliv Environment

Description: Order confirmation mail is not received for QT Deliv Environment.

Steps To Recreate:

  1. Log In to http://myco-qp71.mycodev.com
  2. Search for any SKU and add the item to cart (example 978922).
  3. Shopping cart page is displayed.
  4. Click on Checkout now in shopping cart page. The Sign In page will be displayed.
  5. Click Continue Checkout in the sign in page and the user will be navigated to Shipping methods page.
  6. Enter all the necessary fields in shipping methods page and click continue.
  7. Payment Methods page will be displayed.
  8. Enter all Billing and Contact information and click on "Submit Order".
  9. Order Confirmation page is displayed.
  10. Check Order confirmation mail is received for your mail Id

Expected Result: Order cofirmation mail should receive for all orders.
Actual result: Order confirmation mail is not received after 1 day.

Order Number:

    Merchandise - W132756205, W132744447
    Gift Card   - W132756211, W132606563
    Appliance   - W132756215, W132606562

Debugging steps...

I verifed SMTP email host mail1.myco.com, defined in WCS admin console, is working

s1qp8i: /home/wasadmin==> telnet mail1.myco.com 25
Trying...
Connected to mail2.ern.myco.com.
Escape character is '^]'.
220 025-SN1MAIO-06 Trusted Receive Connector
ehlo myco.com
250-025-SN1MAIO-06.025d.mgd.msft.net Hello [130.30.236.82]
250-SIZE 73400320
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-AUTH
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 XEXCH50
mail from:micheal_pareene@myco.com
250 2.1.0 Sender OK
rcpt to:micheal_pareene@myco.com
250 2.1.5 Recipient OK
data
354 Start mail input; end with <CRLF>.<CRLF>
Subject: test message

this is a test message
.
250 2.6.0 <59f4e13d-0901-43da-90de-e1a51@025-SN1MAIO-06.025d.mgd.msft.net> Queued mail for delivery
quit
221 2.0.0 Service closing transmission channel
Connection closed.



Oct 10 - Unable to localize to all stores in QT Delivery

Go to http://myco-qp71.mycodev.com/StoreFinder/index.jsp and search for store 121.

Expected Result: It should display the stores within 50 miles.
Actual Result: It is not displaying any stores within 50 miles

Fix:

s_code.js is missing in QT env on web server and that is resulting in issues with store finder. The same js file exists on qa and thats the reason it works fine...

$ ssh -f s1qa8c ls -l $WC_PROFILE/installedApps/MyCoCell/WC_MyCo.ear/Stores.war/mcus/scripts/s_code.js
-rwxr-xr-x 1 wasadmin www 58127 Jun 12 17:16 WC_PROFILE/installedApps/MyCoCell/WC_MyCo.ear/Stores.war/mcus/scripts/s_code.js

$ ssh -f s1qp8n ls -l $WC_PROFILE/installedApps/MyCoCell/WC_MyCo.ear/Stores.war/mcus/scripts/s_code.js

ls: 0653-341 The file WC_PROFILE/installedApps/MyCoCell/WC_MyCo.ear/Stores.war/mcus/scripts/s_code.js does not exist.

To fix:

for i in `cat s1qp8n s1qp8o s1qp7n s1qp7o`
do
scp s_code.js ${i}:$WC_PROFILE/installedApps/MyCoCell/WC_MyCo.ear/Stores.war/mcus/scripts/
done



Sep 22, 2011 - AD Stage - SSLHandshake Exception

  1. Clear cookies

  2. Clear cache

  3. Open AD71 Stage environment Checkout page

  4. If asked whether you only want to view content that was delivered securely, select NO

  5. Sign in.

  6. Go to My Account

  7. Select "Email and Clubs"

  8. You should see the exception.

    Error...

    [9/12/11 15:21:36:556 EDT] 00000028 servlet E com.ibm.ws.webcontainer.servlet.ServletWrapper service SRVE0068E: Uncaught exception created in one of the service methods of the servlet /mcus/GlobalHeader.jsp in application WC_MyCo. Exception created : com.ibm.websphere.servlet.error.ServletErrorReport: Problem accessing the absolute URL "https://secure.myco-st71stg.mycodev.com/webapp/catalog/servlet/LayoutServiceInvoker?storeId=10051&langId=%2d1&catalogId=10053&service=header&container=no&version=v2". javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.g: PKIX path building failed: java.security.cert.CertPathBuilderException: PKIXCertPathBuilderImpl could not build a valid CertPath.; internal cause is:
    java.security.cert.CertPathValidatorException: The certificate issued by CN=VeriSign Class 3 International Server CA - G3, OU=Terms of use at https://www.verisign.com/rpa (c)10, OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US is not trusted; internal cause is:
    java.security.cert.CertPathValidatorException: Certificate chaining error
    Caused by: javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.g: PKIX path building failed: java.security.cert.CertPathBuilderException: PKIX
    CertPathBuilderImpl could not build a valid CertPath.; internal cause is:
    java.security.cert.CertPathValidatorException: The certificate issued by CN=VeriSign Class 3 International Server CA - G3, OU=Terms of use
    at https://www.verisign.com/rpa (c)10, OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US is not trusted; internal cause is:
    java.security.cert.CertPathValidatorException: Certificate chaining error

To set trace...

*=info: com.ibm.ws.security.*=all: SSL=all

Sept 22

Unable to recreate issue. I am successfully pulling up Email and Clubs page.



Sep 15, 2011 - AD Stage - Node Agent sync errors

Node synchronization issues in nodeagent log between AD Stage appserver (s1ad6a) and AD Stage dmgr (s1ad6d).

[9/15/11 14:24:36:455 EDT] 0000005e NodeSync E ADMS0012E: The system is unable to create an administrative client connection: com.ibm.websphere.management.exception.AdminException: Admin client connection to deployment manager is unavailable; nodeagent has not discovered the dmgr
at com.ibm.ws.management.sync.NodeSync.getAdminClient(NodeSync.java:503)
at com.ibm.ws.management.sync.NodeSync.getCellRepositoryEpoch(NodeSync.java:378)
at com.ibm.ws.management.sync.NodeSyncTask.doSync(NodeSyncTask.java:237)
at com.ibm.ws.management.sync.NodeSyncTask.run(NodeSyncTask.java:157)
at java.lang.Thread.run(Thread.java:736)
.
[9/15/11 14:24:36:459 EDT] 0000005e NodeSync E ADMS0005E: The system is unable to generate synchronization request: com.ibm.websphere.management.exception.AdminException: Admin client connection to deployment manager is unavailable; nodeagent has not discovered the dmgr
at com.ibm.ws.management.sync.NodeSync.getAdminClient(NodeSync.java:503)
at com.ibm.ws.management.sync.NodeSync.getCellRepositoryEpoch(NodeSync.java:378)
at com.ibm.ws.management.sync.NodeSyncTask.doSync(NodeSyncTask.java:237)
at com.ibm.ws.management.sync.NodeSyncTask.run(NodeSyncTask.java:157)
at java.lang.Thread.run(Thread.java:736)

Following steps in TroubleShooting: Synchronization problems to try and debug.

Note that contrary to technote instructions, FileTransfer app should not be visable in Enterprise Applications panel as it became a System Application as of WAS v6.1.

This is not a problem with duplicate ports.

According to this discussion, the problem could be related to certificates.



Sep 14, 2011 - AD Stage - SSL HANDSHAKE FAILURE during startup

Appserver startup is failing on AD Stage

[9/14/11 13:38:15:057 EDT] 00000001 WSX509TrustMa E CWPKI0022E: SSL HANDSHAKE FAILURE: A signer with SubjectDN "CN=s1ad6a.myco.com" was sent from target host:port "172.20.73.107:9201". The signer may need to be added to local trust store "/opt/WAS70/AppServer/profiles/MyCo/config/cells/MyCoCell/nodes/s1ad6a/trust.p12" located in SSL configuration alias "NodeDefaultSSLSettings" loaded from SSL configuration file "security.xml". The extended error message from the SSL handshake exception is: "PKIX path building failed: java.security.cert.CertPathBuilderException: PKIXCertPathBuilderImpl could not build a valid CertPath.; internal cause is:
java.security.cert.CertPathValidatorException: The certificate issued by CN=s1ad6d.myco.com, OU=Root Certificate, OU=MyCoCell, OU=DmgrNode, O=IBM, C=US is not trusted; internal cause is:
java.security.cert.CertPathValidatorException: Certificate chaining error". java.security.cert.CertPathValidatorException: Certificate chaining error".
[9/14/11 13:38:15:089 EDT] 00000001 SystemOut O CWPKI0428I: The signer might need to be added to the local trust store. You can use the Retrieve from port option in the administrative console to retrieve the certificate and resolve the problem. If you determine that the request is trusted, complete the following steps: 1. Log into the administrative console. 2. Expand Security and click SSL certificate and key management. Under Configuration settings, click Manage endpoint security configurations. 3. Select the appropriate outbound configuration to get to the (cell):MyCoCell:(node):s1ad6a management scope. 4. UnderRelated Items, click Key stores and certificates and click the NodeDefaultTrustStore key store. 5. Under Additional Properties, click Signer certificates and Retrieve From Port. 6. In the Host field, enter 172.20.73.107 in the host name field, enter 9201 in the Port field, and 172.20.73.107_cert in the Alias field. 7. Click Retrieve Signer Information. 8. Verify that the certificate information is for a certificate that you can trust. 9. Click Apply and Save.

One of the anomalies we are seeing in AD Stage is that the trust store signer cert for the "default" alias has an "Issued by" from the appserver instead of the dmgr.

SSL certificate and key management > Manage endpoint security configurations > s1ad6a > SSL configurations > NodeDefaultSSLSettings > Key stores and certificates > NodeDefaultTrustStore > Signer certificates > default

Alias default
Version 3
Key size 1024
Serial number 1306291503533413445
Validity period Valid from May 23, 2011 to May 19, 2026.
Issued to CN=s1ad6a.myco.com, OU=Root Certificate, OU=Cell1, OU=s1ad6a, O=IBM, C=US
Issued by CN=s1ad6a.myco.com, OU=Root Certificate, OU=Cell1, OU=s1ad6a, O=IBM, C=US
Fingerprint (SHA digest) 40:02:99
Signature algorithm SHA1withRSA(1.2.840.113549.1.1.5)

To fix, we deleted "default" SSL alias for the signer certificate, and then recreated it by using "Retrieve from Port" for the Signer Certificate, attaching to node agent (s1ad6a, port 9401). We then synced the nodes, and restarted all processes. The SSL HANDSHAKE FAILURE error we were encountering earlier with server restarts is no longer appearing.



Aug 15, 2011 - QA Live Cell2 SSL issues

Error:

[8/15/11 9:06:39:372 EDT] 0000002a SSLHandshakeE E SSLC0008E: Unable to initialize SSL connection. Unauthorized access was denied or security settings have expired. Exception is javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?

There is a tech note which references a fix.



Aug 10, 2011 - QA Live Cell1 node "Not synchronized"

According to console, node "Not synchronized".

To fix I tried...

  1. On appserver box...

    cd $WC_PROFILE/bin
    ./stopServer.sh WC_MyCo
    ./stopNode.sh
    cd $WC_PROFILE
    rm -rf wstemp/*; rm -rf tranlog/*
    cd bin
    syncNode.sh s1qa8d 8879"
    ./startNode.sh

    Note that we would NOT delete tranlog contents on a production system.

  2. Found success messages in...

    $WC_PROFILE/logs/syncNode.log

  3. In dmgr console, check...

    System Administration | Nodes

    ..and saw node status showed "Not synchronized".

So that did not work. I checked the dmgr log and found...

8/10/11 15:31:03:663 EDT] 00000015 ORBRas E com.ibm.ws.security.orbssl.WSSSLClientSocketFactoryImpl createSSLSocket ProcessDiscovery : 0 JSSL0080E: javax.net.ssl.SSLHandshakeException - The client and server could not negotiate the desired level of security. Reason: com.ibm.jsse2.util.g: PKIX path building failed: java.security.cert.CertPathBuilderException: PKIXCertPathBuilderImpl could not build a valid CertPath.; internal cause is:
java.security.cert.CertPathValidatorException: The certificate issued by CN=MyCo QA Root CA v2, O=My Company, DC=myco, DC=com is not trusted; internal cause is:
java.security.cert.CertPathValidatorException: Certificate chaining error javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.g: PKIX path building failed: java.security.cert.CertPathBuilderException: PKIXCertPathBuilderImpl could not build a valid CertPath.; internal cause is:
java.security.cert.CertPathValidatorException: The certificate issued by CN=MyCo QA Root CA v2, O=My Company, DC=myco, DC=com is not trusted; internal cause is:
java.security.cert.CertPathValidatorException: Certificate chaining error

So there might be a certificate.

Also in the past removing symbolic links has fixed node sync issues. s1qa8a has the following symbolic links...

$ find . -type l
./installedApps/MyCoCell/OnlineCatalogEE.ear/OnlineCatalog.war/mcus/ShoppingArea/Content/en_US
./installedApps/MyCoCell/WC_MyCo.ear/Stores.war/mcus/ShoppingArea/Content/en_US
./installedApps/MyCoCell/WC_MyCo.ear/Stores.war/mcus/bizhtml

At this point I am going to pursue the certificate angle and see if I can discover any more log messages...

Node log has...

[8/11/11 0:46:16:849 EDT] 00000023 MBeanHelper E Could not invoke an operation on object: WebSphere:name=NodeAgent, process=nodeagent, platform=common, node=s1qa8a, diagnosticProvider=true, version=7.0.0.13, type=NodeAgent, mbeanIdentifier=NodeAgent, cell=MyCoCell, spec=1.0 because of exception: javax.management.JMRuntimeException: ADMN0034E: The service is unable to obtain a valid administrative client to connect process "s1qa8a" from process "dmgr", because of exception: com.ibm.websphere.management.exception.ConnectorException: ADMC0009E: The system failed to make the SOAP RPC call: invoke



Jul 30, 2011 - Unable to deploy OnlineCatalogEE.ear

Node agent process was running on appserver, but the NDM console showed that there was no communication between dmgr and node agent. We tried...

  1. Stopping all processes (dmgr, WC_MyCo, nodeagent)
  2. Clearing $WC_PROFILE/temp and $WC_PROFILE/wstemp
  3. startManager.sh
  4. syncNode.sh s1ad6d 8879 from appserver
  5. ./startNode.sh

But the NDM console still showed that there was no communication between dmgr and nodeagent.

I checked the dmgr SystemOut.log and noticed a lot of certificate errors. To eliminate this as possible cause, I disabled Administrative Security, and then restarted everything. After this, when checking in NDM console, we saw the dmgr was able to successfully communicate with node agent, so it looks like there might be some cert issues between ndm and node agent.

Here is error from s1ad6d:

[7/30/11 0:27:39:214 EDT] 00000016 ORBRas E com.ibm.ws.security.orbssl.WSSSLClientSocketFactoryImpl createSSLSocket ProcessDiscovery : 0 JSSL0080E:
javax.net.ssl.SSLHandshakeException - The client and server could not negotiate the desired level of security.
Reason: com.ibm.jsse2.util.g: PKIX path building failed:
java.security.cert.CertPathBuilderException: PKIXCertPathBuilderImpl could not build a valid CertPath.
internal cause is: java.security.cert.CertPathValidatorException:
The certificate issued by CN=MyCo QA Root CA v2, O=My Company, DC=myco, DC=com is not trusted



Jul 21, 2011 - Slow start

Error in SystemOut.log...

annotations E ArchiveInputStreamData iterate unable to process input stream java.lang.ArrayIndexOutOfBoundsException

To determine class that is causing problem, you can set trace specification is *=info:com.ibm.config.annotations=finer

Ultimate fix was to set...

name="metadata.complete" value="false"

...in...

$DMGR_HOME/config/cells/MyCoCell/applications/<app>.ear/deployments/<app>/deployment.xml

To get detailed startup trace information, set...

*=info: org.apache.struts.*=all: com.myco.*=all: com.ibm.websphere.commerce.WC_SERVER=all



Jul 14, 2011 - Scheduled jobs not running

On ST Delivery.

db2 connect to ds1012sa user wasadmin using foo

db2 "select SCCJOBREFNUM, 
            SCSPREFSTART, 
            SCSACTLSTART, 
            SCSINSTRECOV, 
            SCSRESULT, 
            SCSSTATE   
            from schconfig, SCHACTIVE 
            where SCSJOBNBR=314569 
            and SCSJOBNBR=SCCJOBREFNUM"

SCCJOBREFNUM         SCSPREFSTART               SCSACTLSTART               SCSINSTRECOV         SCSRESULT SCSSTATE
-------------------- -------------------------- -------------------------- -------------------- --------- --------
              314569 2011-07-14-00.01.00.000000 -  

See: Scheduled job states



Jul 14, 2011 - Stage Propagation APAR

Applying 7.0.0.2-WS-WCServer-IF1491.pak to ST Stage. Executing install instructions. Product install successful. WC_MyCo instance install unsuccessful. Error message:

Failed to export the WCS instance to /tmp/wcupdate directory. For more information, see the log file:

WC_INSTALL/logs/update/actions/install/exportear_WC_MyCo.log

This log file does not exist. To get past this, IBM support said to install APAR as user root (we previously tried as non-root user), so I had UNIX Admin log on to s1st6a as user root and run...

cd /opt/WCS70/UpdateInstaller
./update.sh -silent -options /opt/WCS70/UpdateInstaller/responsefiles/install.txt

Same error about failure to export. Additionally, log file...

/opt/WCS70/logs/update/actions/install/exportear_WC_MyCo.log

...has error...

[wsadmin] WASX7246E: Cannot establish "SOAP" connection to host "s1st6d.myco.com" because of an authentication failure. Ensure that user and password are correct on the command line or in a properties file.
[wsadmin] Exception message (if any): "ADMN0022E: Access is denied for the getProcessType operation on Server MBean because of insufficient or empty credentials."

I turned off Administrative security, cycled dmgr and appserver, and ran stopNode.sh, syncNode.sh, startNode.sh, and then had UNIX Admin try again. Turning off security fixed the security errors we were receiving, and the EAR export finished cleanly, but we are now running into other errors further downstream.

Unable to find IBM WebSphere Commerce at a version that is equal to 7.0.0.2.

s1st6a is currently at WCS version 7.0.0.2, so not sure why we are getting this error.

Log files:

Instance versionInfo command is failing, saying it cannot find history xml file...

cd $WC_INSTALL/bin
./versionInfo.sh /opt/WCS70/instances/MyCo

We queryed the SITE table to verify we are at WCS 7.0.0.2...

$ db2 connect to  DS1014SA user wasadmin using foo

$ db2 "select fixpack from site where compname='BASE'" FIXPACK ------- 2 1 record(s) selected.

We copied version file from another machine to move forward...

cd /opt/WCS70/instances/MyCo/properties/version/update/backup
scp s1qa8a:/opt/WCS70/instances/MyCo/properties/version/update/backup/NIFHistory.xml .

Sent UNIX Admin a request to try WCS Update Installer again...

cd /opt/WCS70/UpdateInstaller
./update.sh -silent -options /opt/WCS70/UpdateInstaller/responsefiles/install.txt

This time we got further, but did not finish. An exception was thrown saying there was not enough disk space to write to /tmp/wcupdate.

July 17: Dev has indicated they have a workaround and do not require this fix any longer.



Jul 1, 2011 - App distribution

PMR: 89445,442,000

Running...

$AdminApp isAppReady WC_MyCo

...on s1qa9a returns false.

On appserver, a rogue process, running for almost two months, was found after stopping dmgr, appserver, and nodeagent.

wasadmin 12320992 1 0 May 06 - 0:23 /opt/WAS70/AppServer/profiles/MyCo/installedApps/CommerceNetwork/WC_MyCo_soccom.ear/SocCore/zero-rep ository/stable/expanded/zero/zero.management.zso-1.1.1.3.30778/lib/ppc_64/aix/zso /opt/WAS70/AppServer/profiles/MyCo/installedApps/CommerceNetwork/WC_TH D_soccom.ear/SocApp

We also found files with incorrect permissions...

$ pwd
/opt/WAS70/AppServer/profiles/MyCo/logs/WC_MyCo/
$ls -l
-r-xr--r-- 1 wasadmin www 20971442 Jun 30 03:40 SystemErr_11.06.30_03.40.55.log
-r-xr--r-- 1 wasadmin www 20971442 Jun 30 04:21 SystemOut_11.06.30_04.21.28.log
-r-xr--r-- 1 wasadmin www 15369 Jul 01 02:43 stopServer.log
-r-xr--r-- 1 wasadmin www 17301 Jul 01 02:47 native_stdout.log
-r-xr--r-- 1 wasadmin www 6763 Jul 01 02:49 startServer.log
-r-xr--r-- 1 wasadmin www 8 Jul 01 02:49 WC_MyCo.pid
-r-xr--r-- 1 wasadmin www 20971329 Jul 01 14:02 SystemOut.log
-r-xr--r-- 1 wasadmin www 9648875 Jul 01 15:37 SystemErr.log
-r-xr--r-- 1 wasadmin www 168168124 Jul 01 15:45 native_stderr.log

One interesting anomaly found is that AIX fixpack level for s1qa9d...

$ oslevel -s 7100-00-03-1115

...is different than for all other hosts...

oslevel -s 7100-00-02-1041

We tried to recreate WC_MyCo.ear by running...

    cd $WC_PROFILE/installedApps/MyCoCell
    tar cvf /opt/install/WC_MyCo.ear.`date +"%Y%m%d"`.tar WC_MyCo.ear
    rm -rf WC_MyCo.ear
    cd $WC_PROFILE/config/cells/MyCoCell/applications
    cp -r WC_MyCo.ear /opt/install/
    rm -rf WC_MyCo.ear
    cd $WC_PROFILE/bin
    ./syncNode.sh s1qa9d 8879

Doing that should have recreated the WC_MyCo.ear file on the appserver. That did not happen.

I ran ISALite on build (s1np1a), deployment (s1qa9d), and appserver (s1qa9a).

ISALite had some runtime errors...

s1np1a: /opt/install/IHS70/htdocs/issues/ISALite==> ./runISALite.sh
WPLR0004E: Error writing version report to /PLRTOutput.xml: com.ibm.ci.invtool.core.ReportException: java.io.FileNotFoundException: /PLRTOutput.xml (The file access permissions do not allow the specified action.)
End Installation Status Report

Looks like a bug in ISALite where it is trying to write files to root directory.

Some output was generated: 89445,442,000.zip, which was sent to Portal Engineer [portalengineer@us.ibm.com].

Fix

We ran into the following permission issues (now fixed) on s1qa9a.

We are not sure how those permissions were changed.

On s1qa8a we had the same problem with log files set to read only, but did not encounter the same problem with MyCoCell permissions.

$AdminApp isAppReady WC_MyCo is returning true now, which means the app is distributed.

Until we determine cause of permission issues, I.ll be monitoring file and directory permissions more closely going forward, and encourage you to do the same

The last time stamp for log files in QA Live Cell1 had Jun 30 date. The cluster was created on Tue 6/28/2011 9:18 PM, so I don't believe it was cluster configuration that cause the problem.

I am going to add a validation to check log file permissions...

ls -lR $WC_PROFILE/logs/WC_MyCo/*.log | grep "\^-r-x"

...and directory permissions...

ls -lR $WC_PROFILE/installedApps/MyCoCell | grep drw-r--r--



Jun 29, 2011 - Cannot browse to a PLP

Issue: QA Live cell1 and cell2 both displaying "No products available"

Fix: PLP pages were broken due to Endeca development activity on AD Deliv Endeca host (QA7-1 is pointing to AD instance). Problem solved after Endeca host restarted.



Jun 29, 2011 - ST Stage DCTM issue

ST Stage did not restart after deployment.

I did a syncNode.sh on s1st6a and syncNode.log had.

[6/29/11 11:27:42:008 EDT] 00000001 AppUtils W ADMA0078W: The file: /opt/WAS70/AppServer/profiles/MyCo/installedApps/MyCoCell/WC_MyCo.ear/Stores.war/mcus/ShoppingArea/Content cannot be deleted.
[6/29/11 11:28:42:356 EDT] 00000001 FilePermissio E failure in setting file permissions

To fix....

  1. Unlink DCTM symbolic links on appserver
  2. ./stopNode.sh
  3. ./syncNode.sh s1st6a 8879
  4. ./startNode.sh
  5. Restart cluster
  6. Recreate symbolic links



Jun 27, 2011 - CMC Preview Functionality Not Working

The Out of the Box preview functionality is not working across all environments.

To recreate...

  1. Login to CMC
  2. Choose Marketing from Tools
  3. Choose mcus store
  4. Click on Preview Dialog Button

Error message is not the same on all environments, For example, on ST Delivery, we get...

A WebGroup/Virtual Host to handle /webapp/wcs/preview/servlet/PreviewStore has not been defined. SRVE0255E: A WebGroup/Virtual Host to handle s1st5c.myco.com:8006 has not been defined. IBM WebSphere Application Server

On AD Stage, we get...

404 JSPG0036E: Failed to find resource /B2BDirectStorefrontAssetStore/index.jsp /B2BDirectStorefrontAssetStore/index.jsp

For s1qa8a/s1qa9a, there are PreviewServlet initialization errors in SystemOut.log...

00000013 servlet E com.ibm.ws.webcontainer.servlet.ServletWrapper init SRVE0100E: Uncaught init() exception created by servlet PreviewServlet in application WC_MyCo:

Here are the canonical virtual host mappings that we should be using...


You might need to create virtual host VH_MyCo_Preview...

Virtual Hosts > VH_MyCo_Preview > Host Aliases
   
s1ad6c  8006    
s1ad6c  8007    
s1ad6c.myco.com  8006    
s1ad6c.myco.com  8007    


June 28:

In ST Delivery we...

  1. Mapped VH_MyCo_Preview to correct web modules
  2. Synced to master repository.
  3. Generated and propagated plugin-cfg.xml

Need to co-ordinate with Dev and QA teams for time to restart WC_MyCo application.


June 29:

Fix: In WCS 7, context path for Preview functionality changed from "webapp/wcs/stores" to "webapp/wcs/preview". Commerce Administrator is validating in QA Stage



Jun 27, 2011 - wsadmin credential errors

I was validating QA STAGE. Getting error when running wsadmin scripts...

javax.management.JMRuntimeException: ADMN0022E: Access is denied for the getState operation on Server MBean because of insufficient or empty credentials.

For example...

cd $WC_PROFILE/bin/local
../wsadmin.sh -username myadmin -password foo -f display.jacl all

The same jacl script is running cleanly on s1qa8a and s1qa9a, so I suspected node synchronization problem. To fix, I ran...

cd $WC_PROFILE/bin/local
./syncNode.sh s1qa4d.myco.com 8879

That fixed problem.



Jun 20, 2011 - OutofMemory

Javacore and heapdumps due to OutOfMemory in QA Live cell1

Change heap from...

Xmx=1024m

...to...

-Xmx=2048m

See: MustGather: Out of Memory errors with WAS

Use native_stderr.log to analyze the garbage collection activity



Jun 15, 2011 - ST STAGE (s1st6a) data source

Analyzing warnings and errors in ST Stage (s1st6a) SystemOut.log after deploy. First warning...

name: jdbc/WebSphere Commerce DB2 DataSource MyCo: First component in name WebSphere Commerce DB2 DataSource MyCo not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]

For deploy, the data source name set in...

../WC_MyCo.ear/deployments/WC_MyCo/WebSphereCommerceServerExtensionsData.jar/META-INF/ibm-ejb-jar-bnd.xmi

...did not match data source set in WAS configuration...

jdbc/WCS DB2 DataSource MyCo

To fix, I created new DS in s1st6a to match DS in ibm-ejb-bnd.xml

jdbc/WebSphere Commerce DB2 DataSource MyCo

So that warning should go away now.



May 28, 2011 - checkEnablementStatus.sh issue on qa9a

Unable to successfully run checkEnablementStatus.sh on s1qa9a

$ ./checkEnablementStatus.sh -DinstanceName=MyCo -DdbUserPassword=foo
----
Buildfile: ../components/common/xml/enableFeature.xml

ANTContribUtilities:

checkInstanceName:

init:

checkFeatureName:

BUILD FAILED
/opt/WCS70/components/common/xml/enableFeature.xml:94: The following error occurred while executing this line:
/opt/WCS70/components/common/xml/commonEnablementTasks.xml:430: The feature name common is incorrect.

Total time: 6 seconds



May 23, 2011 - Management Center in AD Deliv not working

Launching Management Center. Reviewing SystemOut.log from s1ad7a reveals lots of errors but none with timestamp corresponding to the launch. Request not making it over to appservers.


172.19.163.225 - - [23/May/2011:16:29:29 -0500] "GET /docs/ HTTP/1.1" 200 16250
172.19.163.225 - - [23/May/2011:16:29:37 -0500] "GET /lobtools HTTP/1.1" 302 -
172.19.163.225 - - [23/May/2011:16:29:38 -0500] "GET /lobtools/ HTTP/1.1" 304 -
172.19.163.225 - - [23/May/2011:16:29:38 -0500] "GET /lobtools/cmc/ManagementCenter HTTP/1.1" 200 7525
172.19.163.225 - - [23/May/2011:16:29:38 -0500] "GET /lobtools/javascript/shell/ManagementCenter.js HTTP/1.1" 304 -
172.19.163.225 - - [23/May/2011:16:29:38 -0500] "GET /lobtools/images/shell/no_tab_background.png HTTP/1.1" 304 -
172.19.163.225 - - [23/May/2011:16:29:39 -0500] "GET /lobtools/images/shell/background_tile.png HTTP/1.1" 304 -
172.19.163.225 - - [23/May/2011:16:29:40 -0500] "GET /lobtools/cmc/ManagementCenterMain?locale=en_US HTTP/1.1" 200 14790
172.19.163.225 - - [23/May/2011:16:29:42 -0500] "GET /lobtools/dojo/dojo/dojo.js HTTP/1.1" 304 -
172.19.163.225 - - [23/May/2011:16:29:42 -0500] "GET /lobtools/javascript/openLaszlo/embed-compressed.js HTTP/1.1" 304 -
172.19.163.225 - - [23/May/2011:16:29:43 -0500] "GET /lobtools/images/shell/mc_logo.png HTTP/1.1" 304 -
172.19.163.225 - - [23/May/2011:16:29:43 -0500] "GET /lobtools/ManagementCenter.swf? HTTP/1.1" 304 -
172.19.163.225 - - [23/May/2011:16:31:08 -0500] "GET /docs/issues.html HTTP/1.1" 304 -
172.19.163.225 - - [23/May/2011:16:31:08 -0500] "GET /docs/images/IHSFix.jpg HTTP/1.1" 304 -

The ManagementCenter.swf file is there, but it is tiny. I don't think it is being built correctly. Either code is messed up or there is a problem with the build.



May 14, 2011 - QA Live s1qa9a deployment issues

Comparing log files generated by the deployment failures to the log files of the successful runs yesterday and today, we see consistently that for successfully runs, the was.policy content for the profile was written to the log whereas for all the failed runs it was missing.

FAILED:

  [wsadmin] Deploying EJB module WebSphereCommerceServerExtensionsData.jar to WC_MyCo.
  [wsadmin] Started: 2011/05/13 11:21:49
  [wsadmin] WASX7017E: Exception received while running file 
            "/opt/wcbd-dist/deploy/wcbd-deploy-server-20110511-144513/scripts/wcbd-wsadmin.py"; 
            exception information: com.ibm.ws.scripting.ScriptingException: 
            WASX7444E: Invalid parameter value "" for parameter "config id" on command "showAttribute"
  [wsadmin]

SUCCESSFUL:

  [wsadmin] Deploying EJB module WebSphereCommerceServerExtensionsData.jar to WC_MyCo.
  [wsadmin] Started: 2011/05/12 22:23:28
  [wsadmin] WASX7327I: Contents of was.policy file:
  [wsadmin] 
  [wsadmin] grant codeBase "file:${application}" {
  [wsadmin] };
  [wsadmin] 
  [wsadmin] grant codeBase "file:${jars}" {
  [wsadmin] };
  [wsadmin] 
  [wsadmin] grant codeBase "file:${connectorComponent}" {
  [wsadmin] };
  [wsadmin] 
  [wsadmin] grant codeBase "file:${webComponent}" {
  [wsadmin] };
  [wsadmin] 
  [wsadmin] grant codeBase "file:${ejbComponent}" {
  [wsadmin] };
  [wsadmin] 
  [wsadmin] 
  [wsadmin] Update of WC_MyCo has started.
  [wsadmin] ADMA5058I: Application and module versions are validated with versions of deployment targets.
  [wsadmin] ADMA5009I: Extracting application archive to 
            /opt/WAS70/AppServer/profiles/dmgr/wstemp/wstemp/app_12f/ext/WebSphereCommerceServerExtensionsData.jar.
  [wsadmin] ADMA5064I: FileMergeTask completed successfully for WC_MyCo.
  [wsadmin] ADMA5113I: Activation plan created successfully.
  [wsadmin] ADMA5005I: The application WC_MyCo is configured in the WebSphere Application Server repository.

Here is SystemOut.log



May 12, 2011 - QA Live s1qa8a deployment issues

Deploying MyCo to QA Live on both dmgrs (qa71cell1 and qa71cell2) the deployment consistently failed with this message:

[wsadmin] ERROR: The application application WC_MyCo is not found on the server.

Here are logs...

This might be related to WXS augmentation of commerce appservers. We have 2 cells, cell1 and cell1, both with extreme scale client configured and enabled. We tried to deploy to cell1, but the dmgr complained about a extreme scale session management class not found. Commerce Administrator and Cher tried to disable session management and bounced the cell, but the problem of the same class not found did not go away.

WXS is interfering with the deployment

[wsadmin] ; targetException=java.lang.IllegalArgumentException: com.ibm.ws.xs.config.sessionmanagement.appmgmt.tasks.SessionManagementAppDeploymentTaskExt
[wsadmin] Server stack trace
[wsadmin] JMXTransformException java.lang.ClassNotFoundException: com.ibm.ws.xs.config.sessionmanagement.appmgmt.tasks.SessionManagementAppDeploymentTaskExt

It seems that the deployment classpath is not correct. The logs show the missing class:

com.ibm.ws.xs.config.sessionmanagement.appmgmt.tasks.SessionManagementAppDeploymentTaskExt

To fix, copy xsadmin.sessionmanagement.jar to...

$WAS_HOME/lib

...on s1ad7a and add class path entry for following jar file name to WCBD build classpath...

$WAS_HOME/lib/xsadmin.sessionmanagement.jar



May 11, 2011 - ST Stage s1st6a

Unable to create instance when running...

$ config_ant.sh -DinstanceName=MyCo ConfigureDatabase > /tmp/ConfigureDatabase.log 2>&1 &

Here are log files...


May 9, 2011 - wasadmin .profile on s1ad7a

When logging in wasadmin .profile throwing exceptionls. I added "set -x" to debug.

Someone made a change to...

/opt/db/db2/instance/db2con01/sqllib/userprofile -rwxr-xr-x 1 db2con01 db2sadm 0 Feb 09 16:06 /opt/db/db2/instance/db2con01/sqllib/userprofile

...which is called by wasadmin.s .profile. The change is throwing an exception and preventing the rest of the profile from being loaded. We need someone with edit permission for that file to log on and fix.


May 6, 2011 - Feature Pack 2 enablement - QA Live s1qa9a

It looks like it might matter whether we do federation before or after feature packs have been enabled. I am currently running into authentication problems on s1qa9a/d when running.

./config_ant.sh -buildfile $WC_INSTALL/components/common/xml/enableFeature.xml -DinstanceName=MyCo -DfeatureName=foundation -DdbUserPassword=foo

This is a problem I did not run into with lower life cycle standalone environments.

I tried setting username/password in $WC_PROFILE/properties/soap.client.properties, but that did not work, still getting auth errors.

I tried turning off security on NDM, like I did in 8a/d environment. Unfortunately, unlike in 8a/8d environment, with security turned off in 9a/9d, I am unable to do things like sync the nodes or start the appserver, so something is funky with 9a/9d.

To fix...

  1. removeNode.sh

  2. Enable FEP2

  3. Start server1 on Commerce node

  4. Run addNode.sh

    ./addNode.sh s1qa9d.myco.com 8879 -includeapps -username myadmin -password foo


May 5, 2011 - Feature Pack 2 enablement - QA Live s1qa8a

I got all the way through to social-commerce enablement, the last one and now it looks like it is stuck in an endless loop

[wsadmin] WebSphere:cell=MyCoCell,node=s1qa8a,distribution=unknown,expansion=unknown
[wsadmin] ADMA5011I: The cleanup of the temp directory for application WC_MyCo_soccom is complete.
[wsadmin] ADMA5072I: Distribution status check completed for application WC_MyCo_soccom.
[wsadmin] ADMA5071I: Distribution status check started for application WC_MyCo_soccom.
foundation, management-center, and store-enhancements are enabled

Fixed by doing a CTRL-C, and running enablement again...

CheckPrereqInDB:
[CheckFeaturePrerequisite] Feature foundation is enabled in EAR.
[CheckFeaturePrerequisite] Feature foundation is enabled in DB.

CheckFeature:
     [echo] ------------------------------------------------------
     [echo] Feature           - INSTALLED -        - DB -        - EAR -
     [echo] ------------------------------------------------------
     [echo] foundation        7.0.2.0        7.0.2.0        7.0.2.0
     [echo] ------------------------------------------------------
[forEachTask] featureName: management-center

CheckPrereqInDB:
[CheckFeaturePrerequisite] Feature management-center is enabled in EAR.
[CheckFeaturePrerequisite] Feature management-center is enabled in DB.

CheckFeature:
     [echo] ------------------------------------------------------
     [echo] Feature           - INSTALLED -        - DB -        - EAR -
     [echo] ------------------------------------------------------
     [echo] management-center        7.0.2.0        7.0.2.0        7.0.2.0
     [echo] ------------------------------------------------------
[forEachTask] featureName: store-enhancements

CheckPrereqInDB:
[CheckFeaturePrerequisite] Feature store-enhancements is enabled in EAR.
[CheckFeaturePrerequisite] Feature store-enhancements is enabled in DB.

CheckFeature:
     [echo] ------------------------------------------------------
     [echo] Feature           - INSTALLED -        - DB -        - EAR -
     [echo] ------------------------------------------------------
     [echo] store-enhancements        7.0.2.0        7.0.2.0        7.0.2.0
     [echo] ------------------------------------------------------
[forEachTask] featureName: content-version

CheckPrereqInDB:

CheckFeature:
     [echo] ------------------------------------------------------
     [echo] Feature           - INSTALLED -        - DB -        - EAR -
     [echo] ------------------------------------------------------
     [echo] content-version        7.0.2.0        N/A        N/A
     [echo] ------------------------------------------------------
[forEachTask] featureName: social-commerce

CheckPrereqInDB:
[CheckFeaturePrerequisite] Feature social-commerce is enabled in EAR.
[CheckFeaturePrerequisite] Feature social-commerce is enabled in DB.

CheckFeature:
     [echo] ------------------------------------------------------
     [echo] Feature           - INSTALLED -        - DB -        - EAR -
     [echo] ------------------------------------------------------
     [echo] social-commerce        7.0.2.0        7.0.2.0        7.0.2.0
     [echo] ------------------------------------------------------

BUILD SUCCESSFUL
Total time: 9 seconds



May 5, 2011 - QA Live s1qa8a

Yesterday I noticed that the bundled WC_MyCo application on QA Live s1qa8a was missing. After consulting with Lead Architect, we decided to restore standalone backup of configuration. Unfortunately, the reason WC_MyCo app was missing was because a federation of 8a to 8d a few days earlier. My understanding was that federation was not going to occur until after DB migration and custom WC_MyCo application deployment, so was not looking for tell-tale signs like a node agent running.

I tried to re-federate (addNode.sh), getting error:

ADMU0027E: An error occurred during federation Server nodeagent on node s1qa8a is already a member of a core group.; rolling back to original configuration.

I tried removing core group by logging on to NDM console and going to...

Servers | Core Groups | DefaultCoreGroup | Core group servers

...but page does not render. Error 500...

java.lang.NullPointerException at com.ibm.ws.console.distmanagement.DistHelper.getServerContext(DistHelper.java:589) at com.ibm.ws.console.highavailabilitymgmt.CoreGroupServerController.setupCollectionForm(CoreGroupServerController.java:156)

At this point I updated WAS NDM xml config files to remove s1qa8a core group references.

vi `find . -type f -exec grep -l s1qa8a {} \; | grep -v temp | grep -v logs`

I removed 8a references from...

./config/cells/MyCoCell/coregroups/DefaultCoreGroup/coregroup.xml

...and cycled dmgr...

./stopManager.sh -username myadmin -password 'foo'
./startManager.sh

Re-running addNode on 8a

./addNode.sh s1qa8d.myco.com 8879 -includeapps -username myadmin -password foo

That worked. Success



May 3, 2011 - APAR 25595

To prevent the following error, APAR 25595 needs to be applied on all environments.

[5/2/11 11:34:20:834 CDT] 0000004a servlet E com.ibm.ws.webcontainer.servlet.ServletWrapper service SRVE0068E: Uncaught exception created in one of the service methods of the servlet /mcus/include/AOLPS_Results.jspf in application WC_MyCo. Exception created : java.lang.ClassCastException: javax.servlet.jsp.el.ImplicitObjectELResolver$ImplicitObjects incompatible with org.apache.taglibs.standa

APAR has already been applied to development toolkits.

Here is a copy you can apply: 7.0.0.13-WS-WAS-IFPM25595.pak.

Perform a backup of WAS config before applying.



May 2, 2011 - IHS and Plugin fixes not installing

Running WAS Update Installer on web servers. Trying to install IHS and Plugin fixpacks. Fixpacks not recognized as being valid.

Note that we are installing 32-bit versions of fix packs.

Opening a PMR with IBM support.

Fix

To install successfully, as user wasadmin for both...

  1. Install 64-bit IHS fix pack
  2. Install 34-bit Plugin fix pack

Server Status
s1qa8c Complete
s1qa9c Complete
s1st6c Complete
s1st5c Complete
s1st7c Complete
s1st4a Pending



Apr 28, 2011 - QA Live ConfigureDatabase issue

Running config_ant.sh ConfigureDatabase. Getting error...

UpdateUserCreationTime:
[copy] Copying 1 file to /opt/WCS70/schema/xml
[Massload] Massloading /opt/WCS70/schema/xml/wcs.keys.xml
[Massload] -dbname dqa012sa -dbuser wasadmin -dbpwd ****** -infile /opt/WCS70/schema/xml/wcs.keys.xml -method sqlimport -commitcount 1000 -maxerror 1 -customizer -schemaname WASADMIN
[Massload] Error in MassLoading, please check logs for details.

BUILD FAILED
/opt/WCS70/config/deployment/xml/configureDatabase.xml:209: The following error occurred while executing this line:
/opt/WCS70/config/deployment/xml/configureDatabase.xml:216: The following error occurred while executing this line:
/opt/WCS70/config/deployment/xml/createBaseSchema.xml:218: Error in massloading

File /opt/WCS70/instances/MyCo/logs/messages.txt has...

> 2011-04-28 16:33:27.022, <Thread-7>, com.ibm.wca.MassLoader.MassLoad::main, S1
Exception Message: PathNotExistException: /opt/WCS70/instances/MyCo/logs/wcs.keys.error.xml

Fixed problem by...

  1. If it exists, remove line DBUSER=db2con01 from WC_INSTALL/bin/setenv.sh
  2. Running droptables.sh
  3. Running dropviews.sh
  4. Recreating instance with CreateSchema=true



Apr 19, 2011 - ST Delivery federation

Note: Apr 19, 2011 federation of ST Delivery failed. In a sense the federation actually was successful in that with every step we received a SUCCESS message. We were able to start both the appserver and WC_MyCo app, but as UNIX Admin noted, it started with errors.

I wonder if we had application errors after federation because manual changes were made to the application on the server, but no new deployment with all components occurred after Apr 16, meaning the federation surfaced some parts of the system that were still using components from the Apr 16 deploy, and not the manually edited components.

I recommend that when we try federation in the future, we should do so with a deployment where all application components are in place from the build, and not rely on files that were manually edited on the server.

We probably do not want to ever federate ST Delivery, for two reasons:

  1. Because ST Delivery will never be part of a cluster, there is no technical reason it needs to be federated

  2. More importantly, because ST Delivery DB was configured in an unusual way, which then required a kludge to enable feature packs, it might not ever federate successfully.

Future Commerce instance creation will not use the procedure we used for ST Delivery, so the issues with required configuration reset should not re-occur. ST Delivery is an outlier.

Michael Pareene



ST1Live Site Admin login/password

Because we attached to prexisting DB for ST Delivery creation, we were unable to set Site Administrator login/password. We had to reset the wcsadmin user password.

From s1st5a appserver...

$ db2
$ connect to datpoc18 user wasadmin using foo
$ select salt from userreg where logonid='wcsadmin';
SALT
-------------
v4k2ktr8tn6f
$ quit

$ cd $WC_INSTALL/bin
$ ls wcs*
$ wcs_encrypt.sh wcs_password.sh wcs_pmpassword.sh
$ ./wcs_password.sh foo5 v4k2ktr8tn6f zz333bb0000000

=== Encrypted Password ===

ASCII Format: CedMEyTgE93jb0jNlFm0jttSiJ66tRweBLum3mqeQ5A=
Hex Format: 4365644D457954674539336A62306A4E6C466D306A747453694A363674527765424C756D336D71655135413D

$ db2
$ connect to datpoc18 user wasadmin using foo
$ update userreg set logonpassword=x'4365644D457954674539336A62306A4E6C466D306A747453694A363674527765424C756D336D71655135413D' where logonid = 'wasadmin'

To re-enable disabled account we ran...

update userreg set status = 1 where users_id = -1000; users_id = -1000 for site admin user



Apr 12, 2011 - ST1Live instance creation issue

Trying to create new Commerce instance on s1st5a (ST Delivery), attaching to datpoc18. Getting error

CreateDB2SP:
[EchoNL] Creating DB2 stored procedure ...
[sql] Executing file: /opt/WCS70/schema/db2/storedprocedure/availreceipts.procedure.sql
[sql] Failed to execute: CREATE PROCEDURE availreceipts ( IN p_versionspc_id BIGINT, IN p_ffmcenter_id INTEGER, IN
p_merchantstore_id INTEGER, OUT p_availinv INTEGER, IN p_session_id BIGINT, OUT p_sperror INTEGER,
OUT p_sqlstate .snip.

BUILD FAILED
/opt/WCS70/config/deployment/xml/createBaseSchema.xml:489: com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-454,
SQLSTATE=42723, SQLERRMC=WASADMIN.AVAILRECEIPTS, DRIVER=4.11.69

Total time: 35 seconds
The createInstance.properties file I am using specifies not to create DB or Schema, and that the DB already exists.

Here are the DB related settings I am using:

db2InstallDir=/opt/db2/db2_97_03
bCreateDB=false
bCreateSchema=false
isRemoteDB=true
dbType=db2
WASJDBCDriverType=db2
ejbType=db2
sqldir=db2
dbaName=db2con01
dbaPassword=poctest01
dbName=datpoc18
dbHostname=s1ad7b.myco.com
dbServerPort=50180
dbNodeName=datpoc18
tablespaceName=WCTBLSPC
dbUserName=wasadmin
schemaName=WASADMIN
dbUserPassword=foo
dbActive=true
dbExist=true
loadmethod=sqlimport

We are going to try creating instance against existing DB by skipping the ConfigureDatabase task.

That worked.



Apr 12 - DB2 tablespace issue (Fixed)

Instance creation failure. See: createInstanceANT.log

The dba created tablespaces manually, but they are named something other than what commerce expects. We could try to figure out a mapping of what was created to what commerce expects, but we would still be missing some tablespaces based on what is created by commerce and what they have manually created.

Fix:

Pravardhan Chimmula recreated tables using IBM standard names.



Credentials issue

Feb 11, 2011

Credentials are failing when I try to log on to s1ad7a and s1ad7b. Credentials still work for s1ad7c.

I've been logging in with users root and wcsuser. Neither of them are working now for 7a and 7b.

Both UNIX Admin and Operations Architect are out today, so sent an email to Craig Wilson.

Feb 14, 2011

Fixed.

A system admin had changed passwords for both users. Passwords were reset to defaults on Sunday Feb 13.



adminctl bad user name

Feb 14, 2011

Problems starting IHS admin server:

s1ad7c:/opt/IHS70/bin # ./adminctl start
httpd: bad user name @@SetupadmUser@@
./adminctl start: admin http could not be started

Fixed by editing...

/opt/IHS70/conf/admin.conf

...and setting...

User nobody
Group nobody