Get Data Moving 1
Results 1 to 1 of 1

Thread: Using AisDeployer to Send an AIS Solution to Support

  1. #1
    Join Date
    Sep 2006
    Posts
    233
    Rep Power
    10

    Using AisDeployer to Send an AIS Solution to Support

    AisDeployer is a new utility that ships with AIS version 5.0 that support the process of deploying AIS solutions from the development environment to staging and production environment. This utility is also useful for similar tasks such packaging an AIS solution for sending it to AIS support for analysis.

    The following paper explains how the AIS deployer can be used to package and send AIS solutions by email to AIS support (or to anyone else for that matter).

    How to Send an AIS Solution to Support
    When an AIS support issue requires better understanding of the AIS solution deployed at a customer site AIS Support may ask the customer to send it the solution for analysis.


    Sending the solution means sending the AIS definitions making the solution (metadata only, in most cases no data needs to be sent). With the release of AIS 5.0 a new utility called AisDeployer is provided that helps customers send their solutions to support (assuming sending the solution metadata is permitted).


    The steps to send an AIS solution are described below.


    Prerequisites

    The following items are required:
    • The AisDeployer must be deployed on a Windows machine (no other AIS component is required on this machine)
    • All AIS servers involved in the solution must be at least of version 4.8.2
    Steps

    Step 1 – Invoke AisDeployer

    From the Start menu select All Programs à Attunity à AIS Deployer à AisDeployer

    The following screen will appear:

    Attachment 28

    Step 2 – Create an Empty AisDeployer Solution

    To create an empty AIS deployment solution press the New button. The following screen will appear:

    Attachment 29

    Type in the Solution Path text box a directory path where the solution will be created. The directory must be empty – in the picture above we entered the path C:\AisSolutions\ToSupport1 (the directory C:\AisSolution will be created automatically if it does not exist).

    To create the empty solution press the Create Solution button.

    Step 3 – Add the AIS Solution Machines

    This step must be repeated for each AIS server machine that is part of the solution: press the Add Machine button to add a new AIS server to the solution. The following screen will appear:

    Attachment 30

    Enter the host, port, username and password of the AIS machine. Enter a name for this machine in the Name text box and optional description in the Description text box.


    The username and password entered must be associated with a user who has administration access to the AIS definitions. The port number can be omitted, in which case port 2551 will be used.


    It is recommended at this point to press the Check button to make sure the machine details were filled properly. A dialog box will pop up showing the AIS machine platform type and AIS version in use as shown below:

    Attachment 31

    Once checked, press the OK button to complete the adding of the machine.

    Step 4 – Import AIS Definitions from Solution Machines

    Once all AIS machine in the solution were added, press the Import button to bring all AIS definitions into the newly created solution. The screen will look as follows:

    Attachment 32

    While importing, the program shows its progress in a grid with errors marked in red. An error in importing a specific resource does not break the process – the error is shown and the process resumes with the next resource. A log of the import process is kept under the solution path in the logs/import directory. In this example, the log is located in:

    C:\AisSolutions\ToSupport1\.logs\.imports\20060921 T1122.log

    The import log file is named based on the time in which the import started.
    If the import process stalls or takes too long, it can be stopped by pressing the Stop button. Obviously, in such case the import will be partial (and this will be reflected in the log as well).

    Step 5 – De-Classify the Solution
    In order not to leak security sensitive information, one should 'prune' the solution directory before sending it. In particular the following directories should be deleted:

    • solution-dir/.system
    • solution-dir/machines/machine-name/users


    Step 6 – Package the Created Directory in a Zip File and Email it

    All that remains now is to zip the contents of the C:\AisSolutions\ToSupport1 directory and email it to AIS support.

    Notes

    If the AIS servers involved in the solution are before version 4.8.2 then the process for the same task is less automatic and involves the following steps:
    • Repeat this step for each solution machine:
      • In Studio right-click the machine in the Configuration perspective and select ‘Export XML Definitions…’ – save the XML produced to a file called ‘machine_XXX.xml’
      • For all datasources defined on the machine, switch to the Metadata view and there right-click the datasource name and select the ‘Export XML Definitions…’ – save the XML produced to a file called ‘datasource_XXX.xml’
    • Once you have the above files for all solution machines simply zip them together and send them to AIS support.
    Last edited by DrorHarari; 11-14-2006 at 07:54 PM. Reason: Fixing image links
    By Dror Harari

    To Find Out more About Attunity Technology:
    Attunity
    or:
    Contact Us

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •