Go2Group Go2Group Mashup · 2008-07-17 · Section 2 – Go2Group Mashup Overview Go2Group...

Go2Group, Inc. • 138 North Hickory Avenue • Bel Air, MD 21014 • (877) 442-4669

www.Go2Group.com

Your Productivity Force Multiplier

Go2Group

Go2Group Mashup ClearCase UCM Mashup for Serena Business Mashup Solution

Installation and Usage Guide


www.Go2Group.com


Go2Group

Table of Contents

Section 1 – Go2Group Mashup Requirements .....................................................................3 What’s Needed .......................................................................................................3 Where to Get Help ...................................................................................................3

Section 2 – Go2Group Mashup Overview ...........................................................................5 Use Cases ..............................................................................................................6 Use Case Example ....................................................................................................6 Application and Orchestrations ....................................................................................6

Section 3 – Go2Group Mashup Installation.........................................................................7 Installation Assumptions ............................................................................................7 G2G ClearCase Share Trigger Components Installation.........................................................9 G2G ClearCase Web Services Component Installation ........................................................ 16 G2G SBM Component Installation ................................................................................ 20

Section 4 – Embed G2G Component in workflow............................................................... 26 Section 5 - G2G Workflow Configuration......................................................................... 33

Add Two Target Servers to environment ....................................................................... 33 Add Endpoints to Environment ................................................................................... 35 Add Values for the UCMConfig Auxiliary table ................................................................. 36 Add Values for the G2G_LICENSE Auxiliary table.............................................................. 39 Create UCM Activity ............................................................................................... 41 Change Lock State of a UCM Activity............................................................................ 44

Section 6 - Go2Group Mashup Tips and Troubleshooting..................................................... 47 General Suggestions ............................................................................................... 47 Updates and Upgrades............................................................................................. 47

Section 7 – Go2Group Mashup Additional Information ........................................................ 48 Technical Support .................................................................................................. 48 Sales Support........................................................................................................ 48 Learn More .......................................................................................................... 49


www.Go2Group.com


Go2Group

Section 1 – Go2Group Mashup Requirements

What’s Needed To install the Go2Group ClearCase UCM add-on for Serena, you will need the following:

• Serena Business Mashup Server

• For more information on Serena’s Business Mashup Solutions, please visit the Serena website at: www.serena.com/mashups.

• IBM Rational ClearCase

• Go2Group ClearCase UCM add-on for Serena Business Mashup (Go2Group CaT Mashup – UCM)

• Either Tomcat or JBoss on the Perforce. If you don’t have either, you will need to install one before beginning installation.

• Note: it is not required to install Tomcat or JBoss on the same server as the Subversion Server. While installation can be on separate servers, this will take some minor installation assistance from Go2Group.

• For Tomcat, version 5.5 or higher is required.

• Go2Group recommends Tomcat.

• For JBoss, version 4.0.5 or higher is required.

• Java JRE 1.5.12 or higher is required.

In addition to the technical requirements above, you will need administrator-level permissions on the Serena Business Mashup Server and IBM Rational ClearCase when installing the Go2Group Mashup.

Where to Get Help Go2Group provides support for its entire line of products, including Go2Group Mashups. Go2Group support is available by telephone, email, and a Go2Group Mashup specific customer support ticket system:


www.Go2Group.com


Go2Group

• By telephone

• For the Americas and EMEA+1 (877) 442-4669

• For Japan +81 3 5326 3073

• For the rest of APAC and Australia +886 2 2708 8473

• By email: [email protected]

• By ticket: support.Go2Group.com

A customer login is required to access the support site above. Please contact Go2Group for your login credentials.

For support with Serena Business Mashup, please contact your Serena representative.

For support with IBM Rational ClearCase, please contact your IBM representative.


www.Go2Group.com


Go2Group

Section 2 – Go2Group Mashup Overview

