Installing the Application for the first time¶
Log into the WebSphere Integrated Solutions Console (ISC) for your IBM Connections Environment.
Navigate to Applications \ Application Types \ Websphere enterprise applications and select "Install".
Locate the "isw-connections-ccm.ear" file on your local file system and select Next.
Select Fast Path and select Next.
Step 1: Leave the default values, update the Application Name if required, and select "Next".
Step 2: Confirm Installation on UtilCluster and WebServer1 then select "Next".
Step 3: Leave the default values and select "Next".
Step 4: Check summary and Complete installation.
Save the master configuration once complete.
Updating the Web Server Plug-in¶
The procedure in this section may or may not be required depending on the configuration of your Connections environment.
In the ISC, navigate to Servers \ Server types \ Web servers.
Select the web server, and click "Generate Plug-in". (If your environment has multiple web servers, you should be able to select them all for this step.)
When the above step completes, select the web server again, and click "Propagate Plug-in". (If your environment has multiple web servers, you should be able to select them all for this step.)
Configuring the Application¶
Without a licence applied, the application can only be used in test mode, where files and folders are reported but not actually migrated.
When requesting a licence you will need to supply:
- The domain name used to access the application in the browser.
- For limited (demo) licences: The community UUIDs that will be allowed to migrate their files.
After receiving your key, you will need to create
name space bindings
for CMM Migrator using the exact values provided by the Huddo team.
All licenced installs require
Limited licences also require
|Binding identifier +
Name in name space...
||Licence key string
||Comma delimited list of community ids without white space
You may follow the steps below for how to create name space bindings.
In the ISC, navigate to Environment \ Naming \ Name space bindings.
Select the "Cell" scope, then click "New".
Set the binding type to "String", then click "Next".
Set both the "Binding identifier" and "Name in name space" fields to "iswCCMLicenceKey". Enter your licence key in the "String value" field.
Click "Next", then click "Finish", then save the master configuration. Repeat these steps for
In the ISC, select the "isw-connections-ccm" application from the list
Navigate to Configuration \ Detail Properties \ Security role to user/group mapping
Select the AdminUsers role and Map users/groups per your requirements. It is suggested that only one or a select group of users are given access to this application.
Select "OK" and save the changes to the configuration.
Start the application by checking the select box for it from the list and selecting "Start".
Updating the Application¶
This part of the document only applies if you have been provided with a new version of the application for the purpose of fixing bugs or adding features.
Log into the ISC for your IBM Connections Environment.
Navigate to Applications \ Application Types \ Websphere enterprise applications.
Select the "isw-connections-ccm" application from the list, and click "Update".
Using the default option ("Replace the entire application"), select the new "isw-connections-ccm.ear" file, and click "Next".
Click "Next" at the bottom of each subsequent screen, leaving all options at the default, then click "Finish" upon reaching the "Step 3: Summary" stage.
After clicking "Finish", there will be some delay while the next screen fills in. Click the "Save" link when it appears.
Depending on your WebSphere configuration, the nodes may synchronize immediately or there may be some delay (typically up to 1 minute) while they synchronize in the background. Changes to the application only take effect after nodes have synchronized.
After updating the application and synchronizing nodes, and before using the application again, any users of the application should clear their web browser cache to ensure that changes to client-side files take effect. It is only necessary to clear the cache or "temporary internet files". Clearing cookies or logins is unnecessary.