CAST Components
Page tree

Versions Compared

Old Version 6

changes.mady.by.user James Hurrell

Saved on

compared with

New Version 7

changes.mady.by.user James Hurrell

Saved on

Key

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

...

Before you can use the tool to migrate your schemas, you need to create a configuration.castmigration XML file which will contain the instructions about what needs to be migrated and information about the source RDBMS and target CSS. An example file is shown below:


 code
Code Block
language
xml
<?xml version="1.0" encoding="UTF-8"?>
<Configuration originServerDriverClassName="DRIVER_NAME" originServerUrl="URL" targetServerDriverClassName="org.postgresql.Driver" targetServerUrl="jdbc:postgresql://SERVER_NAME_OR_IP_ADDRESS:<2280|2282>/postgres" licenseKey="LICENSE_KEY">
 <MBSchema name="MNGT_NAME" skipCustomTables="true|false" state="" isSelected="true|false">
  <KBSchema name="LOCAL_NAME" skipCustomTables="true|false" state=""/>
  <CBSchema name="CENTRAL_NAME" skipCustomTables="true|false" state=""/>
 </MBSchema>
</Configuration>

<configuration> tag

This tag contains the values needed to connect to the source RDBMS and the target CSS server, the CAST AIP license key and an optional value for those migration schemas from CAST AIP 7.0.x:

ElementDescriptionOptionsRequired?

originServerDriverClassName

Defines the JDBC driver used to connect to the source RDBMS.Yes(tick)

originServerUrl

Defines the URL (in JDBC format) used to connect to the source RDBMS.
  • Oracle SID: jdbc:oracle:thin:@HOST:PORT:SID
  • Oracle SERVICE: jdbc:oracle:thin:@//[HOST][:PORT]/SERVICE
  • MS Microsoft SQL Server: jdbc:jtds:sqlserver://<server>[:<port>][/<database>]
Yes(tick)
targetServerDriverClassNameDefines the JDBC driver used to connect to the target CSS.org.postgresql.DriverYes(tick)
targetServerUrlDefines the URL (in JDBC format) used to connect to the target CSS.jdbc:postgresql://HOST:<2280|2282>/postgresYes(tick)
licenseKeyDefines the CAST AIP license key assigned to the schemas you wish to migrate.Full CAST AIP license key in the format: Sample&amp;Test:1;AIP/EFP:20121031:ABCDEFGHYes(tick)


Info
Note that you can only specify one source and one target server per configuration.castmigration file.

<MBSchema> tag

This tag defines the CAST AIP schemas that will be migrated from the source RDBMS to the target CSS server:

ElementDescriptionOptionsRequired?
nameDefines the name of the Management Service you would like to migrate.Name of the CAST Management Service.Yes(tick)
skipCustomTablesWhen set to True, any custom tables you may have created in the CAST schemas on the source RDBMS will NOT be migrated to CSS. When set to False or the option is omitted entirely, then all tables are migrated.True | FalseNo(error)
state

This option should be left blank. It will be updated with a status on completion of the migration process:

  • Migrated - the schema was successfully migrated
  • Blank or any other entry - the schema was not migrated
N/AYes(tick)
isSelectedThis option can be set to True (the Management Service and all associated schemas will be migrated) or False (the Management Service and all associated schemas will NOT be migrated).True | FalseYes(tick)


Info

Note that:

  • When specifying a Management Service, you must also specify the associated Analysis and Dashboard Services in their own child tags (KBSchema and CBSchema)
  • The associated Analysis and Dashboard Services must be stored on the same source server.

<KBSchema> / <CBSchema> tag

These two tags must be defined as child tags of the <MBSchema> tag:

ElementDescriptionOptionsRequired
nameDefines the names of the Analysis or Dashboard Services you would like to migrate. These services must be associated to the parent Management Service you have defined in the <MBSchema> tag.Name of the CAST Analysis or Dashboard Service.Yes
skipCustomTablesWhen set to True, any custom tables you may have created in the CAST schemas on the source RDBMS will NOT be migrated to CSS. When set to False or the option is omitted entirely, then all tables are migrated.True | FalseNo
state

This option should be left blank. It will be updated with a status on completion of the migration process:

  • Migrated - the schema was successfully migrated
  • Failed - the schema migration failed
  • Skipped - the schema migration was skipped (incorrect version, connection error, schema exists on target already
  • Halted - the schema migration was halted because another related schema migration failed
N/AYes

Examples

Oracle using SID

Code Block
<?xml version="1.0" encoding="UTF-8"?>
<Configuration originServerDriverClassName="oracle.jdbc.OracleDriver" originServerUrl="jdbc:oracle:thin:@192.168.20.10:1521:ORA" targetServerDriverClassName="org.postgresql.Driver" 
targetServerUrl="jdbc:postgresql://192.168.20.11:2280/postgres" licenseKey="Sample&amp;Test:1;AIP/EFP:20121031:ABCDEFGH">
<MBSchema name="ABC_MNGT" state="" skipCustomTables="true" isSelected="true">
	<KBSchema name="ABC_LOCAL" skipCustomTables="true" state=""/>
	<CBSchema name="ABC_CENTRAL" skipCustomTables="true" state=""/>
</MBSchema>
</Configuration>

Oracle using Service

...

Migrating only one schema

In this example, only the V123_LOCAL schema will be migrated. Adding state="Migrated" to the V123_MNGT and V123_CENTRAL schemas will force only the V123_LOCAL schema to be migrated:

 


Code Block
<?xml version="1.0" encoding="UTF-8"?>
<Configuration originServerDriverClassName="oracle.jdbc.OracleDriver" originServerUrl="jdbc:oracle:thin:@//192.168.20.10:1521/PRODMASSTEST05.castsoftware.com" targetServerDriverClassName="org.postgresql.Driver" targetServerUrl="jdbc:postgresql://192.168.20.11:2280/postgres" licenseKey="Sample&amp;Test:1;AIP/EFP:20121031:ABCDEFGH">
 <MBSchema name="V123_MNGT" skipCustomTables="true" state="Migrated" isSelected="true">
  <KBSchema name="V123_LOCAL" skipCustomTables="true" state=""/>
  <CBSchema name="V123_CENTRAL" skipCustomTables="true" state="Migrated"/>
 </MBSchema>
</Configuration>
 

Note that if you are only migrating either the Analysis or Dashboard Service (KBSchema or CBSchema), you should ensure that you attach this schema to a Management Service (MBSchema/MNGT) in the target CSS server using the CAST Management Studio:
...