Go2Group leverages Serena's new process-driven, Mashup approach, allowing Mashup users to view ClearCase change history related to specific incidents, without ever having to leave Serena® Business Mashups. Go2Group's ClearCase UCM add-on for Serena Mashup (Go2Group CaT Mashup – UCM) displays ClearCase data within Serena's tabbed interface.

Using Serena Business Mashups, a tester simply logs an incident into the Serena interface. If there is a ClearCase change history log associated with the specific incident, the "Version Control" tab will provide a description of the changes made. The user can review change history information such as:

• The user who made the change

• The date of the change

• The location of the change

• The change history ID

• The check-in comment

The display of related change history within Serena helps keep the process flowing by providing users the information needed to make timely decisions.


www.Go2Group.com


Go2Group

Use Cases Actors - All members of the Test and Development Teams including:

• Test engineers using Serena

• Developers using ClearCase

• Code/peer review participants

Products Involved:

• Serena Business Mashup for test environment

• ClearCase client for developers change management environment

Questions Being Answered:

• Which source files have been checked in to resolve a specific incident?

• When were source files checked in to resolve a specific incident?

• Who checked in source files to resolve a specific incident?

• What check-in comments are available?

• Who reviewed the changes?

Use Case Example

• Issue logged in Serena

• Developer is assigned the issue by creating a UCM activity

• Developer modifies files and checks them in to ClearCase

• Developer marks the issue as 'resolved' and transitions the issue to "Peer Review"

• The issue now displays the change history of files changed

Application and Orchestrations The ClearCase add-on for Serena Mashup contains the following applications and orchestrations:

• ClearCase add-on for Serena Application – Sample workflow, containing the ClearCase add-on for Serena Orchestration, that displays ClearCase version control history

• ClearCase add-on for Serena Orchestration – Communicates with ClearCase server to create a UCM activity and to change the lock state property of an activity for specific issues


www.Go2Group.com


Go2Group

Section 3 – Go2Group Mashup Installation

This installation wizard is used to install components for the integration between ClearCase under the UCM environment and the Serena Business Mashup (SBM). The installation includes three separate installation shields, two on the ClearCase Server and One on the Mashup Server. This section covers all three installation shields:

• Go2Group ClearCase Share Trigger Components on the ClearCase Server: This is used to install ClearCase triggers and programs for check-in/check-out files that update data to the SBM server.

• Go2Group ClearCase Component on the ClearCase Server:

This is for the ClearCase server to provide web services interface let Business Mashup flow to create UCM activities.

• Go2Group SBM Component on the Serena Business Mashup Server:

This is for the SBM server to provide web services interface let ClearCase triggers to update any change history.

Installation Assumptions The following installation steps assume has completed the following:

• A local copy of the Go2Group Mashup installation file has been downloaded from the Go2Group website (www.Go2Group.com).

• A license key has been requested / received from Go2Group.

• The installer has the appropriate privileges to the Serena and IBM servers, along with the connected database(s).

• You have coordinated with the SBM, and ClearCase administrators to obtain support and recycle the servers.


www.Go2Group.com


Go2Group

Installation

There are THREE separate install shields needed to install this Mashup.

• ONE: The G2G SBM Components, which are Go2Group WAR files that need to be placed on the Mashup Server.

• TWO and THREE: The G2G ClearCase Component consist of Go2Group Java WAR and G2G ClearCase Share Trigger Components which need to be placed on the ClearCase Server. These are two separate install shields.

• Users don’t need to install anything at all since the triggers are installed on the ClearCase Server.


www.Go2Group.com


Go2Group

G2G ClearCase Share Trigger Components Installation To install the G2G ClearCase Share Trigger Components installation, double click the G2GCCComponent_windows_0_3.exe installation file to launch the installation wizard. The installation wizard appears. Click the Next button to continue the installation.

Review the Go2Group End User License Agreement. After agreeing to the EULA, select the I Accept the Agreement option and click the Next button.


www.Go2Group.com


Go2Group

The G2G ClearCase Share trigger component is pre-selected for you. You only need to click Next to continue.

Next, decide which folder will be the installation root for the ClearCase Trigger Component, your View Name, and your View Path. This is a little bit difficult, and you will need to make decisions, so make sure your ClearCase Admin is by your side for this step!

There are two basic options for triggers:

• Some triggers are applied to the entire VOB. This is what we recommend. However, your ClearCase Admin may not want this option as it may be enforced to all VOB users. This is the type of trigger we will talk about and the type our install shield supports.

• Other triggers are applied to some specific elements or types. We do not support this type of trigger in the install shield. In this case, the ClearCase Admin should have SOP ways of dealing with these types of triggers and will know where to copy the trigger files to.

You should have the ClearCase Admin choose the following three locations: • Location for the root directory for the Go2Group ClearCase Share Trigger component,

Go2Group recommends selecting a shared directory for the root installation such as C:\g2g-mp. • The View Name. This is the View Name that the ClearCase Admin will use to install the triggers

and will become part of the View Path such as G2G_DEMO_Integration. • VOB Name. This is the name of the VOB that you will apply the triggers to. This will become

part of the View Path Name such as SBM_UCM_DATA. The View Path name consists of View Name + VOB Name:

M:\G2G_DEMO_Integration\SBM_UCM_DATA


www.Go2Group.com


Go2Group

Now, enter the root directory for the Go2Group ClearCase Share Trigger component in the window below.

Before the G2G ClearCase Share Trigger component can continue installation, a shared directory should be created. Click the Next button to continue and install the trigger components.


www.Go2Group.com


Go2Group

If you want to change the location of the triggers in the future, you can re-run this install shield.

After the shared directory is created, the installer copies files to the destination directory.

Once the files have been copied to the destination directory, the installer will request input values to create configuration files. There are three required fields:

• Product Name: Found in the license file provided by Go2Group.

• Mashup Bridge License Key: If you have not received a license key, please contact Go2Group.

• Go2Group SBM Server Side Web Services Endpoint: Users can use the default value to modify the server IP and port number. For additional information, please contact your SBM administrator. This is the location of the SBM Web Services Endpoint URL. EX: http://mashup_server:8085/mashupmgr/services/SCMServices


www.Go2Group.com


Go2Group

After entering the required values, click the Next button to continue.

Next, the installer will help you to install triggers by your input.

There are three required values those you have to input:

• The View Name: This is the View Name that the ClearCase Admin will use to install the triggers and will become part of the View Path such as G2G_DEMO_Integration.

• The element VOB Name: This is the name of the VOB that you will apply the triggers to. This will become part of the View Path Name such as SBM_UCM_DATA.

• The Trigger Shared Folder: Location for the root directory for the Go2Group ClearCase Share Trigger component, Go2Group recommends selecting a shared directory for the root installation such as \\cc_server\g2g-mp.


www.Go2Group.com


Go2Group

After entering the required values, click the Next button to continue.

Click the Next button to continue.


www.Go2Group.com


Go2Group

You have now completed installing the triggers.


www.Go2Group.com


Go2Group

G2G ClearCase Web Services Component Installation This step will install the Go2Group g2g-ws.war war file, not the ClearCase Triggers, the triggers were installed in the previous step.

To install the G2G ClearCase Component installation, double click the G2GCCComponent_windows_0_3.exe install shield file to launch the installation shield. The installation wizard appears. Click the Next button to continue the installation.



www.Go2Group.com


Go2Group

Before continuing the installation of the G2G ClearCase Component in the image below, ensure there is a current installation of Tomcat or JBoss on the ClearCase server. If not, please install Tomcat/JBoss on your ClearCase server.

The Tomcat/JBoss server MUST be started by a ClearCase administrator account.

