Home

	Expand Search

Introducing OmniConnect for Adaptive Server Enterprise

Chapter 1: Welcome to OmniConnect

Where To Begin

Where To Begin

Steps Needed to Use OmniConnect

To run OmniConnect follow these steps:

• Make sure you have installed the OmniConnect option.
• Install DirectConnect server(s) or gateways for the external data sources you choose to access (such as Oracle, Ingres, DB2, Informix, or Rdb).
• Configure the server to access remote objects as described in Component Integration Services User's Guide.

Migrating from OmniConnect Release 10.5

The following section provides instructions for migrating from OmniConnect release 10.5 schemas to OmniConnect release 11.5. If you are a new OmniConnect user who is not using earlier versions of OmniConnect, you will not need to read this section.

You can migrate to OmniConnect Release 11.5 only if you are currently using OmniConnect release 10.5.

Preparing to Migrate

Read the documentation on the ddlgen utility in the Component Integration Services User's Guide. This utility is used to migrate objects defined in OmniConnect. ddlgen creates an isql script that you can use to recover the following objects:

• Servers
• Database definitions
• Logins
• Remote logins
• External logins
• Database options
• Object ownership
• Users and groups
• Aliases
• Rules and defaults
• User datatypes
• Rules and defaults bound to user datatypes
• Table definitions
• Rules and defaults bound to table columns
• Local views
• Triggers
• Procedures
• Permissions

Migrating

The migration process requires four steps:

1. Run the ddlgen utility against the existing OmniConnect release 10.5, and save the output script.

2. Install OmniConnect release 11.5 in a different directory from OmniConnect release 10.5.

3. Edit the ddlgen script that you created in step 1 if required. This might be necessary to initialize required devices and to update create database statements so that objects are created on the correct devices. It may also be necessary if your system requires real passwords.

4. Use the isql utility to redirect the ddlgen output script, created in step 1, to the new OmniConnect release 11.5.

Elements Not Restored

ddlgen does not migrate the settings of configuration parameters. The System Administrator should use the sp_configure procedure against the old installation to generate a list of configuration settings. Then use sp_configure against the new installation to re-establish configuration option settings.

Configuring OmniConnect

See the Component Integration User's Guide for instructions on configuring OmniConnect.