Web application needs to applications should be added to the app manager and should be published in order App Manager for users to consume the web application. Below sections describe the process in detail on how to add a start using them. Details of the process of adding a web application to App Manager is described below.
Table of Contents
Anchor Step 1 : Add web application to the publisher Step 1 : Add web application to the
| Step 1 : Add web application to the publisher | |
| Step 1 : Add web application to the |
...
publisher
Step 1 :
| publisher |
...
Adding web application to the
...
publisher
This is the first step that needs to be done in the process of web application publishing. Follow the steps below to add the web application to App Manager.
| Info |
|---|
Adding a web application to |
...
App Manager doesn’t mean that |
...
it is hosted in |
...
App Manager. It can be hosted |
...
in any server, and |
...
the URL will be exposed through |
...
Descriptions of important fields are described below.
...
App Manager. |
- Log in to the publisher.
- Click Add Web App.
- Enter details of the web app as follows and click Add.
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 login. This will be explained in detail later in this documentlogging in. |
Context | Sub context of the web application. Gateway URL for 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 for 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 | Here users can add URL patterns, throttling tiers and whether to skip throttling for the URL pattern or not. For example, if javascript Javascript requests should not be throttled, user can simply add a URL pattern with 'Skip ThrottelingThrottling' is being set to true. |
Anchor Step 2 : Promote lifecycle state
| Step 2 : Promote lifecycle state |
Promote Web Application to Published State
Step 2 : Promote lifecycle state
Step 2 : Promote lifecycle state
| Step 2 : Promote lifecycle state |
After adding the web application to the publisher, you need to promote its lifecycle state to publish it as follows.
Promoting web application to published state
Once a web application is added to app managerApp Manager, it is added to the registry as an asset, and a lifecycle is attached to the web application. The Lifecycle State lifecycle state for a newly created web application is 'Created'. Users can change the state to 'In-Review', which will automatically initializes initialize a work flow event. Work flows will be explained in another section. Once an ' admin ' user approves the work flow event, then lifecycle goes state moves to the 'Published' state and will appear in the Store store for users to consume. This behavior can be extended according to the user requirement with the provided extension points.
Once a web application correctly goes to reaches the 'Published' state, user can find an API resource will be created under <APPM<PRODUCT_HOME>/repository/deployment/server/synapse-configs/default/api folder/ 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.
As the next step we After promoting the lifecycle state of the added web 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.