This site contains the documentation that is relevant to older WSO2 product versions and offerings.
For the latest WSO2 documentation, visit https://wso2.com/documentation/.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Created Web applications should be published in App Manager for users to start using them. 


Promoting web application to published state

After adding the web application to the publisher, you need to promote its lifecycle state to published state, to publish it as follows.


Once a web application is added to App Manager, it is added to the registry as an asset, and a lifecycle is attached to the web application. The lifecycle state for a newly created web application is 'Created'. Users can change the state to 'In-Review', which will automatically initialize a work flow event. Work flows will be explained in another section. Once an admin user approves the work flow event, then lifecycle state moves to the 'Published' state and will appear in the store for users to consume. This behavior can be extended according to the user requirement with the provided extension points.

Once a web application reaches the 'Published' state, an API resource will be created under <PRODUCT_HOME>/repository/deployment/server/synapse-configs/default/api/ directory. Name of the file will be {web app created user}–{web app name}_v{version}.xml. This is the REST endpoint, which will be invoked once the gateway URL is accessed. 

After promoting the lifecycle state of the added web application, you need to configure security for it. For information on configuring security for web applications, see Securing with SAML2 SSO.

  • No labels