So Docs 2 CR1 and iFix 1 is not playing ball

posted in: community, connections, docs, Technical | 0

I knew that some of our community had seen issues with applying Docs 2 CR1 and the accompanying iFix, so I purposely held off applying it.

But low and behold on Saturday afternoon when I did attempted to install CR1 I had problems.

The Docs and Viewer applications deployed without issues, but the Conversion server had these errors:

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, connections.hostname.com, [u\'connections.hostname.com\'], 8]"

WASX7017E: Exception received while running file "../execwas.py"; exception information: com.ibm.websphere.management.exception.AdminException: CWWSY0102E: Target with name connections.hostname.com was not found.

My friend and co-speaker Roberto Boccadoro had had this exact issue .. so off I went to his blog and round this post: IBM Connections Docs 2.0 CR1 fix does not install.

Excellent .. Followed the instructions but that didn’t resolve it – exactly the same issue. I checked the machine name, its host entry and FQDN and they were all correct – stumpted I asked in the Connections skype chat as I know other people had seen similar issues.

Monday morning .. I started getting some answers ….

Another quality participant Robert Farstad had seen issues with the Conversion application installing the iFix 1 for CR1 so I checked out his blog post here: Docs 2.0 CR1 iFix 001 – Conversion app will not update. Where there is an issue with the conversion-config.json in the Dmgr config not having the iFix attribute in the build section
i.e

 "ifix_version": 6,

I added this at version 1 for my test as I hadn’t applied any fixes at this point.

Tried to run the update again and you guessed it – failed again with the same issue as previously.

Roberto went back through his notes and found another post he had made on another Docs install he had issues applying the fix on ..IBM Connections Docs CR1 installation may fail with an error on Conversion server. This issue was exactly the same problem as I had the resolution is actually very simple

  1. Edit the applypatch.py in the Docs CR1 install directory
    Comment out the 2 lines in red from the def update_apps() section of the file

    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()
  2. Under Docs CR1 install directory, go into the DocsApp subdirectory and rename the file concord-config.json to concord-config.json.OLD or something similar
  3. Re run the apply update script – it should work this time AND update the ifix version number in the config file to 6.
  4. Stop the Conversion cluster
  5. Under Docs CR1 install directory open the DocsConversion subdirectory. Unzip the docs_remote_installer.zip to a directory (in my case this was E:\Install\Docs\IBMConnectionsDocs_2.0_CR1\DocsConversion\docs_remote_installer)
  6. Check the [SYM_COUNT] which is the number of instances of symphony that are configured, typically this is between 4 and 8. Check the <Conversion_Install_Root>\symphony directory (in my case E:\IBM\ConnectionsDocs\Conversion\symphony)
  7. From the docs_remote_installer directory () run the command
    upgrade_node.bat --installroot <CONVERSION_INSTALL_ROOT> --symcount <SYM_COUNT>
    
    i.e
    
    upgrade_node.bat --installroot E:\IBM\ConnectionsDocs\Conversion --symcount 8
  8. Check fixpack.log in directory <CONVERSION_INSTALL_ROOT>\logs\
  9. Restart the Conversion cluster

Now all is good with my Docs update .. its working perfectly with Connections.

Thanks again to Roberto and Robert for helping me find the right solution.

Leave a Reply