Configuring Portal Deployment

Usage

To configure the Portal Deployment

Depending on the configured portal server, not all the options listed below are available.

Call up

INUBIT Workbench > Configuration > General Settings > Portal > Portal deployment

Option Description

Portlets archive name

Default value for the name of the *.war file and the directory where the INUBIT portlets which are included in delivery are stored. You find the directory in <Liferay-installdir>/<Tomcat-dir>/webapps. The default value is suggested on deployment, you can enter any other name.

Task lists on the portal

The values 2/2 (initial state) show, that there are two task lists and both are active. If you add further task lists or deactivate existing task lists, these values are adjusted.

The button administration guide 176 0 opens a dialog where you can create new task lists are active and activate/deactivate existing task lists.

Refer to

Monitoring portlets on the portal

The values 1/1 (initial state) show, that there is one monitoring portlet and that it is active. The values always adjust to the number of configured and activated or de-activated monitoring portlets.

The button administration guide 176 0 opens the XSLT style sheet where you can define which monitoring portlets are active and what contents they display.

For information about configuring different monitoring portlets refer to Monitoring Portlets in the INUBIT Process Cockpit.

Report portlet

Activates the report portlet.

Name of the report portlet

Name of the report portlet.

Refer to Using the Report Viewer

URLs of the report portlet

Space-delimited list of the URLs of all servers for which data is to be collected for reports, to have them displayed in the report portlet.

Process portlet

Activates the report portlet.

Refer to Portlet Process Viewer in the INUBIT Process Cockpit

Name of the process portlet

Name of the process portlet.

URLs of the Process Portlet

Whitespace separated list of the URL of all servers for which process data is to be collected, to have them be displayed in the process portlet

Portlet archives (Administration/ Deployment)

To display this option you must first configure a portal server.

The button opens a dialog, in which you can assemble web applications of the INUBIT Process Engine to a portlet archive and make them available on the configured portal server.

You need to re-deploy portlets after performing the following actions:

Task lists: creating, activating, deactivating, changing name or category
Monitoring-Portlets: creating, activating, deactivating, changing name or category
Web Application Connector: creating, activating, deactivating, changing name, changing category, changing permissions After all other actions, as for example modifications at modules in the portlet workflow, it is sufficient to re-initialize the portlet.

Refer to

Download WAR

For exporting all portlets, so that they may, for example, be made available to an arbitrary portal server.

All portlets in the directory <liferay-installdir>/<tomcat-dir>/webapps/isp are compressed to a *.war file and stored into the selected directory.

For an overview over the portlets refer to the file <liferay-installdir>/<tomcat-dir>/webapps/isp/WEB-INF/portlet.xml.

Allow form proxy servlet only for this process engine

The form proxy servlet mediates certain parts of a form between the portlet and the process engine (e.g. Download buttons). For security reasons this is only allowed for this process engine, by changing this property arbitrary process engines can be allowed.

Configuring Documentation Modules for BPC

Usage

To create and deploy one or more documentation modules with different content and for different user groups to be accessible in the BPC portal.

Prerequisites

You have configured the Business Process Center as portal server.

Proceed as follows

Open the Administration > General Settings > Portal > Portal Deployment tab.

Click the icon administration guide 176 0 to open the DocumentationModule configuration file.

By default, it looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<DocumentationModule>
  <Portlet name="Documentation module" enabled="true">
    <displayDiagramTypes>
      <!--Use this option to filter by diagram types, Eg: bpd, technical, organigram,
          systemdiagram, constraintsdiagram, processmap-->
        bpd, technical, organigram, systemdiagram, constraintsdiagram, processmap
    </displayDiagramTypes>
    <userGroup>
      <!--Use this option to filter by user group Eg: BusinessProcessCenter, admin-->
    </userGroup>
  </Portlet>
</DocumentationModule>

Configure the following parameters to adjust the existing module as desired:

Portlet name="Documentation module" enabled="true"

The Portlet name must be unique.

If the enabled="true" option is set, the documentation module is visible in the BPC portal.

If the enabled="false" option is set, the documentation module is invisible in the BPC portal.

displayDiagramTypes

Filter the documentation module for the following diagram types. The options must be separated by a comma and a blank space.

Option Diagram type

Option	Diagram type
`bpd`	Business Process Diagrams
`technical`	Technical Workflow Diagrams
`organigram`	Organization Diagrams
`systemdiagram`	System Diagrams
`constraintsdiagram`	Business Object Diagrams
`processmap`	Process Maps

