...
The fields on which you need to enter the values accordingly when adding a web application 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 logging in. |
Context | Sub context of the web application. Gateway URL of the web application contains the context that should be provided in this field. |
Version | Version of the web application. Users can have multiple versions of the same web application. Version will appear in the gateway URL. |
| Transport | The transport protocol used (For example: http/ https). |
| Web App URL | URL of the web application. This URL will be considered as the landing page for the web application. |
| URL Pattern | URL patterns, throttling tiers and whether to skip throttling for the URL pattern or not. For example, if Javascript requests should not be throttled, user can simply add a URL pattern with 'Skip Throttling' being set to true. |
Anchor Step 2 : Promote lifecycle state Step 2 : Promote lifecycle state
Step 2 :
Promote lifecycle | Step 2 : Promote lifecycle state | |
| Step 2 : Promote lifecycle state |
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.
Promoting web application to published state
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.
...