Stephan Freudl's picture

As Marie announced last week - MashZone 2.1 is available now. It comes with a variety of new features. One major aspect of this version was webMethods integration. In this article I am going to describe how to embed MashApps into My webMethods, SAG's portal application framework.

My webMethods server (MWS) provides the user interface for many SAG products, like our all new Business Events offering published at CeBIT 2011. Integrating MashApps into other sites was introduced last year already, however, Single Sign On support was pending.
From now on embedded MashApps might be password protected as well as convenient to use at the same time. This works as you can instruct MashZone 2.1 to trust an authentication entity, MWS in this article. Therefore, once authenticated against MWS you don't need to log into MashZone again to include a password protected app.

The article assumes that both systems are connected to the same central user database, already. And, of course you need a MashApp to include within MWS. The next thing you need to install before configuration begins is the all new MWS visualization portlet. It is part of the SAG installer and configuration should be straight forward.

Now, having both systems up and running there are some values in to be edited. This configuration file resides in the sub folder system of MashZone's installation directory. By updating five keys you are specifying which entity MashZone is going to trust. As you might recognize the SSO protocol both products rely on is SAML. Each of the five keys start with mashzone.saml.  and the comment nearby suggests proper values already. All you need is host name and port number of MWS. After changing the configuration you need to restart the MashZone server.

In MWS the MashZone portlet can be -- once installed and activated -- promoted to become a workspace tool. This is normally done using the sysadmin account.
The MashZone workspace tool enables you to to populate the canvas of an empty or existing workspace as depicted below.

Please note, the user Administrator is currently authenticated in MWS. This user is eligible to use MashZone, too. Until now the MashZone portlet shows an empty frame, only. Editing its properties enables you to point it to a MashApp's URL.

As soon as you accept the settings the frame loads the MashApp - without any subsequent authentication request. The link to the MashApp can be obtained in MashZone via the Share dialog. It might be useful to remove the MashZone branding while embedding it.

Finally your MWS view looks like this; the MashApp is show without authenticating Administrator again. If somebody invokes the link for the MashApp outside MWS, MashZone asks for user credentials.