The installation location of the Go2Group jar files will vary depending upon if you are using JBoss or Tomcat.

• For the G2G ClearCase Component being installed into Tomcat, you should install the jar files here: %apache-tomcat-install-root%\webapps

• For the G2G ClearCase Component being installed into JBoss, you should install the jar files here: %JBoss-install-root%\server\default\deploy

If the installation root does not exist, the installer will ask to create it automatically, you will need to say yes.

So you need to choose the installation directory.


www.Go2Group.com


Go2Group


Click the Next button to install the war file and continue.


www.Go2Group.com


Go2Group

Next, you will need to restart Tomcat or JBoss depending upon which one you deployed to.

You can choose to restart using the screen below, or choose to skip it and restart manually later. Before restarting any server, you will need to check with the server admin first.

Congratulations, you have completed this step.


www.Go2Group.com


Go2Group

G2G SBM Component Installation During this process, you will need to stop the SBM Server (Serena Common JBoss Service). Please coordinate with the SBM Server Admin.

Locate the installation file G2GSBMComponent_windows_0_3.exe to begin the G2G SBM Component installation. Double click the installation file to launch the installation wizard. The installation wizard appears. Click the Next button to continue the installation.



www.Go2Group.com


Go2Group

After you agree, you will need to click Next in the Select Components screen below. There is only one component, G2G SBM Component and it is preselected.

Make sure that the SBM Server (Serena Common JBoss Service) is turned off as mentioned above.

Next, decide which folder will be the installation root for each component.

For the G2G SBM Component, Go2Group recommends using the default directory as the root installation but it must be set to the location of the Serena installation. For example, C:\Program Files\Serena

If the installation root does not exist, the installer will ask to create it automatically. When prompted, say yes.



www.Go2Group.com


Go2Group

Again, before continuing to install this component, please ensure the SBM Server (Serena JBoss) service has been stopped (on Windows from the Services screen).

To stop the SBM Server (Serena JBoss Server), click Stop in the window below.

And the windows will help you to stop the service.


www.Go2Group.com


Go2Group

After you stop the Serena Common JBoss Service, go back to the installer.

Click the Next button to continue the installation.

The installer then copies the Mashup files to the destination directory.


www.Go2Group.com


Go2Group

Click the Next button to complete the Mashup portion of the installation.

Click the Finish button to complete the Mashup installation portion of the installation. However, you are not finished yet!


www.Go2Group.com


Go2Group

Now that the SBM Server (Serena Common JBoss Server) has stopped, and the deployment is completed, you need to restart the SBM Server (Serena Common JBoss Server), see screen below.

Before the Mashup will work, you have two more steps to do. You need to embed G2G component in workflow and configure G2G workflow. See the next two sections below.


www.Go2Group.com


Go2Group

Section 4 – Embed G2G Component in Workflow

This section is to introduce the G2G orchestration flows, workflow designers have to use the Serena Mashup Composer to import the G2GCreateActivityWorkflow and the G2GLockActivityWorkflow into your own application workflows. The G2G orchestration mashup file will be installed in C:\Program Files\Go2Group Mashups folder.

We provide two orchestration flows to create UCM activities and to change the lock state of an activity. The G2GCreateActivityWorkflow is provided to create UCM activities. The G2GLockActivityWorkflow is provided to lock/unlock UCM activities.

You may need to refer to Serena’s Mashup Documentation if you need help with workflows. Here is a generic workflow setup that will work for you. We recommend that you have the SBM Admin perform the following steps.

The G2GCreateActivityWorkflow orchestration flow is provided to let users create UCM activities within a Mashup application flow. Users can use the Business Mashup Composer to merge our orchestration flow with their application flow. A sample application flow containing the orchestration flow is also provided. The Go2Group Mashup is in the “CC Issue Defect Tracking.zip” file.


www.Go2Group.com


Go2Group

This orchestration flow contains two web services nodes.

