Tag: docs

Posted on

GDPR and IBM Connections / Docs On-Prem

At IBM Think back in March, the Connections Offering Management team promised us some information to help with GDPR compliency. The Connections Cloud information has been available for a while and the On-Premises docuemtation was on the way.

Today my friend and fellow IBM Champion Roberto alerted me to the technotes that are available.

IBM Connections: http://bit.ly/cnxGDPR

IBM Docs: http://bit.ly/docsGDPR

There is a new section in each of the knowledgebases entitled Managing personal data in accordance with GDPR – see here for Connections and here for Docs (note the docs section mostly points to the Connections KB).

The technotes refer to a number of standard tasks that should be configured as part of the install and configuration process – such as using SSL for HTTP traffic, disabling anonymous access etc.

I am sure that this information will evolve as time goes on, but its a great start.

Posted on

IBM Docs 2 CR3 is here – and with some cool new features

So at last IBM Docs 2 CR3 has been released and with it some awesome new features that the community have been asking for (thank you IBM).

 

What’s new in Docs 2 CR3? LOADS of new features and fixes including …

The most exciting is probably the ability to deploy the Conversion server on linux (finally)!!

  • You can directly deploy Conversion server on Linux when installing IBM Docs.
  • If you already have IBM Docs installed with Conversion server on Windows, you can migrate existing Conversion server from Windows to Linux.

 

A track change feature for the Docs editor which is another feature that has been on the wish list for a while

  • Added Track Change support in Document Editor. People with editing access can use a new view in the sidebar to see what changes were made to the file and when and who. Changes can be filtered by the timeline and editors. File owners can turn Track Change on and off, and clear change history.

 

You can install CR3 straight over Docs 2, no need for the other CRs or iFixes – make sure you run the DB updates though to update the Docs schema.

 

Additional features and full realse notes can be found here: IBM Connections Docs 2 CR3 release notes

Download it now from Fix Central 🙂

Posted on

Docs 2.0 CR2 – here we go again

I am blogging this mainly so I remember how to solve this

Big thanks to fellow ICS community member and all round great guy Robert Farstad for blogging this

Again you can see a problem when patching Docs 2 to CR2 as it can’t find the FQDN of the hosts.

The code has changed so it’s not possible to use the work around that we had previously.

There is a slight twist to getting it to work which Rob has explained fabulously so thank you mate .. you saved me a lot of grief .. and even IBM point people to that blog as they did when I opened a PMR to find out how to fix it .. 🙂

Posted on

So Docs 2 CR1 and iFix 1 is not playing ball

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.