When you have completed the upgrade, you will need to complete the following actions:

Update all CAST Management Studio connection profiles to allow connection to the same schemas on the new database/instance/host

from 8.3.40

Use tools\ConnectionProfile\CAST-Connection-Profile-Configuration.py (see Using the CAST-Connection-Profile-Configuration.py file).

up to 8.3.39

Open the following file with a text editor:

%appdata%\CAST\CAST\<version>\cast-ms.connectionProfiles.pmx

Modify in the relevant <connectionprofiles.ConnectionProfilePostgres> tag, the following attributes:

• the host="xxx" to change the source <xxx> host name to the target <xxx> host name. Note that if the instances are located on the SAME host, there is no need to do this.
• the port="xxxx" to change the source port="xxxx" to the target port="xxxx". Note that if you are using a custom port number for your CSS/PostgreSQL instance, you should enter it here.
• the name= attribute in the relevant <connectionprofiles.ConnectionProfilePostgres> tag to ensure there is no confusion as to which CAST Storage Service/PostgreSQL users are connecting to (this is optional).

When the changes have been made, save the file.

<?xml version="1.0" encoding="UTF-8"?>
<document version="1.1">
	<lot symbol="connectionProfiles" label="Connection profiles" requires="connectionprofiles:2.1;pmcgeneral:3.1;system:1.0">
		<connectionprofiles.ConnectionProfiles>
			<connectionProfiles>
				<connectionprofiles.ConnectionProfilePostgres entry="uuid:0f76b31a-e440-4210-af8b-6c16a4f05bec" name="v8325_mngt on CastStorageService _ MySourceServer:2282" user="operator" password="CRYPTED2:90B1A6EC1618661401B724DB5AC34595" schema="v8325_mngt" host="MySourceServer" port="2282"/>
				</connectionProfiles>
			</connectionprofiles.ConnectionProfiles>
	</lot>
</document>

<?xml version="1.0" encoding="UTF-8"?>
<document version="1.1">
	<lot symbol="connectionProfiles" label="Connection profiles" requires="connectionprofiles:2.1;pmcgeneral:3.1;system:1.0">
		<connectionprofiles.ConnectionProfiles>
			<connectionProfiles>
				<connectionprofiles.ConnectionProfilePostgres entry="uuid:0f76b31a-e440-4210-af8b-6c16a4f05bec" name="v8325_mngt on CastStorageService _ MyTargetServer:2282" user="operator" password="CRYPTED2:90B1A6EC1618661401B724DB5AC34595" schema="v8325_mngt" host="MyTargetServer" port="2282"/>
				</connectionProfiles>
			</connectionprofiles.ConnectionProfiles>
	</lot>
</document>

Update connection profiles for CAST Server Manager, CAST Enlighten and CAST Report Center

CAST Server Manager, CAST Enlighten and CAST Report Center use a legacy type of connection profile that is difficult to edit manually. The simplest method therefore is to run each exe and either:

• manually modify the connection settings in the GUI
• create new connection profiles from scratch

When the database name is different from postgres, the host field must follow format : 'LIBPQ:<HOST>:<PORT>,<DATABASE>', and the port field is not used.

Update cms_inf_store_css table in _MNGT schema

Run the following query:

• where <prefix> is the schema prefix for the schemas that you have moved to the target server
• where target <database> name is 'postgres'
• where <port> is the port used by your target instance
• and where <targetserver> is the host name of the target server.

set search_path = <prefix>_mngt;
update cms_inf_store_css set port=<port>, host='<targetserver>:<port>', object_name='<targetserver>:<port>';

• when target database name is different from 'postgres':

set search_path = <prefix>_mngt;
update cms_inf_store_css set port=<port>, host='LIBPQ:<targetserver>:<port>,<database>', object_name='<targetserver>:<port>,<database>';

• Start a command prompt (cmd.exe) as an administrator (search for "CMD" and then right click and select "Run as administrator")
• Create a Windows user called "postgres" and add a password (Welcome2017!):

net /user postgres Welcome2017! /add

• Now stop the two instances, for example:

net stop CastStorageService2
net stop CastStorageService3

• Now open a text editor as an administrator (right click and select "Run as administrator") and edit the following files by changing the authentification method to trust. Assuming you have installed the CAST Storage Service with default settings these files will be located here:
  • %PROGRAMFILES%\CAST\CASTStorageService2\db_data\pg_hba.conf
  • %PROGRAMFILES%\CAST\CASTStorageService3\db_data\pg_hba.conf

//BEFORE
# TYPE  DATABASE        USER            ADDRESS                 METHOD