bpd

Business Process Diagrams

technical

Technical Workflow Diagrams

organigram

Organization Diagrams

systemdiagram

System Diagrams

constraintsdiagram

Business Object Diagrams

processmap

Process Maps

userGroup

Filter the documentation module for the following user groups. The options must be separated by a comma and a blank space.

Optional: To configure another documentation module, duplicate the Portlet section and configure it as described in step 3.
1. Adjust the name attribute. The new name must be unique.
2. Configure the displayDiagramTypes parameter.
3. Configure the userGroup parameter.
Save the changes.
To deploy the documentation module(s) as portlets to the BPC portal click at the Portlet archive (Administration/Deployment) option and choose the documentation module(s) to be deployed.
To remove a deployed documentation module, click the icon in the Action column in the Archives on portal server table.

Configuring Monitor Modules for BPC

Usage

To create and deploy one or more monitoring modules with different content to be accessible in the BPC portal.

Prerequisites

You have configured the Business Process Center as portal server.

Proceed as follows

Open the Administration > General Settings > Portal > Portal Deployment tab.

Click the administration guide 176 0 icon in the Monitor modules in BPC option line to open the MonitorModule configuration file.

When having patched from an INUBIT version earlier than 7.4.0.43, the value can be 0/0. After clicking the administration guide 176 0 icon and saving it changes to a value greater than 0/0, depending on how many monitoring modules are configured.

By default, it looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<MonitoringModule>
  <Portlet enabled="true" name="Demo System Log" id="demoSystemLog">
    <types>
      <!--Use this option to define the type of the Logs, Eg:systemLog, auditLog,
          queueLog, schedulerLog, connectionLog, keyLog-->
      <type name="Queue Log">
        <!--userDefinedColumn values for System Log and Queue Log will be dynamically
            deployed to BPC-->
            queueLog
        <statuscolor>
          <values name="Error">#FEC8C8</values>
          <values name="Suspend">#C8C8C8</values>
          <values name="Retry">#C8C8FF</values>
          <values name="Queued">#D1C3BB</values>
          <values name="Waiting">#FFFFC8</values>
          <values name="Processing">#C8FFC8</values>
        </statuscolor>
      </type>
      <type name="System Log">
        <!--userDefinedColumn values for System Log and Queue Log will be dynamically
            deployed to BPC-->
            systemLog
        <statuscolor>
          <values name="Error">#FEC8C8</values>
        </statuscolor>
      </type>
      <type name="Audit Log">auditLog
        <statuscolor>
          <values name="Error">#FEC8C8</values>
        </statuscolor>
      </type>
    </types>
  </Portlet>
  <Portlet enabled="true" name="Demo Process Log" id="demoProcessLog">
    <types>
      <!--Use this option to define the processLog type-->
      <type name="Process Log" tablename="" databaseName="">
        <!--Specify the process Log table in tableName attribute-->
        processLog
      </type>
    </types>
  </Portlet>
</MonitoringModule>

Configure the following parameters to adjust the existing module as desired:
- Portlet enabled="true" name="Demo System Log" id="demoSystemLog"
  
  The name and the id must be unique.
  
  If the enabled="true" option is set, the monitoring module is visible in the BPC portal.
  
  If the enabled="false" option is set, the monitoring module is invisible in the BPC portal.
- <type name="Audit Log">auditLog</type>
  - Filter the monitoring module for one or more of the following log types. A portlet can consist of several log types.
- <values name="Error">#FEC8C8</values>
  
  In the Status column, for each log type a default color code is configured, but you can change it.
- <type name="Process Log" tablename="" databaseName="">
  
  The tablename field, you can configure which data is to be visible in processlog.
  
  In case of non-IS Log database tables, in the databaseName field, you can configure the Database Connector name.
  
  Option Log type
  
  systemLog
  
  System Log
  
  auditLog
  
  Audit Log
  
  queueLog
  
  Queue Log
  
  schedulerLog
  
  Scheduler Log
  
  connectionLog
  
  Connection Log
  
  keyLog
  
  Key Log
Optional: To configure another monitoring module, duplicate the Portlet section and configure it as described in step 3.
Save the changes.
To deploy the monitoring module(s) as portlets to the BPC portal click at the Portlet archive (Administration/Deployment) option and choose the monitoring module(s) to be deployed.
To remove a deployed monitoring module, click the icon in the Action column in the Archives on portal server table.