Main Home: Royalcyber.com  |  Tel: +1.630.355.6292   |  Global Offices  

Troubleshooting common Publishing Issues

The following error is shown in the SystemOut.log while importing Personalization rules. EJPVP10606E Items to be imported already exist in the workspace

If you had exported the entire workspace including the root node and were attempting to import to target server using the “Import” button, this will not work since the root node already exists. You need to export from a folder if you wish to use the import option.
Note: Simply moving the nodes from root to a folder will not work since the configured portlets expect the rule to be at the root location. You would need to reconfigure the portlets.

pznload script fails with javax.net.ssl.SSLHandshakeException 

Symptom:

WebSphere\PortalServe\pzn\v6.0\publish>pznload.bat
--serverUrl https://wpsupport.xxx.xxx.xxx:10035/wps/pznpublish/pznpublishtarget
--username wpsadmin --password xxxxxx c:\rule\SampleRule.nodes

Publishing file: 'c:\rule\SampleRule.nodes'
Server url: 'https://wpsupport.xxx.xxx.xxx:10035/wps/pznpublish/pznpublishtarget'
Destination workspace: 'The default workspace for rules on the target server.'
Destination path: '/'
Published objects will only overwrite existing objects

Publish started [datetime] Connecting to the publish server
datetime com.ibm.websphere.personalization.publish.command.AbstractPublishExecutor execute
WARNING: could not send the request data
javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: Certificate not Trusted
at com.ibm.jsse2.bx.a(Unknown Source)
at com.ibm.jsse2.by.a(Unknown Source)
at com.ibm.jsse2.by.a(Unknown Source)
at com.ibm.jsse2.w.a(Unknown Source)
at com.ibm.jsse2.w.a(Unknown Source)
at com.ibm.jsse2.v.a(Unknown Source)
at com.ibm.jsse2.by.a(Unknown Source)
at com.ibm.jsse2.by.l(Unknown Source)
at com.ibm.jsse2.by.startHandshake(Unknown Source)
at com.ibm.net.ssl.www.protocol.https.b.o(Unknown Source)
at com.ibm.net.ssl.www.protocol.https.q.connect(Unknown Source)
at com.ibm.net.ssl.www.protocol.https.t.connect(Unknown Source)
at com.ibm.websphere.personalization.servlet.util.HttpUrlConnectionWriter.initialize(HttpUrlConnectionWriter.java:121)
at com.ibm.websphere.personalization.servlet.util.HttpUrlConnectionWriter.close(HttpUrlConnectionWriter.java:110)
at com.ibm.websphere.personalization.publish.command.AbstractPublishExecutor.execute(AbstractPublishExecutor.java:112)
at com.ibm.websphere.personalization.publish.task.LoadFromFileSystemTask.run(LoadFromFileSystemTask.java:89)
at com.ibm.websphere.personalization.publish.PznLoad.main(PznLoad.java:60)
Caused by: java.security.cert.CertificateException: Certificate not Trusted
at com.ibm.jsse.bi.a(Unknown Source)
at com.ibm.jsse.bi.checkServerTrusted(Unknown Source)
at com.ibm.jsse2.ba.checkServerTrusted(Unknown Source)
... 14 more
Publish failed [datetime] The publish job could not be started: Unable to communicate with the remote server

The pznload script will fail with above error, if the trust store are not included in cacerts. The truststore for Personalization is handled through JSSE. Since this task is executed as a separate java process, it by default looks for the truststore in
<was_home>\java\jre\lib\security\cacerts. Use the IKeyman utility in WebSphere Application Server to extract the WAS certificates into cacerts and rerun the task. Please refer to WebSphere Application Server Infocenter to extract/import certificates.
Also, please note you have to extract the certificate in the target/publish server and import in the node, where you are running the task.

pznload script fails with java.io.IOException: HTTPS hostname wrong exception
This error occurs when the serverUrl is configured to utilize SSL.

Symptom:

WebSphere\PortalServer\pzn\v6.0\publish>pznload.bat
--serverUrl https://wpsupport.xxx.xxx.xxx:10035/wps/pznpublish/pznpublishtarget
--username wpsadmin --password xxxxx c:\rule\SampleRule.nodes

    Publishing file: 'c:\rule\SampleRule.nodes'
    Server url: 'https://wpsupport.xxx.xxx.xxx:10035/wps/pznpublish/pznpublishtarget'
    Destination workspace: 'The default workspace for rules on the target server.'

Destination path: ‘/’


    Published objects will only overwrite existing objects

Publish started    [datetime] Connecting to the publish server
datetime  com.ibm.websphere.personalization.publish.command.AbstractPublishExecutor execute
WARNING: could not send the request data
java.io.IOException: HTTPS hostname wrong:  should be <wpsupport.xxx.xxx.xxx>
        at com.ibm.net.ssl.www.protocol.https.b.b(Unknown Source)
        at com.ibm.net.ssl.www.protocol.https.b.o(Unknown Source)
        at com.ibm.net.ssl.www.protocol.https.q.connect(Unknown Source)
        at com.ibm.net.ssl.www.protocol.https.t.connect(Unknown Source)
        at com.ibm.websphere.personalization.servlet.util.HttpUrlConnectionWriter.initialize(HttpUrlConnectionWriter.java:121)
        at com.ibm.websphere.personalization.servlet.util.HttpUrlConnectionWriter.close(HttpUrlConnectionWriter.java:110)
        at com.ibm.websphere.personalization.publish.command.AbstractPublishExecutor.execute(AbstractPublishExecutor.java:112)
        at com.ibm.websphere.personalization.publish.task.LoadFromFileSystemTask.run(LoadFromFileSystemTask.java:89)
        at com.ibm.websphere.personalization.publish.PznLoad.main(PznLoad.java:60)
Publish failed     [datetime] The publish job could not be started: Unable to communicate with the remote serverWebSphere\PortalServer\pzn\v6.0\publish>

  1. Ensure WebSphere Application Server (WAS) on the target node is configured to use SSL.
  2. Ensure the certificate has the same common name as the hostname.

    NOTE: 
    If you are using the default certificates that is shipped with WebSphere Application Server, then the common name for this host is “jserver: and you will receive the above error.
    If you need assistance with configuring the certificates in WebSphere Application Server (WAS), Contact WAS Support.

Unable to publish the rules using a custom port and firewall enabled.

Ensure the port that is being used for publishing is opened through the firewall.

When publishing to a server with a different username and password than the source, the following error occurs:


EJPVP20003E: The publish job could not be started: 'The username or password you specified was not valid'

This causes the publish action to fail.

Have the two servers to use the same username and passwords.

Posted in Faqs

 

cont-us-btn

 

Copyright © 2002-2018 Websphereportalguru.com. All Rights Reserved.