# IPv4 local connections:
host    all         all         127.0.0.1/32          md5
# IPv6 local connections:
host    all         all         ::1/128               md5
host    all         all         ::1/0                 md5
# This line allows any client to connect to the server. Doing so, we don't need to manage it anymore.
host    all         all         0.0.0.0/0      		  md5
 
//AFTER
# TYPE  DATABASE        USER            ADDRESS                 METHOD

# IPv4 local connections:
host    all         all         127.0.0.1/32          md5	trust
# IPv6 local connections:
host    all         all         ::1/128               md5	trust
host    all         all         ::1/0                 md5	trust
# This line allows any client to connect to the server. Doing so, we don't need to manage it anymore.
host    all         all         0.0.0.0/0      		  md5	trust

• Grant specific Windows permissions to the "postgres" Windows user on the CSS2 and CSS3 data folders. Assuming you have installed the CAST Storage Service with default settings these data folders will be located here:
  • %PROGRAMFILES%\CAST\CASTStorageService2\db_data
  • %PROGRAMFILES%\CAST\CASTStorageService3\db_data

icacls %PROGRAMFILES%\CAST\CASTStorageService2\db_data /grant postgres:(CI)(OI)F /T
icacls %PROGRAMFILES%\CAST\CASTStorageService3\db_data /grant postgres:(CI)(OI)F /T

• Close the existing command prompt and start a new command prompt (cmd.exe) running it as the Windows postgres user - enter the password when prompted:

runas /user:postgres "cmd.exe"

• Set the PATH variable to include the "bin" folder of the CSS3 installation folder:

set path=%path%;%PROGRAMFILES%\CAST\CASTStorageService3\bin

• Create a new folder "upgradeCSS" in %TEMP% to store files generated during the upgrade process, assign specific Windows permissions to the new "postgres" Windows user on this folder and then change focus into this new folder:

mkdir %temp%\upgradeCSS
icacls %temp%\upgradeCSS /grant postgres:(CI)(OI)F /T
cd %temp%\upgradeCSS

• Run the upgrade process as follows:

pg_upgrade -d %PROGRAMFILES%\CAST\CASTStorageService2\db_data -D %PROGRAMFILES%\CAST\CASTStorageService3\db_data -b %PROGRAMFILES%\CAST\CASTStorageService2\bin -B %PROGRAMFILES%\CAST\CASTStorageService3\bin -p portCSS2 -P portCSS3

• When the upgrade process has completed, ensure you remove the trust authentication method in the following two files:
  • %PROGRAMFILES%\CAST\CASTStorageService2\db_data\pg_hba.conf
  • %PROGRAMFILES%\CAST\CASTStorageService3\db_data\pg_hba.conf
• Now start the two CAST Storage Service servers, for example:

net start CastStorageService2
net start CastStorageService3

Edit the authentication method in the pg_hba.conf file for your source and target instances; for example using vi:

sudo vi /opt/PostgreSQL/9.2/data/pg_hba.conf
 
and:
 
sudo vi /opt/PostgreSQL/9.6/data/pg_hba.conf

Switch all authentication methods to trust in both files and save the files in vi.

