webMethods step by step deployment using deployer
Platform: webMethods 6.1
We can deploy variety of webMethods assets from one server to other or from one environment to other like Development to QA or QA to Production using Deployer.
We may have different environments in our landscape depends upon our Architecture and requirements our landscape is configured with all infrastructure assets in each environment. Most known are Development where basic Design is proposed and the development of integration objects takes place. Quality Assurance (QA) where we perform different kinds of tests and also test the performance and throughput of our integration logic. When everything is set we go live in Production environment where our logic is up and running all the time handling numerous requests and processing huge amount of documents.
In order to deploy our code of various integration objects we use Deployer in webMethods.
Delopment -4 Servers, QA - 4 Servers , Production - 3 Servers
The following are some assets that can be deployed from one webMethods server to other:
a) Scheduled Tasks
Different types of packages in our Developer.
3) Trading Networks
- Processing rules
- Document attributes
- Document types
- Field groups
- Field definition
- Extended ID types
- Contact types
- Binary types
- Partners data
-> Go to Projects and create a deployment project give alias name and save it by setting the project properties.
-> Create Deployment set - give alias name - save it.
-> Select Unresolved dependencies - edit â select ignore for all packages and save
-> Go to Define and define the project by identifying the Assets or project content on source servers.
-> Go to Build / the hammer tool and build the project which contains all the files referenced in the project.
-> Go to Map â select target servers and save it.
-> Select map â create deployment candidate â give alias name and save it.
-> Test your Project by Simulating it using simulator
-> Then click on the deploy option which will deploy it to the target nodes.