• The first web service is from the SBM server. We invoke the GetItem service to get the issue’s issue name, such as: BUG00046.

• If there is a return value, then we invoke the second web service from the ClearCase server side. From the ClearCase server side web services, we can create an UCM activity based on this issue.

• If this issue has a different owner, then the third web services will change the activity owner to the specified ClearCase user.

Let us look into each web service’s data mapping:

In the aewebservices70 web service data mapping, every element is a required field (the most important field is itemID).

Next, map this field with the “Inputs/EventNotice/Extension/ItemId_TableRecId” field.


www.Go2Group.com


Go2Group

In the attachIssueWithSCM web service data mapping, the following fields are required (refer to image, next page):

Field Value Note

scmName CC This is a constant value

issue/issueId This value is from the response of the aewebservices70 node. We map it with: aewebservices70_GetItem/GetItemResponse/return/genericItem/itemName

Issue/issueTitle The issue title for the ClearCase activity headline.

Issue/tableId The table id which contains the issue record.

scmInfo/ productName CCM This is a constant value

scmInfo/stream This filed is to let ClearCase server knows which stream will create the new activity.

scmInfo/vob This field is to let ClearCase server knows which VOB will create the new activity.


www.Go2Group.com


Go2Group

In the changeOwner web service data mapping, the following fields are required (refer to image, next page):

Field Value Note


scmInfo/ scmName CC This is a constant value

scmInfo/stream This filed is to let ClearCase server knows which stream will create the new activity.

scmInfo/vob This field is to let ClearCase server knows which VOB will create the new activity.

owner The ClearCase user account that assigned to own this issue.


www.Go2Group.com


Go2Group

The G2GLockActivityWorkflow orchestration flow is provided to let users change the lock state of UCM activities within a Mashup Application flow. Users can use the Business Mashup Composer to merge our orchestration flow with their application flow. A sample application flow containing the orchestration flow is also provided. The Go2Group Mashup is in the “CC Issue Defect Tracking.zip” file.


www.Go2Group.com


Go2Group

This orchestration flow contains two web services nodes.

• The first web service is from SBM server. We invoke the GetItem service to get the issue’s issue name, such as: BUG00046.

• If there is a return value, then we invoke the second web service from the ClearCase server side. From the ClearCase server side web services, we can change the lock state of an UCM activity based on this issue.

Let us look into each web service’s data mapping:

In the aewebservices70 web service data mapping, every element is required field (the most important field is itemID).

Next, map this field with the “Inputs/EventNotice/Extension/ItemId_TableRecId” field.


www.Go2Group.com


Go2Group

In the SCMServices web service data mapping, the following fields are required (refer to image):

Field Value Note

scmName CC This is a constant value


scmInfo/ productName CCM This is a constant value

scmInfo/ licenseKey The license key string is from Go2Group license file.

scmInfo/stream This filed is to let ClearCase server know which stream will create the new activity.

scmInfo/vob This field is to let ClearCase server know which VOB will create the new activity.

state This field is to let ClearCase know whether the state is locked or unlocked.


www.Go2Group.com


Go2Group

Section 5 - G2G Workflow Configuration

This sample Mashup shows users how the ClearCase add-on for Serena Orchestration which can be used to create a UCM activity when an issue has been created.

Again, we recommend that you read Serena’s documentation and have a Serena Admin perform these steps for you.

Add Two Target Servers to Environment In Serena Business Mashup Manager, users need to add two target servers in their environment before deploying the sample application in the SBM server. One server is for the System Event Manager, and the other server is for the BPEL Server.

Click Environments and then Default Environment.


www.Go2Group.com


Go2Group

Create Target Servers.

Create one BPEL Server and one System Event Manager Server. Use View Examples to help choose right URL for different type. Leave Authentication option for “none”.

For example:

BPEL: http://sbmserver:8085/jbpm-bpel/services/DeployService


www.Go2Group.com


