Maintenance and configuration for PostgreSQL on Documentation - V2

Maintenance activities for PostgreSQL

Mon, 01 Jan 0001 00:00:00 +0000

End of Life Notice

CAST Storage Service (com.castsoftware.css) is End of Life and is no longer supported or distributed. Customers previously using CAST Storage Service must migrate to a standard PostgreSQL installation. CAST recommends PostgreSQL 18.x.

Info

Summary: This section is designed to group together all miscellaneous backup, optimization and maintenance documentation related to the CAST Storage Service/PostgreSQL. All the tools listed in this page can be found in the CSSAdmin folder at the root of your AIP Core installation.

Changing the default operator and guest passwords for CAST Storage Service

Mon, 01 Jan 0001 00:00:00 +0000

End of Life Notice

Introduction

When a CAST Storage Service is installed or when a PostgreSQL instance is installed, two additional users/roles are created (operator/guest) by default as listed below. An additional user (postgres) is already present out of the box:

Action items after changing the operator user password when using CAST Console

Mon, 01 Jan 0001 00:00:00 +0000

End of Life Notice

Info

Summary: A description of the things you need to update after changing the “operator” user password and when using AIP Console.

Introduction

The “operator” user password is assumed to be set to “CastAIP”. If this is not the case - i.e. you have manually changed it (see Changing the default operator and guest passwords for CAST Storage Service) - you will need to perform the actions listed below when using CAST Console. t is not necessary to change the operator password in any .pmx file nor in the cms_inf_store_css table.

Moving existing CAST schemas

Mon, 01 Jan 0001 00:00:00 +0000

End of Life Notice

Info

Summary: this page provides information about how to move existing CAST schemas - i.e. changing the instance and/or the database.

Introduction

This document provides information about how to move existing CAST schemas in the following scenarios:

SSL encrypted mode configuration for PostgreSQL

Mon, 01 Jan 0001 00:00:00 +0000

End of Life Notice

Info

Summary: Instructions for configuring PostgreSQL and CAST AIP related applications to function in SSL encrypted mode.

Introduction

Out of the box, PostgreSQL is not preconfigured to function in SSL encrypted mode, i.e. to accept incoming encrypted database connections for enhanced security. However, SSL encrypted mode can be configured if required. The configuration process involves specific steps described in this document:

Migrating CAST AIP schemas from Oracle Server and Microsoft SQL Server

Mon, 01 Jan 0001 00:00:00 +0000

End of Life Notice

Note

Note that this tool is no longer maintained and has been removed from CAST AIP ≥ 8.3.15 for the following reasons:

the tool does not support transfers to CSS3/PostgreSQL 9.6
CSS3/PostgreSQL must be used with CAST AIP ≥ 8.3.x (CSS2/PostgreSQL 9.2 is deprecated for use with 8.3.x)

Info

Summary: this page describes how to migrate CAST AIP schemas installed on Oracle Server and Microsoft SQL Server instances over to PostgreSQL.

Accessing PostgreSQL on Amazon Web Services RDS

Mon, 01 Jan 0001 00:00:00 +0000

End of Life Notice

Info

Summary: information about accessing a PostgreSQL instance hosted on Amazon Web Services RDS.

Introduction

CAST supports PostgreSQL instances deployed via Amazon Web Services RDS - some recommendations for accessing these instances for use with CAST AIP are listed below.

Using the CAST-Connection-Profile-Configuration.py file

Mon, 01 Jan 0001 00:00:00 +0000

End of Life Notice

Info

Available in AIP Core ≥ 8.3.37.

Introduction

The file CAST-Connection-Profile-Configuration.py has been made available to allow you to manually create an entry in a cast-ms.connectionProfiles.pmx file. The file is available in the following location:

Using a custom PostgreSQL database other than the default postgres

Mon, 01 Jan 0001 00:00:00 +0000

End of Life Notice

Introduction

Changes have been made to AIP Core and other CAST AIP tools to make it possible to connect to a custom PostgreSQL database other than the default “postgres” (previously custom databases were not permitted for use with CAST). The current compatibility matrix is as below:

PostgreSQL - Troubleshooting

Mon, 01 Jan 0001 00:00:00 +0000

End of Life Notice

Info

Summary: some troubleshooting techniques for specific issues that may be encountered when using PostgreSQL

An existing connection was forcibly closed by the remote host

This error may be be accompanied by the following in the PostgreSQL log:

Storing analyzed source code in encrypted format

Mon, 01 Jan 0001 00:00:00 +0000

End of Life Notice

Introduction

When a CAST application analysis/snapshot is actioned, part of that process is to store the analyzed source code in the application schemas so that client applications such as Imaging, Console and the Dashboards can display that source code. Source code is stored by default in the application schemas in unencrypted format, however, if your environment requires that this source code is stored in encrypted format (due to security or privacy concerns) then it is possible to configure this. Some things to note about this: