Deploying a Custom Data Service

Publish a data service based on a .cds file into the data catalog.

Prerequisites 

Create a custom data service.

Follow these steps to deploy a custom data service file.

  1. In the Navigator, right-click a .cds file and select Deploy Custom Data Service. The Deploy Data Service dialog appears.
  2. (Optional.) Enter a name in the Data Service Name field if you don’t want to use the default name.
  3. (Optional.) Select a grid server from the Grid Server pull-down if you don’t want to use the default server.
  4. (Optional.) To control whether and for how long the results of this data service are cached, select a caching behavior:
    Don’t cache Do not cache the results of this data service—run the data service every time a user or application calls it. (This is the default.)
    Never expire Cache the results of this data service indefinitely.
    Expire after: Cache the results of this data service and let the results expire out of the cache after the specified period of time.

    To define the expiration period, enter a value in the field on the left and select a unit (seconds, minutes, hours, days, or weeks) from the pull-down to the right.

  5. In the Plug-in Coherence field, enter a value that represents the period of time following the last update during which the plug-in for this data service is assumed to be fresh. Use the pull-down to select a unit (seconds, minutes, hours, days, or weeks) for the coherence window. The data service checks for an updated plug-in at the end of the specified time.
  6. In the Run As User field, enter or browse for a user account under which the data service will run.
  7. Click Next. The dialog displays a page for sharing JAR files.
  8. In the dialog, navigate to the Data Federation share in which you want the JAR file for this data service to be stored. Shares are typically in the /Shares branch of the data catalog.
  9. Click Finish to save the data service configuration and deploy the new data service.
    Note: By default, a data service runs on the grid server where it was deployed. If you want data service execution to be shared among several grid servers, you or your grid administrator must configure execution service pooling. For information on execution service pooling, see the Data Federation Administration Guide, part of the DI Suite documentation set, which is available on the Sybase Product Manuals Web site at http://sybooks.sybase.com.

After the data service is deployed, it appears in Enterprise Explorer under Categories/ViewLibrary/DataServices. The JAR file appears in the location you specified.

For product-related issues, contact Sybase Technical Support at 1-800-8SYBASE. Send your feedback on this help topic directly to Sybase Technical Publications: pubs@sybase.com