Open topic with navigation

Creating Artifacts using the Wizard

The wizard helps you create all required artifacts for the deployment in just a few clicks. It is the first step to design and run your workflow.

What Artifacts Can I Create with the Wizard?

You can define the following basic artifacts in minutes:

Application (container)

Components (single deployable application artifact)

Application workflow (which consists of a number of Component Workflows)

Environments (Deployment Targets which represent your endpoints)

Targets (endpoints where you deploy your application components to)

Profiles (link components to targets)

Packages (your application version)

To Create the Required Artifacts using the Wizard

All non-mandatory properties will be defined at a later stage.

1. Run the wizard from the Applications list.
2. Enter a descriptive name for the application (that is, the container where you store your components), such as "WebShop 3-Tier".
3. Select the application type as Generic.
4. Select a folder to store your new application. You can use an existing one or create a new folder based on the application name (administration rights are required).
5. Click Continue.
6. Two components are created by default (Backend & Frontend). Add a third one and define them as follows:

   Name	Type	Description
   BL	Filebased	Files that form the business logic and will be deployed to the business logic server.
   DB	Database JDBC	Scripts that create/update the database and will be executed on the database server.
   FE	Tomcat	Files that build up the front end user interface and will be deployed to the web server.

   Component types are very important. They should match real-life components as well as the type of endpoint that they are being deployed to. The component types have predefined properties which outline characteristics of the components.

7. Select the same destination folder as for the application.
8. Click Continue.
9. Enter a name for the workflow that describes its goal, like "Install".
10. Select the Install Workflow type. This type is used because the purpose of the workflow is to install an application.

11. Select the same destination folder as for the application.

    Please note that you will have to define the workflow later. See Modifying the Application Deployment Workflow.

12. Click Continue.
13. Create a new non-production environment, for example WebShop3Tier-Test.
14. Select the infrastructure_nonproduction folder.
15. Click Continue.
16. Add 3 new Deployment Targets for the test environment.

    Tier	Test Environment targets (Folder: Infrastructure_nonproduction)
    Front End	S_TEST_WEB1
    Database	S_TEST_DB
    Business Logic	S_TEST_APP1

17. Click Continue.
18. Enter a name for the profile (WebShop3Tier Test), which refers to a subset of the Deployment Targets the environment is comprised of.
19. Select the same destination folder as for the application
20. Select the WebShop3-Tier Test login object from the dropdown list. Login objects store login data for hosts. Jobs and file transfers use it in order to access operating systems and applications.
21. Click Continue.
22. Enter a name for the Package, which is an instance of your application (a version, a revision, a tag...). It is recommended to start with 1.0.
23. Select Deployment from the Type dropdown list. Deployment Packages are associated with an application.
24. Select WebShop_3_Tier_Packages as destination folder.
25. Click Continue. An overview of the entities that will be created via the wizard is displayed.
26. Click Finish.

Congratulations! You have created all required artifacts for the deployment in the blink of an eye.

What do I have now?

Next steps:

2. Defining Custom and Dynamic properties
3. Configuring Deployment Workflows
4. Deploying an Application to an Environment
5. Deploying a New Version of the Application

Open topic with navigation