C:\SAS\Config\Lev1\Web\WebAppServer\SASServer13_1\lib
.
proc ASEXPORT meta= ( user='username' password='password' server='host–name' port=port_number repos='repository.name' filter=(DOMAINS "*" USERS "*" LOGINS "Login [Domain/AuthenticationDomain[@OutboundOnly='0']]") ) as= ( server='host–name' user='domain\username' pass='password' port=port_number filter=(DOMAINS "*" USERS "*" LOGINS "*") ) verbose out=asx ; /* * Auto-match domains by name. */ match DOMAINS; /* * Add remaining unmatched domains (optional) */ add DOMAINS; /* * Auto-match users by FQLN. */ match USERS; /* * Add remaining unmatched users (optional) */ add USERS; /* * List everything for review */ list; /* * Create an input file (per noforward) for proc METADATA that we can review. * Don't export passwords or their hosting outbound logins. */ export; quit;
criteria=option is required on the add statements to prevent the addition of all unmatched domains and users. You can also use an initial filter of something other than
*to prevent unmatched domains and users from being available in the snapshot pulled back from DataFlux Authentication Server and SAS Metadata Server.
yourserver:port/SASBusinessDataNetwork/migration/configure
.
Note that you can execute an optional test run to anticipate problems.
Field or Option
|
Description
|
---|---|
Connection to BDN 2.x
database server
|
|
Type of database server
|
Specifies the databases
that were supported by BDN 2.x: SQL Server, Oracle, and DB2.
|
Database server host
|
Specifies the name of
the machine hosting the database server instance.
|
Database server port
|
(Optional) Specifies
the port to which the database server instance is listening.
|
Database name
|
Specifies the name of
the database within the server instance.
|
Override generated JDBC
URL
|
The migration configuration
generates a JDBC URL to connect to the BDN 2.x database. If a correct
URL for the database cannot be generated by the migration code, selecting
this check box enables the user to override the generated JDBC URL.
This is used in case the user cannot resolve a connection problem.
|
JDBC URL to database
|
When Override
generated JDBC URL is not selected, specifies the generated
JDBC URL to the database. When Override generated JDBC
URL is selected, the text field is editable so that you
can enter the JDBC URL to the database.
|
BDN 2.x database connection
properties
|
Specifies additional
properties needed for connecting to the BDN 2.x database. An example
for SQL Server is the instance name: instanceName=SQLSERVER2008.
|
Optional prefix for
BDN 2.x tables
|
Specifies an optional
prefix for the tables that can include catalog and schema prefixes.
An example is Repository1.BDN_.
|
User name for database
connection
|
Specifies the user name
for connecting to the database.
|
Password for database
connection
|
Specifies the password
for connecting to the database.
|
Options
|
|
Keep temporary tables
|
When selected, specifies
that the tables copied from the 2.x database to the 3.1 database are
not dropped after running the migration. The copied tables are put
into a schema named SAS_BDN_TEMP.
|
Skip copying the tables
from the source BDN database
|
When selected, skips
the step of copying the tables from the source BDN database. If the
temporary tables are kept from a previous migration run, they can
be reused in a subsequent migration run, thereby saving the time required
to copy the tables again. There is no need to connect to the source
BDN database when the copy is skipped. Therefore, the database values
are not needed.
|
Test run
|
When selected, executes
a migration run in which none of the SQL statements to create tables
or write to tables are actually executed. Security, lineage, and user
preferences are not updated. The source database tables are read.
|
Run
|
Runs the migration.
|