Managing Files and Artifacts

In this section:

The Files section of iWay Sentinel administration enables the management of various artifacts within the Sentinel environment. Artifacts can represent anything, from actual iWay Integration Applications (iIAs) and Templates to third-party libraries and plain files. The artifacts maintained in Sentinel repository via SPOG can then be used to be distributed to remote servers for various uses such as installation, deployment, updates. This enables centralized distribution of environment updates to multiple end points from a single environment.

When Files view opens, it presents the following layout.

The two sections presented are Sentinel Managed and Other Artifacts.

Sentinel Managed include specific artifacts, such as iWay Integration Applications (iIAs), Templates (iIA templates), Packages (iSM packages) and Patches. Other Artifacts include property files, libraries, and so on, which might need to be stored and distributed through Sentinel.

A standard toolbar is available for file interaction:
Top of page
x
Managing Applications

In this section:

Sentinel Managed components include Applications and Packages. Application is what we know as the iWay Integrated Application (iIA) and its associated Templates, which define the runtime environment. Packages, are the iSM packages which can be published and deployed onto the iSM server to update the server environment.
x
Adding an Application Component

This section describes how to add an Application Component.
x
Procedure: How to Add an Application Component
  1. Click the disk icon with the green +. This will open up a file browser window and enable you to browse to the application to be added to the Sentinel's repository. You may also right-click in the space and select Upload Files as shown in the image below.

  2. Drag in the files you wish to add to the repository, as shown in the image below. Make sure to upload the .ita and .iia files for application management. They are necessary for deployment of iWay Integration Application.

    The uploaded files are displayed in the list of available files, as shown in the following example.

  3. To deploy an application from repository to remote servers, right-click the .iia file and select Deploy, as shown in the following image.

    A Deploy Application(s) screen opens.

  4. Provide a name and optional description for the application to be deployed.

  5. Click Next.

    The Step 2 tab is displayed.

  6. Select the template to be used for deployment and the list of possible target servers, or group of servers, as shown in the image below.

  7. Click Next.

    A confirmation summary message is displayed for the review.

  8. Click Finish.

The application is deployed in the stopped mode to the specified server.
Top of page
x
Managing Artifacts

In this section:

Other Artifacts folder is designed to store non-application specific components. This is also where you would store the JS script files which can be used to schedule Sentinel tasks for execution.

To distribute non-application specific components such as properties files, jar files or any other artifact not managed by application, the artifact needs to be uploaded to the Sentinel's repository and then package needs to be created.
x
Uploading Artifacts

This section describes how to upload an artifact.
x
Procedure: How to Upload an Artifact
  1. To upload an artifact into Sentinel's repository, click the disk icon with green + sign, or right-click and select Upload Files.

  2. Drag and drop, or browse to the artifact you wish to import into the repository.

    Once imported the artifact is available for use.

  3. Right-click the file (or files by highlighting multiples). An options menu is displayed with standard file operations options and Sentinel specific options, as showin in the image below.

    The following options are available:

    • Download. Download the file locally.
    • Edit file. Open the file for editing.
    • Delete. Delete the file from the repository.
    • Get info. Display information for the selected file.
    • Package. Create an iSM package for deployment.
    • Run on Sentinel. Only applicable to scripts, executes the script on the Sentinel server.
    • Run on Server. Only applicable to scripts, executes the script on an iSM server, which distributes the work.
  4. To package a component for distribution, select Package.
  5. Provide the name for the package with optional description and version, as shown in the following image.

  6. Click Next. Step 2 opens, as shown in the following image.

  7. Provide the location hierarchy for how the files should be packaged, as follows:
    • Target Location. Location as it relates to the iWay Home directory. Drop down is predefined with common locations.
    • Subdirectory. Subdirectory to be created under the Target Location.
  8. Click Next. Step 3 opens, as shown in the following image.

    Step 3 provides the confirmation and summary of the package.

  9. Review and click Finish.

The created package is available under the Packages folder of the Sentinel repository, as shown in the example below.

Right-clicking the package presents a menu of available options, as shown in the following image.

The options include:

  • Download. Download the package to local directory.
  • Delete. Delete a package.
  • Get info. Get information for the package.
  • Publish. Upload the package to the remote server(s). This will only upload but not install the package.
  • Deploy. Install the package into the remote server(s).

To distribute the package to multiple servers and install it, select Deploy. A screen with a selection of servers where it should be deployed is displayed. Select server(s), or a group where the package should be deployed and click Deploy.

A confirmation message of successful deployment will be displayed. The package has been installed at the remote server at this point.

iWay Software