Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Redirect
visiblefalse
locationCAST Storage Service - Moving existing schemas to new hosts

Panel

On this page:

Table of Contents

Target audience:

  • CAST AI Administrators


Info

Summary: this page provides information about how to upgrade to CAST Storage Service 3 from CAST Storage Service 2.

Introduction

If you have CAST AIP schemas installed on CAST Storage Service (CSS) 2 you can upgrade these schemas to run on CAST Storage Service 3. This upgrade process can be completed using the following methods:

  1. Using the CSS Upgrade Wizard, a tool provided in the CAST AIP 8.3.x installation, located in: <CAST AIP installation Directory>\CSSAdmin\CSSUpgrade.exe.
  2. Using the backup and restore tools provided with CAST AIP specifically for the CAST Storage Service. This method can only be run from Windows, but it can be used for CAST Storage Service installed on Windows or PostgreSQL installed on Linux.
  3. Using the PostgreSQL pg_upgrade tool from the new release of the DBMS - this tool allows data stored in the PostgreSQL data files to be upgraded to a later PostgreSQL release. This method can be run either from Windows or from Linux.
Info

Note that upgrades from CAST Storage Service 1 are not covered by this documentation.

Anchor
method1
method1
Method 1: using the CSS Upgrade Wizard

This method functions for installations of CSS on Windows and PostgreSQL on Linux but can only be run from Windows. The upgrade process uses the CSS Upgrade Wizard, provided as part of the CAST AIP ≥ 8.3.x, and involves a fully automated process of dumping the required schemas to file and then restoring the dumps on the new host. The CAST Storage Services/PostgreSQL do not need to be installed on the same host, and both can be remote to the machine on which you are running the CSS Upgrade Wizard.

Prerequisites

RequiredDescription
(tick)Ensure that no CAST AIP applications are using the CSS2 (or PostgreSQL 9.2 for Linux) and CSS3 (or PostgreSQL 9.6 for Linux).
(tick)Ensure that you are using the CSS Upgrade Wizard provided with CAST AIP 8.3.x.
(tick)

You must not use "localhost" in the Host field in the CAST Upgrade Wizard for the Source and Target Servers even if the servers are located on the current machine.

Source Server

For the Source Server, the value entered in the Host field in the CAST Upgrade Wizard must match the value defined for the Host field in the Management Service editor in the CAST Management Studio:

If you have used "localhost" in the CAST Management Studio to define a connection to the Management Service, you MUST update this to use either the server's netbios name or its IP address.

Target Server

In normal circumstances, you will not yet have used the CAST Management Studio with the CAST Storage Service 3, as such, there will be no connection profile to compare. Please use either the server's netbios name or its IP address.

Upgrade action

Expand

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

Info
Note that if the CSS Upgrade Wizard is not visible in the start menu, it is located here: <CAST AIP installation Directory>\CSSAdmin\CSSUpgrade.exe.
  • 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 2 whose schemas will be upgraded and transferred to CAST Storage Service 3:
HostThe host name of the source CAST Storage Service 2 as defined in the Host field in the Management Service editor in the CAST Management Studio (see prerequisites above).
PortThe port number used for the source CAST Storage Service 2. This should be set to 2280.
DatabaseThe PostgreSQL database - please leave this set to postgres.
UserPlease leave this set to operator.
PasswordEnter the password for your operator user.
  • 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 3 that will "receive" the schemas from the source CAST Storage Service 2.
HostThe host name of the source CAST Storage Service 3. You can also use its IP address.
PortThe port number used for the source CAST Storage Service 3. This should be set to 2282.
DatabaseThe PostgreSQL database - please leave this set to postgres.
UserPlease leave this set to operator.
PasswordEnter the password for your operator user.
  • Fill in the required fields and then click Next - note that the port numbers for CSS2 and CSS3 are different by default - make sure you enter the correct numbers.
  • The Schema Upgrade Selection page will then be displayed. This page will list all the CAST AIP schemas on the Source Server (CAST Storage Service 2) that are eligible for upgrade to the target CAST Storage Service 3.
  • Select the schemas that you want to upgrade and transfer to your CAST Storage Service 3 - 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 upgrade 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 upgraded and transferred to the CAST Storage Service 3 using CAST Server Manager.

Post upgrade actions

Expand

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 CSS3 

Open the following file with a text editor:

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

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

  • the host="CSS2" to change the source <CSS2> host name to the target <CSS3> host name. Note that if the CSS2 and CSS3 servers are located on the SAME host, there is no need to do this.
  • the port="2280" to change the source port="2280" (for CSS2) to the target port="2282" (for CSS3). 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 users are connecting to (this is optional).

When the changes have been made, save the file.

Code Block
languagexml
titleBefore update
<?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>


Code Block
languagexml
titleAfter update
<?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 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 (i.e. the CAST Storage Service to which you have moved the schemas): replacing <server B> with the target CAST Storage Service name:
Code Block
languagesql
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 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 with the CSS Upgrade Wizard) into a new PGAdmin query window, as follows:

  • Run the query.

Method 2: using CAST Storage Service backup and restore tools

This method functions for installations of CSS on Windows and PostgreSQL on Linux but can only be run from Windows. The process involves dumping the required schemas to file and then restoring the dumps on the new host. The CAST Storage Services/PostgreSQL do not need to be installed on the same host, and both can be remote to the machine on which you are running the CAST Storage Service backup/restore tools.

Prerequisites

RequiredDescription
(tick)Ensure that no CAST AIP applications are using the CSS2 (or PostgreSQL 9.2 for Linux) and CSS3 (or PostgreSQL 9.6 for Linux).
(tick)Ensure that you are using the backup and restore tools provided with CAST AIP 8.3.x.

Upgrade action

Please refer to the documentation in CAST Storage Service - Maintenance activities for more information:

  • You can use the CSSbackup or CSSBackupAll tools to perform the backup
  • You can use the CSSRestore or CSSRestoreAll tools to perform the restore on the new host
  • Ensure you backup the following CAST AIP schemas for each Application you are moving to the new host:
    • CAST Analysis Service (local)
    • CAST Dashboard Service (central)
    • CAST Management Service (mngt)
    • Any associated CAST Measurement Service (measure)

Post upgrade actions

Expand

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 CSS3 

Open the following file with a text editor:

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

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

  • the host="CSS2" to change the source <CSS2> host name to the target <CSS3> host name. Note that if the CSS2 and CSS3 servers are located on the SAME host, there is no need to do this.
  • the port="2280" to change the source port="2280" (for CSS2) to the target port="2282" (for CSS3). 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 users are connecting to (this is optional).

When the changes have been made, save the file.

Code Block
languagexml
titleBefore update
<?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>


Code Block
languagexml
titleAfter update
<?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 to allow connection to the same schemas on CSS3 

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

Update cms_inf_store_css table in _MNGT schema on CSS3

If the CSS2 and CSS3 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 to CSS3 and where <CSS3> is the host name of the CSS3 server. This will change the port number from 2280 to 2282 and ensure that the display name for the CAST Storage Service in the CAST Management Studio Services view is correct:

Code Block
languagesql
set search_path = <prefix>_mngt;
update cms_inf_store_css set port=2282, object_name='<CSS3>:2282';

If the CSS2 and CSS3 servers are located on DIFFERENT hosts, run the following query instead, where <prefix> is the schema prefix for the schemas that you have moved to CSS3 and where <CSS3> is the host name of the CSS3 server. This will update the port number, host name and ensure that the display name for the CAST Storage Service in the CAST Management Studio Services view is correct:

Code Block
languagesql
set search_path = <prefix>_mngt;
update cms_inf_store_css set port=2282, host='<CSS3>', object_name='<CSS3>:2282';


Info

Note:

  • If you have moved more than one set of schemas from CSS2 to CSS3, you will need to repeat the above queries for each <prefix>_mngt you have moved.
  • If you are using a custom port number for your target instance, you should enter it in the query in place of 2282 (for a CSS3 instance).


Method 3: using pg_upgrade on host server

This method functions for installations of CSS on Windows and PostgreSQL on Linux, and assumes that the two CAST Storage Services are already installed on the same host. The upgrade process uses the pg_upgrade tool from the new release of the DBMS and will copy the data from the old CAST Storage Service/Postgres instance to the new, leaving the old CAST Storage Service/PostgreSQL instance in full working order.

Prerequisites

RequiredDescription
(tick)Ensure the CSS2 (or PostgreSQL 9.2 for Linux) and CSS3 (or PostgreSQL 9.6 for Linux) are installed on the same host server - this is highly recommended for performance reasons.
(tick)

The upgrade process will leave the old CAST Storage Service in place and unchanged, however, CAST does recommend that you backup any CAST AIP schemas you may have on this server using the CAST tools. See CAST Storage Service - Maintenance activities.

(tick)Ensure that no CAST AIP applications are using the CSS2 (or PostgreSQL 9.2 for Linux) and CSS3 (or PostgreSQL 9.6 for Linux).

For CAST Storage Service installed on Windows

Expand
  • 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!):
Code Block
languagetext
net /user postgres Welcome2017! /add
  • Now stop the two CAST Storage Service servers:
Code Block
languagetext
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
Code Block
languagetext
//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
Code Block
languagetext
icacls %PROGRAMFILES%\CAST\CASTStorageService2\db_data /grant postgres:(CI)(OI)F /T
icacls %PROGRAMFILES%\CAST\CASTStorageService3\db_data /grant postgres:(CI)(OI)F /T


Info

This will grant the following permissions to the Windows postgres user:

  • (OI)(CI) - This folder, subfolders, and files.
  • F - Full access (Edit_Permissions+Create+Delete+Read+Write)
  • /T - Traverse all subfolders to match files/directories. This will apply permission changes to all subfolders whether or not they are set to inherit permissions from the parent.

See https://ss64.com/nt/icacls.html for more information.

  • 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:


Code Block
languagetext
runas /user:postgres "cmd.exe"
  • Set the PATH variable to include the "bin" folder of the CSS3 installation folder:
Code Block
languagetext
set path=%path%;%PROGRAMFILES%\CAST\CASTStorageService3\db_data\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:
Code Block
languagetext
mkdir %temp%\upgradeCSS
icacls %temp%\upgradeCSS /grant postgres:(CI)(OI)F /T
cd %temp%\upgradeCSS
  • Run the upgrade process as follows:
Code Block
languagetext
pg_upgrade -d %PROGRAMFILES%\CAST\CASTStorageService2\db_data -D %PROGRAMFILES%\CAST\CASTStorageService3\db_data -b %PROGRAMFILES%\CAST\CASTStorageService2\db_data\bin -B %PROGRAMFILES%\CAST\CASTStorageService3\db_data\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:
Code Block
languagetext
net start CastStorageService2
net start CastStorageService3


For PostgreSQL installed on Linux

Expand
  • Edit the authentification method in the pg_hba.conf file for both PostgreSQL 9.2 and 9.6: /opt/PostgreSQL/9.*/data/pg_hba.conf, for example using vi:
Code Block
languagebash
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:

    • 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:
Code Block
languagebash
echo hostname92:port92:database92:postgres:Postgrespassword> ~/.pgpass
echo hostname96:port96:database96:postgres:Postgrespassword>> ~/.pgpass

 

Info

The syntax of a .pgpass file should be:

  • hostname:port:database:username:password

Therefore:

hostname92 / hostname96Enter the Linux hostname for the old and new PostgreSQL instances. They should be identical as they are installed on the same machine.
port92 / port96

Enter the port numbers for the respective CSS:

PostgreSQL 9.2.x2280
PostgreSQL 9.6.x2282


database92 / database96Enter the name of the default database used on the CAST Storage Service. By default this is "postgres" in both cases.
postgresThis is the "postgres" login within the PostgreSQL database itself. It is created specifically during the installation of PostgreSQL.
postgrespasswordEnter the password for the "postgres" database login.


  • Stop the PostgreSQL instances (you can check the name of the postgres services with the command "sudo systemctl -a | grep -i postgres"), for example: 
Code Block
languagebash
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):
Code Block
languagebash
sudo -i -u postgres
  • Set the PATH variable to include the "bin" folder in the PostgreSQL 9.6 installation folder:
Code Block
languagebash
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:
Code Block
languagebash
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:
Code Block
languagebash
mkdir /tmp/upgradePostgres
  • Change permissions on the "upgradePostgres" folder:
Code Block
languagebash
chmod 777 /tmp/upgradePostgres
  • Change focus into this "upgradePostgres" folder:
Code Block
languagebash
cd /tmp/upgradePostgres_dir
  • Run the upgrade process as follows:
Code Block
languagetext
pg_upgrade -d /opt/PostgreSQL/9.2/data -D /opt/PostgreSQL/9.6/data -b /opt/PostgreSQL/9.2/data/bin -B /opt/PostgreSQL/9.6/data/bin -p portCSS2 -P portCSS3
  • When the upgrade process has completed, ensure you remove the trust authentication method using vi:
Code Block
languagebash
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: 
Code Block
languagebash
sudo systemctl start postgresql-9.2
sudo systemctl start postgresql-9.6


Post upgrade actions

Expand

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 CSS3 

Open the following file with a text editor:

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

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

  • the host="CSS2" to change the source <CSS2> host name to the target <CSS3> host name. Note that if the CSS2 and CSS3 servers are located on the SAME host, there is no need to do this.
  • the port="2280" to change the source port="2280" (for CSS2) to the target port="2282" (for CSS3). 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 users are connecting to (this is optional).

When the changes have been made, save the file.

Code Block
languagexml
titleBefore update
<?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>


Code Block
languagexml
titleAfter update
<?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 to allow connection to the same schemas on CSS3 

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

Update cms_inf_store_css table in _MNGT schema on CSS3

If the CSS2 and CSS3 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 to CSS3 and where <CSS3> is the host name of the CSS3 server. This will change the port number from 2280 to 2282 and ensure that the display name for the CAST Storage Service in the CAST Management Studio Services view is correct:

Code Block
languagesql
set search_path = <prefix>_mngt;
update cms_inf_store_css set port=2282, object_name='<CSS3>:2282';

If the CSS2 and CSS3 servers are located on DIFFERENT hosts, run the following query instead, where <prefix> is the schema prefix for the schemas that you have moved to CSS3 and where <CSS3> is the host name of the CSS3 server. This will update the port number, host name and ensure that the display name for the CAST Storage Service in the CAST Management Studio Services view is correct:

Code Block
languagesql
set search_path = <prefix>_mngt;
update cms_inf_store_css set port=2282, host='<CSS3>', object_name='<CSS3>:2282';


Info

Note:

  • If you have moved more than one set of schemas from CSS2 to CSS3, you will need to repeat the above queries for each <prefix>_mngt you have moved.
  • If you are using a custom port number for your target instance, you should enter it in the query in place of 2282 (for a CSS3 instance).