Web parts for JEE portals

<< Click to Display Table of Contents >>

Navigation:  Bizagi Studio > Bizagi from external applications > Portals integration > Using Web parts for other portals >

Web parts for JEE portals

Overview

As mentioned at Using Web parts for other portals, the following article gives you a broad guideline about how to configure your web parts when using a JEE Bizagi Project.

We are already using Federated authentication for our JEE Bizagi project, and for the sample Intranet portal, which is set up with Liferay Enterprise.

For more information about setting Federated authentication in Bizagi, refer to Federated Authentication.

 

What you need to do

Perform the following steps in order to integrate Bizagi Web parts with your Portal

 

1. Ensure you have a SSO mechanism for your portals.

You will need to rely on a Single Sign-On mechanism to share authentication between your portal and Bizagi's Work portal. In our example, we will use OpenAM Enterprise.

 

2. Edit your portal's content so that you instantiate Bizagi Web parts.

In our example, we will create a new tab in which the Widget content will be rendered.

 

Example

1. Ensure you have a SSO mechanism for your portals.

In Bizagi, a Federated Authentication setting covers this aspect, provided that your other portal supports Federated authentication..

In your Bizagi project, making sure you use Federated authentication is done at the Security module:

 

FederatedAuthentication

 

Once you have activated Federation authentication in Bizagi, you will need to integrate Bizagi JEE and your Portal (Liferay Enterprise) with your Identity Provider (OpenAM).

 

2. Edit your portal's content so that you instantiate Bizagi Web parts.

Once you have integrated Bizagi JEE and your Portal with the identity Provider, It's time to create the space to render your Web parts in the Portal.

To do this, it is necessary to perform two steps:

 

2.1 Contextualize the web part with the SSO session.

When you open your Portal (Liferay) and you are authenticated by your Identity provider (OpenAM), the container to be created needs to contextualize the web part with the current SSO session.

For this purpose, you need to create an element in which you need to do build an interface with the following steps

 

Invoke Bizagi Authentication service, which is located in https://[BIZAGI_SERVER]:[Port]/BizAgi-war/saml2/login.

The invocation of the previous services will respond with 2 values: A session cookie to be evaluated and a URL to redirect the login.

 

We have created an example JavaScript code in order to perform the contextualization, this code can be downloaded here.

 

The execution of the element must be after the user's login.

 

2.2 Create Web part container in your Portal

You may this through an IDE or editor of your choice, or done directly in the Administration Module of your portal if it has that option.

 

For our example using Liferay, we just need to create the container and paste the respective URL of the web part to be rendered.

To do this, log in Liferay using an admin user, then create a new page and add a new IFrame to it.

 

Webparts_JEE_01

 

In the Source URL field, add the following:

 

http://[BIZAGI_SERVER]:[PORT]/BizAgi-war/jquery/webparts/desktop/portal/pages/webpart.htm?type=[WEB_PART]

 

Notice that in the URL above, you should consider assigning values to:

[BIZAGI_SERVER]: Your Application server on which Bizagi's project is hosted.

[PORT]: The port of your Application server.

[WEB_PART]: The internal name of the Web part. To use Bizagi's work portal this value should be specified as workportal or you may specify from the options described at Web parts types and parameters.

 

Click on Save when finish.

 

Once this step is successfully completed, our Corporate portal with Bizagi Web Part, should be looked like this:

 

Webparts_JEE_02

 

As we selected the workportal in the type of Web Part, we have available the same options than in Bizagi Work Portal, depending on the type selected, this look will have different ways to be rendered