XL Deploy PowerCenter plugin

Preface

This document describes the functionality provided by the XL Deploy|Release Description|Interface plugin.

See the XL Deploy reference manual for background information on XL Deploy and deployment automation concepts.

Overview

The XL Deploy PowerCenter plugin provides a configuration item for a PowerCenter container, a control script to check the connection to it, and scripts to import and delete PowerCenter objects. It also includes several support files.

Requirements

• XL Deploy 6.0+

Installation

• Copy the latest JAR file from the releases page into the XL_DEPLOY_SERVER/plugins directory.
• Restart the XL Deploy server.

Integration Tests

In order to run an integration test you have to execute the next command:

./gradlew clean startIntegrationServer --stacktrace

flag --stacktrace will help to find out the root cause issues if they will happen.

This command will run Deploy in a container which is specified by these 2 parameters:

dockerImage = "xebialabs/xl-deploy" // Docker image without the version
version = "10.2.2" // And actually the version of it.

If you would like to see the logs of deploy you can do it next way:

1. Run docker ps and find the container which has image combined by 2 props $dockerImage:$version, for example xebialabs/xl-deploy:10.2.2.

2. Let's image you have there container id = bdc35b82271a. Then you have to type docker logs bdc35b82271a -f, and now you can see logs from the inception till get updates.

Locally you can find mounted folders in /build/integration-server/deploy. You can modify your configuration files and restart the docker image. In case you want to have a more sophisticated setup you can have a look at plugin https://github.com/xebialabs/integration-server-gradle-plugin.

Usage

Version 1.1.0

The powercenter.PowercenterXml has been updated in version 1.1.0 for the following behavior, remaining backwards-compatible with prior versions.

A new property folderNameMap has been introduced as a map_string_string kind to allow for source and target folder names to differ. Multiple entries can be provided. The key of each entry is the source folder name, while the value is the target folder name.

If the folderNameMap is present (not empty), then the source and target folder names in it will be used instead of any folder names in the old folderList property.

The old property folderList is still present as a list_of_string kind to allow for compatibility with prior versions of this plugin.