Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Creating Environment Specific Configurations with WSO2 Developer Studio

685 views

Published on

To view recording of this webinar please use the below URL:

http://wso2.com/library/webinars/2016/02/creating-environment-specific-configurations-with-wso2-developer-studio/


WSO2 Developer Studio provides tooling support for WSO2 products. The latest release, version 4.0, is implemented in a kernel based structure, which changes the installation process of tooling for different WSO2 products. This webinar is a step-by-step tutorial on how to create environment specific artifacts with WSO2 Developer Studio. It will discuss how to

Install WSO2 Developer Studio 4.0 - with tooling support for WSO2 Governance Registry (WSO2 GReg) and WSO2 Enterprise Service Bus (WSO2 ESB)
Create WSO2 ESB and WSO2 GReg artifacts
Implement environment specific artifacts and link them with common artifacts across environments
Deploy and maintain artifacts

Published in: Technology
  • Be the first to comment

Creating Environment Specific Configurations with WSO2 Developer Studio

  1. 1. Environment Specific Artifacts with WSO2 Developer Studio Awanthika Senarath Software Engineer, WSO2 Inc. Rajeeva Uthayasangar Software Engineer, WSO2 Inc.
  2. 2. Outline Presentation on : ❖ Introduction to WSO2 Developer Studio 4.0.0 ❖ Importance of environment specific artifacts ❖ Recommended approach develop and maintain environment specific artifacts ❖ Deployment model of environment specific artifacts Demo On : ❖ Creation and Maintenance of environment specific artifacts using WSO2 Developer Studio ❖ Deploying artifacts Q &A
  3. 3. WSO2 Developer Studio 4.0.0 ❖ Introduction to WSO2 Developer Studio ➢ Developer Studio has moved into a kernel based architecture from 4.0.0 onwards ➢ What should the users know in migrating to WSO2 Developer Studio 4.0.0
  4. 4. WSO2 Developer Studio 4.0.0 ❖ What is the new architecture.. ➢ A kernel based architecture to better serve the tooling support for WSO2 carbon based products. ❖ What should I know as a Developer Studio user? ➢ How to Download and configure your own Developer Studio ?
  5. 5. Using WSO2 Developer Studio 4.0.0
  6. 6. Set up you own Developer Studio Download Kernel + product plugin composite zip (eclipse + kernel + product tooling) Install additional tooling on the go Download Kernel + eclipse Install product tooling on the go Download Kernel only composite zip (eclipse + kernel) Install product tooling on the go Existing eclipse instance ? Install kernel / product tool (P2/ download zip and install ) Install additional tooling on the go
  7. 7. Environment Specific Artifacts ❖ Why do we need environment specific artifacts ?
  8. 8. Environment Specific Artifacts ❖ Better maintenance and organization of artifacts ❖ Reduce effort of code repetition for different environments.
  9. 9. WSO2 Recommended approach ❖ Small scale developments - Maven placeholder based artifacts ➢ Single capp based simple artifacts with one or two endpoint definitions ➢ Endpoint URLs can be configured during build time ❖ Large scale developments - Greg based registry artifacts for dynamic content ➢ multiple capps and multiple endpoints ■ with mounted registry (shared) - different resource paths for resources ■ with separate registry + ESB instances - same resource path for resources
  10. 10. Large Scale Deployments ESB Artifacts Greg Artifacts Greg Artifacts Greg Artifacts DEV Endpoint PROD Endpoint QA Endpoint
  11. 11. Deployment You have to use shared registry with mounting to facilitate this without duplicating your ESB artifacts. If you use separate registry paths in a shared registry without mounting, you will have to maintain duplicate ESB artifacts.
  12. 12. Demo o Sample Use-case oWSO2 Developer Studio download and configuration oWSO2 ESB Artifact Creation oWSO2 Greg Artifact Creation oMaintenance of Environment Specific artifacts
  13. 13. Questions?
  14. 14. Contact us !

×