WebSphere

This information applies to feature pack. To use what is described, you must have installed the optional feature pack Deploying and configuring widgets for the feature pack

You must deploy and configure widgets for the IBM® WebSphere® Process Server V6.2 and WebSphere Enterprise Service Bus V6.2 Feature Pack before you and others on your team can begin using them in Business Space powered by WebSphere.

Before you begin
Before you deploy and configure widgets, you must complete the following steps:
  • Install the IBM WebSphere Process Server V6.2 and WebSphere Enterprise Service Bus V6.2 Feature Pack.
  • Configure Business Space, the user interface for the widgets, and all Representational State Transfer (REST) endpoints. For more information, see Configuring Business Space.
  • For WebSphere Process Server, if you are going to use the Human Task Management and My Work Organizer widgets, configure Business Process Choreographer. For more information, see Configuring Business Process Choreographer.
  • If you have multiple Business Process Choreographer containers configured, make sure that the serviceEndpointRef in the widget XML files HumanTaskManagementWidgets.xml and WorkOrganizerWidgets.xml points to the appropriate container. For more information, see Enabling Business Space widgets for multiple endpoints in the Configuring Business Space documentation.
  • Install Adobe® Flash Player on all systems where business users access Business Space. Adobe Flash Player V9 or later is required to properly view graphical features in widgets.
About this task

To install feature pack widgets, perform the following steps.

Procedure
  1. Run the configure62FeaturePack.py script, which is located in install_root\BusinessSpace\scripts.

    The configure62FeaturePack.py script installs the enterprise archive (EAR) file for the Administration widgets, the Human Task Management widgets, and the My Work Organizer widgets. It registers the widgets, and it registers templates for the widgets that you can use in Business Space.

    For the Administration widgets, the script configures the REST services. Service monitoring is configured by default on the System REST service deployment target.

    For the Human Task Management and My Work Organizer widgets, the script deploys query tables. Make sure that the server (or at least one member of the cluster) where Business Process Choreographer is configured is running before you run the script. For a deployment environment, the deployment manager must be running.

    Note: For a network deployment environment, run the script on both the deployment manager and one dedicated managed node where Business Space is deployed and where a cluster member is running. Before running the script, go to the administrative console and make sure to select Synchronize changes with Nodes on the Console Preferences page.
    Tip: If you have WebSphere Business Modeler Publishing Server or WebSphere Business Monitor installed separately from WebSphere Process Server or WebSphere Enterprise Service Bus and you are using a stand-alone profile, some of the widgets are not enabled until the REST service endpoints are configured. First, make sure that you have Solution Management widgets and Managing Tasks and Workflows widgets configured as part of WebSphere Process Server V6.2, or Solution Management widgets configured as part of WebSphere Enterprise Service Bus V6.2. Run the configure62FeaturePack.py script for WebSphere Business Modeler Publishing Server or WebSphere Business Monitor and then run it again for WebSphere Process Server or WebSphere Enterprise Service Bus. For the feature pack widgets, you must edit the administrationEndpoints.xml file in addition to the endpoints files for WebSphere Business Modeler Publishing Server, WebSphere Business Monitor, WebSphere Process Server, and WebSphere Enterprise Service Bus. For more information, see Enabling Business Space widgets manually for remote endpoints in the Configuring Business Space documentation.
    1. Include parameters for one or more widget sets that you want to deploy:
      • -administration for the Administration widgets (for use with WebSphere Enterprise Service Bus and WebSphere Process Server).
      • -humanTaskManagement for the Human Task Management widgets (for use with WebSphere Process Server).
      • -workOrganizer for the My Work Organizer widgets (for use with WebSphere Process Server).
      For example, run one of the following commands if you want to deploy all the widgets:
      • On Linux®, UNIX®, and z/OS® platforms: profile_root/bin/wsadmin.sh -f install_root/BusinessSpace/scripts/configure62FeaturePack.py -administration -humanTaskManagement -workOrganizer ...
      • On i5/OS® platforms: profile_root/bin/wsadmin -f install_root/BusinessSpace/scripts/configure62FeaturePack.py -administration -humanTaskManagement -workOrganizer ...
      • On Windows® platforms: profile_root\bin\wsadmin.bat -f install_root\BusinessSpace\scripts\configure62FeaturePack.py -administration -humanTaskManagement -workOrganizer ...

      If you do not specify one of these parameters, the Administration widgets are automatically deployed.

      You might need to include additional parameters, depending on the widgets and your environment, as described in the following steps.

    2. For WebSphere Process Server and the Human Task Management and My Work Organizer widgets, include the -bpcServer parameter to specify the deployment target where you want to configure the feature pack:

      -bpcServer (nodes:node_name:servers:server_name) | clusters:cluster_name

      If you have configured Business Process Choreographer, this parameter is optional. The script automatically deploys the query tables on the same target as the Business Process Choreographer container. If you have more than one Business Process Choreographer container configured, include this parameter to specify the deployment target where you want to configure the feature pack.

      Omit this parameter if Business Space connects to a Business Process Choreographer container in a remote cell.

    3. For Administration widgets, include the -scaServer parameter, which designates the server or cluster where the Service Component Architecture (SCA) modules are deployed:

      -scaServer (nodes:node_name:servers:server_name) | clusters:cluster_name

      If you are using the Remote messaging and remote support pattern, designate the application cluster.

      This parameter affects the Module Browser widget, which you use to list all the deployed SCA modules and select one for detailed inspection or administration.

      If you have configured Business Process Choreographer, this parameter is optional. The configure62FeaturePack.py script automatically deploys the SCA REST service on the same target and uses its configured host name, port, and transport type.

      Omit this parameter if Business Space connects to an SCA container in a remote cell.

      If you are using an HTTP server to access your Web modules for load balancing, you can use the optional parameters -scaRESTServiceProtocol, -scaRESTServiceHostName, and -scaRESTServicePort with the -scaServer parameter:

      -scaRESTServiceProtocol http://|https://

      -scaRESTServiceHostName host_name

      -scaRESTServicePort port_number

      If -scaServer is specified without these three parameters, the script defaults to the first cluster member or to the stand-alone server.

      Note: After you run the configure62FeaturePack.py script, if you want to modify the protocol, the host name, or the port for the SCA REST service, you must run the updateSCARESTServiceEndpoint.py script. Run one of the following commands on the deployment manager or the stand-alone server:
      • On Linux, UNIX, and z/OS platforms: profile_root/bin/wsadmin.sh -f install_root/BusinessSpace/scripts/updateSCARESTServiceEndpoint.py -scaServer (nodes:node_name:servers:server_name) | clusters:cluster_name -scaRESTServiceProtocol http://|https:// -scaRESTServiceHostName host_name -scaRESTServicePort port_number
      • On i5/OS platforms: profile_root/bin/wsadmin -f install_root/BusinessSpace/scripts/updateSCARESTServiceEndpoint.py -scaServer (nodes:node_name:servers:server_name) | clusters:cluster_name -scaRESTServiceProtocol http://|https:// -scaRESTServiceHostName host_name -scaRESTServicePort port_number
      • On Windows platforms: profile_root\bin\wsadmin.bat -f install_root\BusinessSpace\scripts\updateSCARESTServiceEndpoint.py -scaServer (nodes:node_name:servers:server_name) | clusters:cluster_name -scaRESTServiceProtocol http://|https:// -scaRESTServiceHostName host_name -scaRESTServicePort port_number
      where the -scaServer parameter defines the server or cluster where the SCA REST Services application is deployed. For a stand-alone server, this parameter is optional.
  2. Restart the Business Space Manager application.
  3. Log in to Business Space at http://host:port/BusinessSpace, where host is the name of the host where your server is running and port is the port number for your server.
  4. Create a space with the template for the widgets that you want to use.

    Templates and pages are available only for the widgets that you specified in step 1 when you ran the script. For example, if you did not specify the -humanTaskManagement parameter, the Advanced Managing of Human Tasks and Workflows template is not available. If you did specify the -humanTaskManagement parameter but not the -workOrganizer parameter, a space created from the Advanced Managing of Human Tasks and Workflows template contains an Organize Work page that points to Work Organizer widgets that are not deployed. In that case, delete the Organize Work page.

    1. Click Manage Business Spaces to open Business Space Manager.
    2. In the Business Space Manager toolbar, click the create space icon.
    3. In the Create Space window, type the name for the new space, select From a template, and select one of the following templates:
      • Extended Solution Management, which includes Module Administration and Service Monitoring pages for WebSphere Enterprise Service Bus and includes Module Administration, Business Calendars, Security, and Service Monitoring pages for WebSphere Process Server.
      • Problem Determination, which includes the Module Problem Determination and System Health Monitor pages for both WebSphere Enterprise Service Bus and WebSphere Process Server.
      • Advanced Managing of Human Tasks and Workflows, which includes My Work, Organize Work, Create Tasks, Manage Human Workflows, and Manage Human Tasks pages for WebSphere Process Server.
    4. Click OK. The window closes and the Business Space Manager lists the space that you created.
  5. Repeat step 4 for each group of widgets that you want to use.
