Sybase Data Federation deployment

Sybase Data Federation is enabled via Avaki servers that provide Enterprise Information Integration (EII) capabilities. These servers simplify provisioning, access, and integration of distributed data—for one group, or across the extended enterprise.You can integrate relational data, XML documents, files, and application data across departments, locations, and companies, and allow access to authorized users via a number of protocols and interfaces including transparent file access, ODBC, JDBC, and SOAP.

Before installing Sybase Data Federation, determine how to deploy Data Federation subcomponents in your environment. Decide the number of Avaki required in your domain, and the machines on which these servers will run.

Sybase Data Federation subcomponents

Use the DI Suite installer to install the Sybase Data Federation subcomponents listed below. The Sybase Data Federation domain can consist of one or more of the servers that together implement the data catalog and provide data integration framework and its provisioning and access services.

Basic Avaki domain

A basic Avaki domain can contain one or two grid servers, with one serving as the grid domain controller (GDC).

NFS or Windows file access

Extended file sharing

Interconnecting domains

Avaki domains can be accessed by a number of different clients. In some cases, clients require no Sybase software installed on their machines. This category includes transparent file access clients that access files in the data catalog via NFS or CIFS and Web service clients that access Avaki via SOAP calls. Clients that require some Sybase software installed include ODBC or JDBC clients and machines that are used for running the Avaki command line interface (CLI) client.

Avaki Client

NoteTo use Sybase Data Federation tooling capabilities, install Sybase WorkSpace. Sybase WorkSpace is packaged separately from DI Suite. You must use the installer provided with Sybase WorkSpace to install this development tool for DI Suite.

Installation recommendations

Consider the following installation guidelines to help you plan your Avaki domain. These are general guidelines that do not cover all possibilities. Planning an Avaki domain is a complex activity that must be performed in consultation with a Sybase deployment architect.

Example deployment architecture

Figure 5-3 shows an example deployment architecture of an Avaki domain with primary and secondary grid domain controllers, grid servers, share servers, a proxy server, and a data grid access server deployed. Users and applications can access relational data and Web services via Avaki services configured on the grid servers and files via the data grid access server using NFS or CIFS (Windows) clients.

Figure 5-3: Sybase Data Federation deployment architecture

This figure shows an example deployment architecture of a Data Federation domain with primary and secondary grid domain controllers, grid servers, share servers, a proxy server and a data grid access server deployed.