1. General Information – explains how fixes will be released for Connections 3.0.1 via CR (Component Refresh)
2. Customization and Modifications – an overview of how to customize Connections, what modifications are supported, and any implications they have on fixes/future upgrades
3. List of the Latest CR’s – easily check if you have the latest fixes against this list
4. Instructions on applying Component Refresh (CR) updates – helpful tips for applying updates.
The technote contains many useful links to additional information in each section.
The APAR Document (login required) is blank, but this seems to fix the issue where the Mobile App responded with “the July 2011 mobile fix needs to be installed†when it was actually installed on the server already. Thanks to Chris Whisonant for help figuring out at least one of the fixed issues.
Last week the Android client for IBM Connections was released in to the Android Market, over the last 24 hours the Blackberry and iOS apps found their way in to their respective app stores as well.
Remember you need to install the Mobile Fix on your IBM Connections 3.0.1 Servers before you can use the clients.
The IBM clients limit you to connecting to one Connections instance which should cover most people, if you need to connect to multiple Connections instances you can always check out iWildFire which supports multiple instances.
The Mobile Update to enable the Android Mobile App (iOS and Blackberry apps still waiting approval in their app stores) is now available from Fix Central.
When using DB2 you might want to use the Control Center GUI to query or manage a database that resides on a remote machine, took me a little time to work out and I promised others I would share this. I am sure there is more then one way to accomplish this, your mileage may vary.
Before you begin you need to collect the following information
Fully Qualified Hostname where the DB2 database resides
Services file entry for the database – this will include the instance name and port number (default is 50000, but could be different depending on your DB2 Configuration
The Database Name to connect to
The operating system of the DB2 Install
Username & Password to connect to the Database
You can get this information from your friendly Database administrator or find it yourself. If you have access to the physical machine where DB2 is installed you can get the instance name and port number from the services file on that machine.
Before you begin edit the Services file on the machine with the DB2 Client, simply cut and paste the entry from the DB2 host machine for example this would represent two unique DB2 instances
db2_LC3 50000/tcp DB2_LC25 60000/tcp
From the DB2 Control center (on the client machine) launch the Configuration Assistant
From the ‘Selected’ dropdown choose Add a Database Using Wizard
Select Manually configure a connections to a database and click Next
Select TCP/IP as the communications protocol
Enter the FQHN of the DB2 server and the Service name (that you added to the services file above) use the “Retrieve†button to fill in the port number (from the services file)
Fill in the database name (in this example I am connecting to an IBM Connections Profiles DB named PEOPLEDB. Assign an Alias – Aliases must be unique, for example I might connect to a production and test PEOPLEDB, the aliases must be unique (aliases are also limited to 8 characters the first of which must be alpha). Optionally you can add a descriptive comment.
Simply accept the defaults on this screen
Use the dropdown to fill in your operating system, and fill in the Instance Name, the instance name is the same value you put in the System file
Fill in the system name using the same value as instance name above, the other fields should already be filled in
Keep the default of Use authentication value in server’s DMB Configuration (unless you are using a different authentication method). Click Finish when you are done
Click on Test Connection to verify your work
Enter your database username and password (username is most likely LCUSER for an IBM Connections database) and click Test Connections
If you see this you have completed the setup successfully, if not go back and double check your work
I ran in to this issue yesterday, and thanks to Luis Benitez and David Hay for steering me in the right direction.
This problem on occurs in multi-node deployments of IBM Connections, and fortunately there is a fix out there for both 3.0 and 3.0.1.
“Problem Users are receiving multiple copies of email digests sent from scheduled daily/weekly task ‘EmailDigestDelivery’.
Problem description The problem occurs on a multi-node deployment. The bug is in the load balancing (same scheduled delivery tasks is running in parallel on the different nodes) of scheduled tasks logic. Apply this iFix to address the load balancing problem in ‘News’ application. “
Yesterday I was working with a fresh install of Tivoli Directory Integrator 7.0 Fix Pack 5 (the required version for IBM Connections), every time I tried to run an assembly line I was faced with this message
Looking at the log I saw this error ‘api.remote.naming.port’ : ‘1099null’
Searching around I find suggestions to check the Default.tdiserver file in the Workspace directory, but the value there looked correct.
“Tivoli Directory Integrator Configuration Editor port issue: If you see the message "Invalid value specified for ‘api.remote.naming.port’ " when working with the Tivoli Directory Integrator Configuration Editor, you can resolve the issue by manually setting the api.remote.naming.port in the solution.properties file located in the <TDI_solution _directory>.â€
Sure enough when I looked in my solution.propertied I found the bad entry
Once I removed the ‘null’ appended to the port and restarted TDI, the default server started right up
If you are running Notes 8.5.2 with Fix Pack 2, apparently a fix to the Connections code in Fix Pack 2, broke the Files and Status plugins, from the technote:
