Created Web applications should be published in App Manager for users to start using them. You can manage the lifecycle of Web applications you create in WSO2 App Manager as described below.
Table of Contents maxLevel 3
Excerpt |
---|
Introduction to |
...
app lifecycle managementThe application (app) approval process involves all the states in an application life cycle from creation to retirement. |
...
Your actions are restricted based on the permissions that |
...
are assigned to |
...
you. The following topics illustrate the application approval process |
...
. App lifecycle management action definitions |
...
You can carry out the following actions in the application approval process |
...
.
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
App lifecycle management based on user rolesThe transitions in the app approval process, together with the permissions needed at each state are listed as follows:
|
...
App lifecycle management statesAfter adding the |
...
application to the publisher, you need to promote its lifecycle state to published state, to publish it as follows. Once |
...
an application is added to App Manager, it is added to the registry as an asset, and a lifecycle is attached to the |
...
application. The lifecycle state for a newly created |
...
application |
...
is |
...
You can change the state |
...
to |
...
which will automatically initialize |
...
...
Once an admin user approves the work flow event, then lifecycle state moves to |
...
the |
...
state and will appear in the |
...
Store for |
...
you to consume. This behavior can be extended according to the user requirement with |
...
the provided extension points. Once |
...
an application reaches |
...
the |
...
state, an API resource will be created |
...
under |
...
directory. Name of the file will |
...
be |
...
|
...
|
After promoting the lifecycle state of the added web application, you need to configure security for it. For information on configuring security for web Web applications, see Securing with SAML2 SSO.