Redeploying an Archived Grid Object

Deploy an object in a grid object archive to a new Data Federation domain or restore it to its original domain.

1. To open the archive (.goa file), right-click it in the Navigator and select Open.
2. In the archive, make sure:
   1. The objects you want to deploy are set to Overwrite existing object or to Do not overwrite existing object, as appropriate.
      Note: If an object already exists on the target server, WorkSpace flags its icon in the Grid Objects to Deploy pane with a yellow triangle, like this:
   2. Any objects you do not want to deploy are set to Do not deploy.
   3. (Optional.) Objects are targeted to deploy to the correct grid servers.
   4. Property overrides for deploying objects are set as desired. Select an object in the archive to see its property overrides in the bottom pane.
      Note: If you deploy before saving changes, unsaved changes in the archive are included in the deployment. To save the archive, type Ctrl+s or select File > Save.
3. Select the GDC at the top of the hierarchy in the Grid Objects to Deploy pane.
4. (Optional.) Click Preview in the right pane. WorkSpace runs a simulated deployment and displays the results in the Console view in the bottom pane. If the preview deploys more objects than you expected, remember that if any objects in the archive have dependencies (objects that provide input), the dependent objects are included in the archive and are deployed along with the objects you explicitly added. Select an object in the left pane to see its dependencies in the right pane.
5. To deploy objects from the archive based on the settings on the Deploy tab in the Properties view, click the Deploy button in the right pane. Alternative: If you want to be prompted to specify a target GDC and to map source to target grid servers, right-click the .goa file in the Navigator and select Deploy Archive. You can also use the New button in the resulting dialog to create a connection profile for a target GDC.
   Note: WorkSpace Data Federation cannot deploy an object into a domain where an object of the same name and type already exists on a different grid server. If you deploy an object to GridServer1, for example, and then decide the object belongs on GridServer2, you must delete the copy on GridServer1 before you can deploy the object on GridServer2.
6. If you used the Deploy button but have not selected a destination GDC, WorkSpace prompts you to identify one.

Configure permissions, caching, and execution schedules for the newly deployed objects. By default, the permissions on an object newly deployed from an archive are set so that the user who deployed the object (who is the owner) can read, write, execute, and delete it and its contents; members of the DomainUsers group in the current grid domain can read the object, but they cannot write, execute, or delete. Users in other domains have no permissions.

• Creating a Data Federation Share in Sybase WorkSpace
  Set up a link that allows a directory in the local file system to appear in the Data Federation data catalog. Applications (including WorkSpace Data Federation) and users who need the files can then access them through the data catalog without having to know which computer or file system they are located on.
• Configuring Redeployed Grid Objects
  Some objects deployed from grid object archives need configuration on their new server. You might need to set access controls, caching attributes, and execution schedules.

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