Migration of Activities to Kudos Boards¶

As part of the installation process for Kudos Boards you can run the migration service to move the existing Activities into Kudos Boards.

Process Overview¶

This service will:

access Activities data in the existing Connections SQL database
process the Activity into a Board
get file attachments and long descriptions not in SQL database via the Activities API
write Boards data into the Component Pack mongo database
write file attachments into S3 storage

Ensure you have updated the following variables as applicable in your boards.yaml file downloaded previously

	Example	Description
`CONNECTIONS_URL`	`httsp://connections.example.com`	URL of your Connections environment
`API_GATEWAY`	`https://[CONNECTIONS_URL]/api-boards`	URL of the Boards API. Used by files attached to a board. URL.
`CONNECTIONS_ACTIVITIES_ADMIN_USERNAME`	`connectionsadmin`	Credentials for user with `admin` role on the Activities application. See `ISC` => `Applications` => `Activities` => `Security role to user mapping`
`CONNECTIONS_ACTIVITIES_ADMIN_PASSWORD`	`adminpassword`	Password for the Activities administrator
`CONNECTIONS_DB_TYPE`	`db2` or `mssql` or `oracle`	SQL database type hosting Activities.
`CONNECTIONS_DB_HOST`	`dbserver.company.com`	SQL Server hostname
`CONNECTIONS_DB_PORT`	`50000` or `1433` or `1531`	SQL Server connection port
`CONNECTIONS_DB_USER`	`dbuser`	SQL Server user name
`CONNECTIONS_DB_PASSWORD`	`dbpassword`	SQL Server user password
`CONNECTIONS_DB_SID`	`DATABASE`	SQL Server SID Note: applicable to Oracle
`CONNECTIONS_DB_DOMAIN`	`domain`	SQL Server connection string Note: applicable to Microsoft SQL
`CONNECTIONS_DB_CONNECT_STRING`	`HOSTNAME=<host>;PROTOCOL=...` or `<host>:<port>/<sid>`	SQL Server connection string Note: Optional Default is built from other values. Only applicable to DB2 and Oracle
`PROCESSING_PAGE_SIZE`	`10` (default)	Number of Activities to process simultaneously. Value must not exceed the connection pool size supported by the SQL database
`PROCESSING_LOG_EVERY`	`50` (default)	The migration process logs every 50 Activities completed
`IMMEDIATELY_PROCESS_ALL`	`false` (default)	Process ALL Activities on service startup.
`COMPLETE_ACTIVITY_AFTER_MIGRATED`	`false`	Mark the old Activity data as complete
`CREATE_LINK_IN_ACTIVITY_AFTER_MIGRATED`	`false`	Create link to new Board in old Activity

Deploy Helm Chart¶

Please deploy the following chart with the same configuration boards.yaml file used to deploy the kudos-boards chart

helm upgrade kudos-boards-activity-migration https://docs.kudosapps.com/assets/config/kubernetes/kudos-boards-activity-migration-3.0.0.tgz -i -f ./boards.yaml --namespace boards --recreate-pods

Migrate Activities¶

The migration interface is accessible at https://[BOARDS_URL]/app/admin/migration to select which Activities to migrate (ie ignore completed/deleted). For some explanation of the interface, see Activity Migration User Interface.

You can also set the env.IMMEDIATELY_PROCESS_ALL if you wish to migrate every Activity without the UI.

Logs¶

You can check the pod logs for the kudos-boards-activity-migration to see progress of the running migration

For example

Example

After Migration Complete¶

The Migration service can be removed. Please use the following command
```
helm delete kudos-boards-activity-migration --purge
```
Turn off the Activities application in WebSphere ISC