IBM Connections CCM downloads via IHS syntax

It’s important to configure IHS to handle downloading of files. I have seen customer environments fail due to out or memory conditions when WAS handles the downloading of files which is not it’s primary role.

Configuring IHS downloads for CCM always stumps me so for once I will write it down in the form of this blog. A frustration is that IBM’s Connections Knowledge Center fails, with each version of Connections, to provide an easy to follow guide. It should only take about 30 minutes to do this but inevitably it takes longer due to poor documentation.

My current project is on Windows so the paths below will differ on *nix.

You need to update httpd.conf as follows.

Alias /library_content_cache “D:/IBM/Connections/data/shared/ccmcache”

<Directory “D:/IBM/Connections/data/shared/ccmcache”>
Order Deny,Allow
Deny from all
Allow from env=REDIRECT_LIBRARIES_CONTENT
</Directory>

<Location /dm>
IBMLocalRedirect On
IBMLocalRedirectKeepHeaders X-LConn-Auth,Cache-Control,Content-Type,Content-Disposition,Last-Modified,ETag,Content-Language,Set-Cookie,Title,X-UA-Compatible
SetEnv LIBRARIES_CONTENT true
</Location>

RequestHeader append LIBRARIES_CONTENT true

Now you need to update fncs-sitePrefs.properties

The documentation says you need to update D:\IBM\Connections\FNCS\configure\explodedformat\fncs\WEB-INF\classes\fncs-sitePrefs.properties with the following

anonymousAccessEnabled=true
enablePropertySheetTemplateMinMax=true
cdhc_isEnabled=true
cdhc_urlPath=/library_content_cache
cdhc_rootPath=D:/IBM/Connections/data/shared/ccmcache
cdhc_guardHeader=LIBRARIES_CONTENT
fncsServerURL=http://connections.collaborationben.com
fncsServerURLSecure=https://connections.collaborationben.com
icURI=https://connections.collaborationben.com

This is all good an well but these values will not make their way into the application unless you redeploy it which is a pain. Michael Urspringer provided a nice work around by adding the values to D:\IBM\WebSphere\AppServer\profiles\AppSrv01\installedApps\Cell01\navigator.ear\fncs.war\WEB-INF\classes\fncs-sitePrefs.properties which will, after a CCMCluster restart, apply the changes circumnavigating deploying the application.

You need to make sure that the above file and D:\IBM\Connections\FNCS\configure\explodedformat\fncs\WEB-INF\classes\fncs-sitePrefs.properties are the same in case you redeploy the application which will over write the same file in navigator.ear.

There was a bit of trial and error to get the correct syntax in fncs-sitePrefs.properties. The value for cdhc_rootPath did not like “” nor did it like backwards slashes as detailed in various IBM documents.

Advertisements

Error accessing Sametime SIP Proxy Registrar in SSC – part 2

Following on from Error accessing Sametime SIP Proxy Registrar in SSC I did indeed come across the same problem when building the customer’s production servers. This time I raised a PMR and it seems that it is known about though I only know if it is a possible match for HF#OHAH-9VMHYR. I sent IBM all the instances I had of ProxyRegCommon.jar on the SSC and combined PR & CF and they told me that the one I want to use is the one in bold below and that I should replace all other instances with it.

SSC

# locate ProxyRegCommon.jar

/opt/IBM/WebSphere/AppServer/profiles/STSCDMgrProfile/optionalLibraries/proxy-registrar/ProxyRegCommon.jar
/opt/IBM/WebSphere/AppServer/systemApps/isclite.ear/sipadmin.war/WEB-INF/lib/ProxyRegCommon.jar

# cp /opt/IBM/WebSphere/AppServer/systemApps/isclite.ear/sipadmin.war/WEB-INF/lib/ProxyRegCommon.jar /home/ldap/BenW/ProxyRegCommon.jar_from_sipadmin_war
# cp /opt/IBM/WebSphere/AppServer/profiles/STSCDMgrProfile/optionalLibraries/proxy-registrar/ProxyRegCommon.jar /opt/IBM/WebSphere/AppServer/systemApps/isclite.ear/sipadmin.war/WEB-INF/lib/

On SIP PR & CF

# locate ProxyRegCommon.jar
/opt/IBM/WebSphere/AppServer/lib/ext/ProxyRegCommon.jar

# cp /opt/IBM/WebSphere/AppServer/lib/ext/ProxyRegCommon.jar /home/ldap/BenW/

# scp BenW@ssc_hostname:/opt/IBM/WebSphere/AppServer/profiles/STSCDMgrProfile/optionalLibraries/proxy-registrar/ProxyRegCommon.jar /opt/IBM/WebSphere/AppServer/lib/ext/

Start the deployment manager, node agent and STMediaServer.

The problem is no more.

IBM Connections 5.5 DB2 migration fails due to full transaction logs

During a database transfer from Connections 4.5 CR05 (DB2 10.1) to Connections 5.5 (DB2 10.5.0.7) I ran across a number of transfer failures using the tool. After a bit of digging such as looking at db2diag.log and DB2 Technotes I found the problem was that the DB2 transaction logs were being filled. Below are some example errors.

[02/03/16 16:33:26.659 CET] com.ibm.db2.jcc.am.SqlTransactionRollbackException: Error for batch element #1: DB2 SQL Error: SQLCODE=-1476, SQLSTATE=40506, SQLERRMC=-964, DRIVER=3.69.49
[02/03/16 16:33:26.659 CET] com.ibm.db2.jcc.am.SqlException: [jcc][103][10843][3.69.49] Non-recoverable chain-breaking exception occurred during batch processing.  The batch is terminated non-atomically. ERRORCODE=-4225, SQLSTATE=null
[02/03/16 16:33:26.659 CET] error.executing.transfer
err.dbtransfer.exception.labelclass com.ibm.db2.jcc.am.BatchUpdateException: [jcc][t4][102][10040][3.69.49] Batch failure.  The batch was submitted, but at least one exception occurred on an individual member of the batch.
Use getNextException() to retrieve the exceptions for specific batched elements. ERRORCODE=-4229, SQLSTATE=null
com.ibm.db2.jcc.am.BatchUpdateException: [jcc][t4][102][10040][3.69.49] Batch failure.  The batch was submitted, but at least one exception occurred on an individual member of the batch.
Use getNextException() to retrieve the exceptions for specific batched elements. ERRORCODE=-4229, SQLSTATE=null

Db2diag.log

EDUID   : 1580                 EDUNAME: db2agent (METRICS) 0
FUNCTION: DB2 UDB, data protection services, sqlpgResSpace, probe:6666
MESSAGE : ZRC=0x85100009=-2062548983=SQLP_NOSPACE
“Log File has reached its saturation point”
DIA8309C Log file was full.

In http://www-01.ibm.com/support/docview.wss?uid=swg21623212 it suggests increasing the sizes for LogFilSiz, LogPrimary, and LogSecond. On the second attempt changing these settings I found values that worked (for me).

db2 update db cfg for metrics using LOGFILSIZ 10000
db2 update db cfg for metrics using LOGPRIMARY 80
db2 update db cfg for metrics using LOGSECOND 40
db2stop
db2start

I had to increase the default values for Metrics and Profiles as they contain a lot of data.

You may want to reset the values after migration so you do not impact disk space.