Go2Group

System Event Manager: http://sbmserver:8085/eventmanager/services/ALFAdmin

Add Endpoints to Environment In the Serena Mashup Manager, users need to add five endpoints in their environment prior to deploying the sample application. The five endpoints are:

• aewebservices70 endpoint is for SBM web services.

Example: http://sbmserver/gsoap/gsoap_ssl.dll?aewebservices70

• ALFEventManager endpoint is for the ALF event manager web services.

Example: http://sbmserver:8085/eventmanager/services/ALFEventManager

• G2GLockActivityWorkflow endpoint is for the activity lock state change web services.

Example: http://sbmserver:8085/G2GUCMOrchestration-G2GLockActivityWorkflow/g2glockactivityworkflowservlet

• G2GCreateActivityWorkflow endpoint is for create activity web services.

Example: http://sbmserver:8085/G2GUCMOrchestration-G2GCreateActivityWorkflow/g2gcreateactivityworkflowservlet

• SCMServices endpoint is for the Go2Group Clear Case Component on Tomcat or JBoss.

Example: http://ccserver:8080/g2g-ws/services/SCMServices


www.Go2Group.com


Go2Group

After we configured target servers and endpoints, we can deploy our own applications into the SBM server now.

We also have to load the mashup zip file that generated from Section 4, and then deploy the mashup. Please reference to Chapter 5 in the “Serena Mashup Manager Guide”.

Add Values for the UCMConfig Auxiliary table After users deploy the sample flow or users’ application flow to an SBM server and use the Mashup Administrator to add projects to use the flow, about how to add projects by using the Mashup Administrator, please reference to the Mashup Administrator Guide.

And then users need to use the Serena Business Mashup Web Interface to add configurations.

Users login into the web interface, and then they click on their applications, our example application is IDTCC.


www.Go2Group.com


Go2Group

Then click on the “Search” function and click on the “Manage Data” item to open the management page.

Choose the “UCMConfig”, click on the “Lookup” button, and then click on the “Create New UCMConfig” link to open a new page.


www.Go2Group.com


Go2Group

The UCMConfig configuration contains four required fields: SCMName, VOB, STREAM and LICENSE.

• SCMName: a constant value “CC”.

• VOB: pvob name that users want to use.

• STREAM: the ClearCase UCM stream name for the mashup. You can find the STREAM information from view properties in the Clear Case Explorer.

• LICENSE: a license key for with this mashup.

After completing this configuration, users can start to use the sample flow.


www.Go2Group.com


Go2Group

Add Values for the G2G_LICENSE Auxiliary table After users login into the SBM and then click on the “Search” function and click on the “Manage Data” item to open the management page.


www.Go2Group.com


Go2Group

Choose the “G2G_LICENSE”, click on the “Lookup” button, and then click on the “Create New G2G_LICENSE” link to open a new page.

The G2G_LICENSE configuration contains four required fields: CC_USER, TT_USER, and LICENSE_KEY.

• CC_USER: a ClearCase user account.

• TT_USER: a SBM user account.

• LICENSE_KEY: a license key for with this mashup.

After completing this configuration, users can start to use the sample flow.


www.Go2Group.com


Go2Group

Create UCM Activity A user logs into the Serena Business Mashup system and submits a new issue. In the submit form, the UCMConfig field must be set to CC. The SCM_User_Mapping field is then set to a ClearCase user who should own this issue.

Click the OK button (top of panel) to continue. When the OK button is clicked, the system will invoke the G2G UCM Mashup Bridge Orchestration flow automatically.


www.Go2Group.com


Go2Group

On the ClearCase server side, it will create a new activity named “1005_BUG00062_Demo bug” and it’s activity id is BUG00062, as displayed in the below picture.

Users can then use the ClearCase client tool to check out files and select the new activity as the target activity, then check those files out.


www.Go2Group.com


Go2Group

