Configuring ASE Manual Discovery
Reference / Command Line Interface Guide / CLI Cookbook: Common Workflows, Tasks, and Examples / CLI Cookbook: Authentication and Users / Configuring ASE Manual Discovery

This topic describes how to use CLI commands to manually add ASE repositories to a SAP ASE environment.  Discovery is the process by which the Delphix Engine identifies data sources and data dependencies on a remote environment. ASE repository discovery is done automatically when an environment is added to the Delphix Engine or when an already added environment is refreshed. In some cases, automatic discovery does not discover all of the repositories in a SAP ASE environment. These repositories may be added using manual discovery.

 Unlike automatically discovered instances, manually discovered instances are not automatically deleted if the environment is refreshed when the instance isn't running. Manually discovered instances are not updated during an environment refresh either. So for example, if you upgrade ASE to a new version or change the listener port, you must manually update the repository.


To manually discover an ASE repository you will need to:
  • Add an ASE environment
  • Use CLI to manually discover a repository

Creating an ASE Environment

Please refer to Adding an SAP ASE Environment for detailed steps.

Manually discovering a repository

In the following example we are using sc-dev3.dc2 as our example environment.

  1. Log into CLI and cd to repository menu:  
$ ssh delphix_admin@sc-dev3.dc2
Password:
sc-dev3.dc2> cd repository
sc-dev3.dc2 repository>

    2. Add (manually discover) an ASE repository instance:


The values used in the following code block are specific to the example instance we are adding.  
sc-dev3.dc2 repository> create
sc-dev3.dc2 repository create *> ls
Properties
   type: ASEInstance
   credentials: (unset)
   dbUser: (unset)
   environment: (required)
   installationPath: (required)
   instanceName: (required)
   instanceOwner: (required)
   ports: (required)
   version: (unset)
sc-dev3.dc2 repository create *> set credentials.type=PasswordCredential
sc-dev3.dc2 repository create *> set credentials.password=sybase
sc-dev3.dc2 repository create *> set dbUser=sa
sc-dev3.dc2 repository create *> set environment=sc-rhel64-sybase-ase-0
sc-dev3.dc2 repository create *> set installationPath=/opt/sybase/15-7
sc-dev3.dc2 repository create *> set instanceName=ASE1570_S1
sc-dev3.dc2 repository create *> set instanceOwner=sybase
sc-dev3.dc2 repository create *> set ports=5100
sc-dev3.dc2 repository create *> ls
Properties
   type: ASEInstance
   credentials:
       type: PasswordCredential (*)
       password: ******** (*)
   dbUser: sa (*)
   environment: sc-rhel64-sybase-ase-0 (*)
   installationPath: /opt/sybase/15-7 (*)
   instanceName: ASE1570_S1 (*)
   instanceOwner: sybase (*)
   ports: 5100 (*)
   version: (unset)
sc-dev3.dc2 repository create *> commit
   `ASE_INSTANCE-22
sc-dev3.dc2 repository>

Updating a repository

Adding onto the above, the following example illustrates updating an ASE instance's version after upgrading ASE:

sc-dev3.dc2> repository
sc-dev3.dc2 repository> select ASE1570_S1 
sc-dev3.dc2 repository 'ASE1570_S1'> update
sc-dev3.dc2 repository 'ASE1570_S1' update *> set version="15.7 SP138"
sc-dev3.dc2 repository 'ASE1570_S1' update *> ls
Properties
    type: ASEInstance
    credentials:
        type: PasswordCredential
        password: ********
    dbUser: sa
    installationPath: /opt/sybase/15-7
    instanceOwner: sybase
    linkingEnabled: true
    ports: 5100
    provisioningEnabled: true
    servicePrincipalName: (unset)
    staging: false
    version: 15.7 SP138 (*)
sc-dev3.dc2 repository 'ASE1570_S1' update *> commit

Be careful when setting the version string. Make sure that it matches output as displayed by the "select @@version" query all the way out to the patch level (PL). For example "15.7 SP138" or "16.0 SP02 PL01".