What to do next

If you want to use the Service Monitor Graph widget, you must enable the service monitoring agent. For more information, see Configuring the service monitor.

If you want to use your feature pack widgets in WebSphere Portal, you must complete additional configuration steps:
  • Follow the steps in Configuring Business Space widgets for WebSphere Portal.
  • When you create portlets for the feature pack widgets, you must edit the Portal.iWidget.Xml.File= line of the portal.iwidgets.properties file before running the iwidget script. Designate one of the following XML files for the widgets that you want to use in WebSphere Portal:
    • AdminWidgetPortlets.xml for the Administration widgets (for use with WebSphere Enterprise Service Bus and WebSphere Process Server).
    • HumanTaskManagementWidgetPortlets.xml for the Human Task Management widgets (for use with WebSphere Process Server).
    • WorkOrganizerWidgetPortlets.xml for the My Work Organizer widgets (for use with WebSphere Process Server).
    For example, change the line in the portal.iwidgets.properties file to Portal.iWidget.Xml.File=AdminWidgetPortlets.xml if you want to configure the Administration widgets for WebSphere Portal.

task Task topic

Terms of use | Feedback


Timestamp icon Last updated: 23 June 2009


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic/com.ibm.websphere.wbpm.fep.psesb.620.doc/doc/tcfg_wpswesbfep_widgets.html
Copyright IBM Corporation 2005, 2009. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).