You can manage the lifecycle of Web application needs to be added to the app manager and should be published in order for users to consume the web application. Below sections describe the process in detail on how to add a web application to the app manager.
Step 1 : Add Web Application to the Publisher
This is the first step that needs to be done in the process of web application publishing. Adding a web application to the app manager doesn’t mean that the web application should be hosted in the app manager. Web application can be hosted anywhere and only the URL will be exposed through app manager. Prior adding a web application, user needs to login to the publisher. Below is a screen capture of the add web application page.
Descriptions of important fields are described below.
...
Name of the field
...
Description
...
Name
...
Name of the application. This is the field which will be used as the SAML2 issuer at the time of login. This will be explained in detail later in this document.
...
Context
...
Sub context of the web application. Gateway URL for web application contains the context provided in this field
...
Version
...
Step 2 : Promote lifecycle state
Promote Web Application to Published State
...
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 definitionsYou 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 |
...
|
...
initialize a work flow event. |
...
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 |
...
under |
...
|
...
be |
...
|
...
|
As the next step we After promoting the lifecycle state of the added application, you need to configure security for web application as describes hereit. For information on configuring security for Web applications, see Securing with SAML2 SSO.