Create a .pgpass file (this file can contain passwords to be used if the upgrade process requires a password for connection (and no password has been specified otherwise) as follows:

echo hostname92:port92:database92:postgres:Postgrespassword> ~/.pgpass
echo hostname96:port96:database96:postgres:Postgrespassword>> ~/.pgpass

Stop the PostgreSQL instances (you can check the name of the postgres services with the command "sudo systemctl -a | grep -i postgres"), for example: 

sudo systemctl stop postgresql-9.2
sudo systemctl stop postgresql-9.6

Switch to the postgres Linux user using the -u command, and add -i (so that the .pgpass file is read):

sudo -i -u postgres

Set the PATH variable to include the "bin" folder in the PostgreSQL 9.6 installation folder:

PATH=$PATH:/opt/PostgreSQL/9.6/bin

Reload the PostgreSQL configuration (this is required since the pg_hba.conf files have been edited) for both the 9.2 and 9.6 instances:

pg_ctl -D /opt/PostgreSQL/9.2/data reload
pg_ctl -D /opt/PostgreSQL/9.6/data reload

Create a new folder "upgradePostgres" in tmp to store files generated during the upgrade process:

mkdir /tmp/upgradePostgres

Change permissions on the "upgradePostgres" folder:

chmod 777 /tmp/upgradePostgres

Change focus into this "upgradePostgres" folder:

cd /tmp/upgradePostgres_dir

Run the upgrade process as follows:

pg_upgrade -d /opt/PostgreSQL/9.2/data -D /opt/PostgreSQL/9.6/data -b /opt/PostgreSQL/9.2/bin -B /opt/PostgreSQL/9.6/bin -p portCSS2 -P portCSS3

When the upgrade process has completed, ensure you remove the trust authentication method using vi:

sudo vi /opt/PostgreSQL/9.2/data/pg_hba.conf
 
and:
 
sudo vi /opt/PostgreSQL/9.6/data/pg_hba.conf

Start the PostgreSQL instances (you can check the name of the postgres services with the command "sudo systemctl -a | grep -i postgres"), for example: 

sudo systemctl start postgresql-9.2
sudo systemctl start postgresql-9.6

When you have completed the upgrade, you will need to complete the following actions:

Update all CAST Management Studio connection profiles to allow connection to the same schemas on the target instance

from 8.3.40

Use tools\ConnectionProfile\CAST-Connection-Profile-Configuration.py (see Using the CAST-Connection-Profile-Configuration.py file).

up to 8.3.39

Open the following file with a text editor:

%appdata%\CAST\CAST\<version>\cast-ms.connectionProfiles.pmx

Modify in the relevant <connectionprofiles.ConnectionProfilePostgres> tag, the following attributes:

• the host="xxx" to change the source <xxx> host name to the target <xxx> host name. Note that if the instances are located on the SAME host, there is no need to do this.
• the port="xxxx" to change the source port="xxxx" to the target port="xxxx". Note that if you are using a custom port number for your CSS/PostgreSQL instance, you should enter it here.
• the name= attribute in the relevant <connectionprofiles.ConnectionProfilePostgres> tag to ensure there is no confusion as to which CAST Storage Service/PostgreSQL users are connecting to (this is optional).

When the changes have been made, save the file.

<?xml version="1.0" encoding="UTF-8"?>
<document version="1.1">
	<lot symbol="connectionProfiles" label="Connection profiles" requires="connectionprofiles:2.1;pmcgeneral:3.1;system:1.0">
		<connectionprofiles.ConnectionProfiles>
			<connectionProfiles>
				<connectionprofiles.ConnectionProfilePostgres entry="uuid:0f76b31a-e440-4210-af8b-6c16a4f05bec" name="v827_mngt on CastStorageService _ CSS2:2280" user="operator" password="CRYPTED2:90B1A6EC1618661401B724DB5AC34595" schema="v827_mngt" host="CSS2" port="2280"/>
				</connectionProfiles>
			</connectionprofiles.ConnectionProfiles>
	</lot>
</document>

<?xml version="1.0" encoding="UTF-8"?>
<document version="1.1">
	<lot symbol="connectionProfiles" label="Connection profiles" requires="connectionprofiles:2.1;pmcgeneral:3.1;system:1.0">
		<connectionprofiles.ConnectionProfiles>
			<connectionProfiles>
				<connectionprofiles.ConnectionProfilePostgres entry="uuid:0f76b31a-e440-4210-af8b-6c16a4f05bec" name="v827_mngt on CastStorageService _ CSS3:2282" user="operator" password="CRYPTED2:90B1A6EC1618661401B724DB5AC34595" schema="v827_mngt" host="CSS3" port="2282"/>
				</connectionProfiles>
			</connectionprofiles.ConnectionProfiles>
	</lot>
</document>

Update connection profiles for CAST Server Manager, CAST Enlighten and CAST Report Center

CAST Server Manager, CAST Enlighten and CAST Report Center use a legacy type of connection profile that is difficult to edit manually. The simplest method therefore is to run each exe and either:

• manually modify the connection settings in the GUI
• create new connection profiles from scratch

When the database name is different from postgres, the host field must follow format : 'LIBPQ:<<HOST>>:<<PORT>>,<<DATABASE', and the port field is not used.

Update cms_inf_store_css table in _MNGT schema on target instance

When the two instances are located on the SAME host, run the following script to perform the required update:

• where <prefix> is the schema prefix for the schemas that you have moved
• where target <database> name is 'postgres'
• where <targetserver> is the host name of the target server
• where <port> is the port used by your target instance.

set search_path = <prefix>_mngt;
update cms_inf_store_css set port=<port>, object_name='<targetserver>:<port>';

• when target database name is different from 'postgres':

set search_path = <prefix>_mngt;
update cms_inf_store_css set port=<port>, object_name='<targetserver>:<port>,<database>';

Launch the CSS Upgrade Wizard from the Windows Start menu as follows:

When the CSS Upgrade Wizard is launched an initial Welcome page will be displayed. Click Next to continue. The Source Server page will then be displayed:

This page enables you to fill in the connection information for your "source server" - i.e. the machine hosting the CAST Storage Service/PostgreSQL whose schemas will be moved.

Fill in the required fields and then click Next. The Target Server page will then be displayed:

This page enables you to fill in the connection information for your "target server" - i.e. the machine hosting the CAST Storage Service/PostgreSQL that will "receive" the schemas from the source CAST Storage Service/PostgreSQL.

Fill in the required fields and then click Next. The Schema Upgrade Selection page will then be displayed. This page will list all the CAST AIP schemas on the Source Server that are eligible for upgrade to the Target Server. Select the schemas that you want to - place a check mark next to each schema as shown below. You can use the Refresh button (lower right corner) to refresh the list of schemas if required.

Click Next to continue. This next page requires you to input a temporary "Working Folder". This folder will be used to store the selected schemas in file format during the transfer process - please choose a folder with plenty of free space. The folder must also already exist and must be empty.

Click Finish to continue the process. A summary of the upgrade action is the displayed:

Check that the summary of the upgrade action is as you require. Click Upgrade to start the process. On completion a message will be displayed showing you where the log of the entire process is stored:

Please check the log file to ensure there are no failures reported during upgrade. A final page will be displayed - click Finish to terminate the process. Finally, check that the schemas have been correctly moved to the target server using CAST Server Manager.

When you have completed the upgrade, you will need to complete the following actions:

Update all CAST Management Studio connection profiles to allow connection to the same schemas on the new host

Open the following file with a text editor:

%appdata%\CAST\CAST\<version>\cast-ms.connectionProfiles.pmx

Modify in the relevant <connectionprofiles.ConnectionProfilePostgres> tag, the following attributes:

• the host="xxx" to change the source <xxx> host name to the target <xxx> host name. Note that if the two servers are located on the SAME host, there is no need to do this.
• the port="xxxx" to change the source port="xxxx" to the target port="xxxx". Note that if you are using a custom port number for your CSS/PostgreSQL instance, you should enter it here.
• the name= attribute in the relevant <connectionprofiles.ConnectionProfilePostgres> tag to ensure there is no confusion as to which CAST Storage Service/PostgreSQL users are connecting to (this is optional).

When the changes have been made, save the file.

<?xml version="1.0" encoding="UTF-8"?>
<document version="1.1">
	<lot symbol="connectionProfiles" label="Connection profiles" requires="connectionprofiles:2.1;pmcgeneral:3.1;system:1.0">
		<connectionprofiles.ConnectionProfiles>
			<connectionProfiles>
				<connectionprofiles.ConnectionProfilePostgres entry="uuid:0f76b31a-e440-4210-af8b-6c16a4f05bec" name="v8325_mngt on CastStorageService _ MySourceServer:2282" user="operator" password="CRYPTED2:90B1A6EC1618661401B724DB5AC34595" schema="v8325_mngt" host="MySourceServer" port="2282"/>
				</connectionProfiles>
			</connectionprofiles.ConnectionProfiles>
	</lot>
</document>

<?xml version="1.0" encoding="UTF-8"?>
<document version="1.1">
	<lot symbol="connectionProfiles" label="Connection profiles" requires="connectionprofiles:2.1;pmcgeneral:3.1;system:1.0">
		<connectionprofiles.ConnectionProfiles>
			<connectionProfiles>
				<connectionprofiles.ConnectionProfilePostgres entry="uuid:0f76b31a-e440-4210-af8b-6c16a4f05bec" name="v8325_mngt on CastStorageService _ MyTargetServer:2282" user="operator" password="CRYPTED2:90B1A6EC1618661401B724DB5AC34595" schema="v8325_mngt" host="MyTargetServer" port="2282"/>
				</connectionProfiles>
			</connectionprofiles.ConnectionProfiles>
	</lot>
</document>

Update connection profiles for CAST Server Manager, CAST Enlighten and CAST Report Center

CAST Server Manager, CAST Enlighten and CAST Report Center use a legacy type of connection profile that is difficult to edit manually. The simplest method therefore is to open each one and either:

• manually modify the connection settings
• create new connection profiles from scratch

Update server display name for CAST Management Studio

The following action will ensure that the name displayed for the CAST Storage Service in the CAST Management Studio Services view is updated to the new host name:

Run the following query in PGAdmin against the _MNGT table on the target CAST Storage Service/PostgreSQL (i.e. the CAST Storage Service/PostgreSQL to which you have moved the schemas): replacing <server B> with the target CAST Storage Service/PostgreSQL name:

select 'update ' || table_schema || '.' || table_name || ' set object_name = 
''<server B>'' where host = ''<server B>'' ;'
from information_schema.tables
where table_name = 'cms_inf_store_css'

The above query will produce update query scripts for every CAST AIP schema on the target CAST Storage Service/PostgreSQL to update the host names in the cms_inf_store_css table. For example:

Copy each update query script you need to run (these should cover all the CAST AIP schemas you have moved to the target CAST Storage Service/PostgreSQL with the CSS Upgrade Wizard) into a new PGAdmin query window, as follows:

Run the query.