Page tree
Skip to end of metadata
Go to start of metadata

Summary: this page describes how to manage application aliases using the Admin Center.


This option is only visible to users with the ADMIN or SUPER ADMIN role.

Introduction

The alias feature you to choose which CAST Storage Service/PostgreSQL instance is used to fetch the source code for an object in a given application when Viewing source code. The Applications panel (panel 4) enables you to manage the application aliases:

  • The Default Alias column shows the alias corresponding to the instance name of the CAST Storage Service/PostgreSQL from which the Application was originally exported
  • the Selected Alias column shows the alias corresponding to the instance name of the CAST Storage Service/PostgreSQL which is currently being used to provide the source code for the Application

If you do not see a list of Applications, click panel 2 to display the Application list:

Use case

This option is aimed at situations where the Application was exported from CAST Storage Service/PostgreSQL instance "A" and the Application is being stored on a different CAST Storage Service/PostgreSQL instance ("B") for use with CAST Imaging. Typically this occurs when a CAST Storage Service/PostgreSQL instance is set up specifically for use with CAST Imaging to avoid CAST Imaging connecting to the "production" CAST Storage Service/PostgreSQL instance.

Managing aliases

In order for this feature to function, the details of the CAST Storage Service/PostgreSQL instances containing the Application source code must first be configured- i.e. all instances must be added. When configured, the column Default alias for a given Application will display all the CAST Storage Service/PostgreSQL instances that have been added - specifically the aliases configured in the line datasource.alias will be displayed.

For example, two CAST Storage Service/PostgreSQL instances have been added: my_postgresqlA and my_postgresqlB:

server.port=9980
api.token=D5ED6A406775FC71B8D2A978883E8ED4
datasource.url=jdbc:postgresql://my_postgresql1:2282/postgres,jdbc:postgresql://my_postgresql2:2282/postgres
datasource.username=operator,operator
datasource.password=CastAIP,CASTAIP
datasource.alias=my_postgresqlA,my_postgresqlB

If you need to switch to a different CAST Storage Service/PostgreSQL instance for the Application's source code, select the Application and click the edit button:

Then choose the alias that corresponds to the CAST Storage Service/PostgreSQL instance you want to switch to:

The alias in the Selected alias column will update to show the alias you selected. This alias (and its corresponding CAST Storage Service/PostgreSQL instance) will now be used to fetch the source code for the application when Viewing source code.

  • No labels