IBM Connections Docs CR1 installation may fail with an error on Conversion server

It has happened to me in at least 3 different systems that the installation on Docs CR1 fails throwing an error about DocsConversion failed. Looking into the iFixInstall.log file you will see

…………………
2016-07-22 12:13:28,415 DEBUG WASX7209I: Connected to process “dmgr” on node connectionsCellManager using SOAP connector; The type of process is: DeploymentManager

WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: “[checkin_json, conversion-config.json]”2016-07-22 12:13:28,415 INFO DocsConversion update failed!
2016-07-22 12:13:28,415 DEBUG Traceback (most recent call last):
File “applypatch.py”, line 31, in update_product
update_apps()
File “applypatch.py”, line 67, in update_apps
update_conversion_binary()
File “applypatch.py”, line 168, in update_conversion_binary
result = CONFIG.call_was_task(‘remote_install_a_version’,[me_hostname, escapes_for_was(str(target_list)), str(sym_count)],True)
File “c:\IBMConnectionsDocs_2.0_CR1\config.py”, line 60, in call_was_task
was_out = self.call_wsadmin(args)
File “c:\IBMConnectionsDocs_2.0_CR1\config.py”, line 43, in call_wsadmin
raise Exception(“Exception thrown while executing WebSphere command:” + ws_out)
Exception: Exception thrown while executing WebSphere command:WASX7209I: Connected to process “dmgr” on node connectionsCellManager using SOAP connector; The type of process is: DeploymentManager

WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: “[remote_install_a_version, DOCS.yourdomain.com, [u\’DOCS.yourdomain.com\’], 8]”

WASX7017E: Exception received while running file “../execwas.py”; exception information: com.ibm.websphere.management.exception.AdminException: CWWSY0102E: Target with name DOCS.yourdomain.com was not found.

The error is somewhat misleading because upon reading it I immediately went on my system and verified that a target in the job manager with the correct name existed. So this is not the real cause.

I opened a PMR and today had a remote session with David McCarthy from IBM Support in Dublin and Jie Peng  from the Docs Dev labs in China, and they solved the issue.

  1. Go in the directory where you have the CR1 installation software
    – Edit the file applypatch.py
    – comment those 2 lines in red
    def update_apps():
    “””update apps in present work directory”””
    for filename in os.listdir(‘./’):
    if(filename.endswith(“.ear”) or filename.endswith(“.ear.zip”)):
    appname = get_app_name(filename)
    CONFIG.call_was_task(‘update_app’,[appname, filename])
    #if os.path.exists(“docs_remote_installer.zip”):
    #update_conversion_binary()
    – go in the DocsApp subdirectory and delete the file concord-config.json
    – run applypatch again
  2. Stop IBM Conversion Cluster, Websphere Console->Servers->Clusters->WebSphere application server clusters->IBMConversionCluster->Stop
  3. In the  directory where you have the CR1 installation software, open the DocsConversion subdirectory. Unzip the file docs_remote_installer.zip in a directory of your choice, for example c:\temp\docs_remote_installer
  4. Change directory to c:\temp\docs_remote_installer\installer\ and run the following command
    upgrade_node.bat – -installroot [CONVERSION_INSTALL_ROOT] – -symcount
    [SYM_COUNT]
    where [CONVERSION_INSTALL_ROOT] value you can get from the ISC (Environment -> WebSphere Variables-> CONVERSION_INSTALL_ROOT
    [SYM_COUNT] is the number of symphony instances, you can get this by counting how many inst* in [CONVERSION_INSTALL_ROOT]\symphony, usually it is 4 or 8.for example: upgrade_node.bat – -installroot c:\IBM\ConnectionsDocs\Conversion – -symcount 8
  5. Check fixpack.log in directory [CONVERSION_INSTALL_ROOT]\logs\
  6. Start IBMConversionCluster, Websphere Console->Servers->Clusters->WebSphere application server clusters->IBMConversionCluster->Start

Now open a browser and go to http://yourdocsserver/conversion/version, you should see something like this

{“timestamp”:”20160711-0948″,”version”:”2.0.0.1″,”build_description”:”IBM Connections Docs 2.0.0″,”product_name”:”IBM Connections Docs”}

If you still see version 2.0.0 then go back in the directory where you have the CR1 installation software, then in the DocsApp subdirectory and delete again concord-config.json. Run again the applypatch command, that will fix it.

Advertisements

6 thoughts on “IBM Connections Docs CR1 installation may fail with an error on Conversion server

  1. Robert, you’re right. In my original post there were two hyphens, I have no idea why WordPress reduced it to one when publishing the post.
    I changed it now, hopefully it will render fine.

    Like

  2. The “upgrade_node.bat” has to be executed on the Conversion node, correct? Although its in a directory called docs_REMOTE_installer?

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s