After users modify / check in the respective files and press the OK button, the program will update the change history record in Serena Business Mashup.

The next time a user logs in to Serena Business Mashup and opens BUG00062 issue, they will see new change history records in the “Version Control” tab.


www.Go2Group.com


Go2Group

Change Lock State of a UCM Activity Users can lock/obsolete or unlock an activity by clicking on the “Lock Activity” or “Unlock Activity” buttons to change the lock state.

First, we’ll display how the lock state changes to obsolete in the sample flow.

Users click on the “Lock Activity” button.

And then users need to decide which state they want to change.


www.Go2Group.com


Go2Group

After users click the OK button, they would then open the ClearCase client and would not see the activity in their activity list. In this example, the activity is related to BUG00062.

If users use the ClearCase command to list activities, they can see the BUG00062 is obsolete. The sample command is:

cleartool lsactivity –obsolete …


www.Go2Group.com


Go2Group

If users change the lock state to locked, the lock state will be reflected when they open the properties with an activity.

If the issue needs to be unlocked, simply click on the “Unlock Activity” button in the main issue window. The activity’s lock state is then reflected as unlocked in the ClearCase client.


www.Go2Group.com


Go2Group

Section 6 - Go2Group Mashup Tips and Troubleshooting

General Suggestions Go2Group provides technical support for its entire line of products, including Go2Group Mashups. If you run into any issues when installing or configuring the Go2Group Mashups, please contact us.

The following steps in blue are NOT steps you need to but are useful to your ClearCase Admin in case of trouble or in case you want to move them.

The g2g-cc-ucm-trigger.bat file gets copied to a shared folder (maybe where you installed it to) where it was installed to specified views and execute the g2g-cc-cum-trigger.bat. For example, if your network shared folder is on a machine called 'machinefortrigs', in a folder shared as 'sharefortrigs', run the script as:

g2g-cc-ucm-trigger.bat "\\machinefortrigs\sharefortrigs"

If the triggers already exist and you need to replace the triggers, run the command as:

g2g-cc-ucm-trigger.bat -r "\\machinefortrigs\sharefortrigs"

Updates and Upgrades Go2Group provides regular updates to Go2Group Mashups. These updates include performance enhancements and minor bug fixes.

Go2Group provides regular upgrades to Go2Group Mashups. These upgrades include new features, performance enhancements, and bug fixes.

To review previous, current, and upcoming updates and upgrades, please visit the Go2Group support site at:

support.Go2Group.com



www.Go2Group.com


Go2Group

Section 7 – Go2Group Mashup Additional Information

The Go2Group Mashup contains a sample application flow. The basic flow is the “IDT Base Workflow”. Go2Group includes an Action in submit transition. The action invokes an orchestration flow which is the G2G UCM Mashup Bridge Orchestration. In this sample flow, we use an auxiliary table to store stream, VOB, and license key values.

Users can deploy this sample flow to see how the orchestration flow works.

Technical Support Go2Group provides technical support for its entire line of products, including Go2Group Mashups. Go2Group technical support is available by telephone, email, and a Go2Group Mashup specific customer support ticket system:

• By telephone: (877) 442-4669




Sales Support Go2Group provides sales support for its entire line of products, including Go2Group Mashups. Go2Group sales support is available by telephone, email, and a Go2Group Mashup specific customer support ticket system:

• By telephone: (877) 442-4669





www.Go2Group.com


Go2Group

Learn More For more information on Go2Group, its products, and its services, please visit our website at:

www.Go2Group.com

For more information on Serena, please visit the Serena website at:

www.Serena.com

For more information on IBM, please visit the IBM website at:

www.IBM.com

Go2Group Go2Group Mashup · 2008-07-17 · Section 2 – Go2Group Mashup Overview Go2Group...

Documents

Transcript of Go2Group Go2Group Mashup · 2008-07-17 · Section 2 – Go2Group Mashup Overview Go2Group...