Creating Artifacts Using the Wizard

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

This page includes the following:

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 many Component Workflows)
Environments (Targets which represent your endpoints)
Targets (endpoints where you deploy your Application components)
Profiles (link components to targets)
Packages (your Application version)

To Create the Required Artifacts using the Wizard

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

Run the wizard from the Applications list.
Enter a descriptive name for the Application (that is, the container where you store your components), such as "WebShop 3-Tier".
Select the Application type as Generic.
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).
Click Continue.
Two components are created by default (Backend & Frontend). Add a third one and define them as follows:
- BL
  Files that form the business logic and will be deployed to the business logic server.
  Type: Filebased
- DB
  Scripts that create/update the database and will be executed on the database server.
  Type: Database JDBC
- FE
  Files that build up the front end user interface and will be deployed to the web server.
  Type: Tomcat
Note: Component types are very important. They should match real-life components and the type of endpoint that they are being deployed to. The component types have predefined properties which outline characteristics of the components.
Select the same destination folder as for the Application.
Click Continue.
Enter a name for the Workflow that describes its goal, like "Install".
Select the Install Workflow type. This type is used because the purpose of the Workflow is to install an Application.
Select the same destination folder as for the Application.

Note: You will have to define the Workflow later. See Configuring Deployment Workflows.
Click Continue.
Create a new non-production Environment, for example "WebShop3Tier-Test".
Select the infrastructure_nonproduction folder.
Click Continue.
Add 3 new Targets for the test Environment.
- Tier: Front End
  Test Environment target (Folder: Infrastructure_nonproduction): S_TEST_WEB1
- Tier: Database
  Test Environment target (Folder: Infrastructure_nonproduction): S_TEST_DB
- Tier: Business Logic
  Test Environment target (Folder: Infrastructure_nonproduction): S_TEST_APP1
Click Continue.
Enter a name for the Profile (WebShop3Tier Test), which refers to a subset of the Targets the Environment is comprised of.
Select the same destination folder as for the Application
Select the WebShop3-Tier Test login object from the drop-down list. Login objects store login data for hosts. Jobs and file transfers use it to access operating systems and Applications.
Click Continue.
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.
Select Deployment from the Type drop-down list. Packages are associated with an Application.
Select WebShop_3_Tier_Packages as destination folder.
Click Continue. An overview of the entities that will be created via the wizard is displayed.
Click Finish.

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

What do I have now?

Application: WebShop 3-Tier
3 Components: DB, BL, FE
Workflow: Install
Test Environment: WebShop3Tier
3 Targets:
- S_TEST_WEB1
- S_TEST_DB
- S_TEST_APP1
Profile: WebShop3Tier Test
Package: 1.0

Next steps: