Page tree
Skip to end of metadata
Go to start of metadata


The full text of this page is only available to our customers.

Please login or sign up. You may also need to provide your support ID if you have not already done so.

Discover with BMC Discovery
download

This product can be discovered by Enterprise version of BMC Discovery, but you can still Download our free Community Edition to discover [other products] !

What is this?
This is a product information page, containing details of the information that BMC Discovery gathers about a product and how it is obtained.
Product Name
iProcess
Publisher Page
TIBCO
Category
Process Automation Middleware
Release
TKU 2019-Aug-1
Change History
TIBCO iProcess - Change History
Reports & Attributes
TIBCO iProcess - Reports & Attributes
Publisher Link
TIBCO

Product Description

TIBCO iProcess provides a wide range of BPM functionality, ranging from the Eclipse based modeling and simulation environment, through a highly scalable process engine, into process monitoring and analytics. The various components can be mixed and matched, depending on client objectives.

Architecture

Known Versions

The modern version of the product has components TIBCO iProcess Engine, TIBCO iProcess Objects Server and TIBCO iProcess Workspace. It has known versions

  • 11.1
  • 11.3
  • 11.4
  • 11.5
  • 11.6

Legacy versions (prior to 10.0) have components Staffware Process Engine, Staffware Process Objects Server and Staffware Client. They have known versions

  • 9.0

Software Pattern Summary

Product Component

OS Type

Versioning

Pattern Depth

TIBCO iProcess EngineUnixActive, FileInstance-based
TIBCO iProcess Objects ServerUnixActiveInstance-based
TIBCO iProcess WorkspaceWindowsRegistry, PackageInstance-based

 

Platforms Supported by the Pattern

The patterns discover TIBCO iProcess deployed on UNIX and Windows platforms.

Identification

Software Instance Triggers

Pattern

Trigger Node

Attribute

Condition

Argument

iProcessEngineDiscovered Process  unix_cmdmatches'procmgr'
and
argsmatches regex "WATCHER"
ObjectsServerDiscovered Processunix_cmdmatches'swentobjsv'
iProcessWorkspaceDiscovered Processwindows_cmdmatches 'staffw'

 

Simple Identification Mappings

The trigger process is given a simple identification mapping:

Name

Command

Arguments

'TIBCO iProcess Engine'

unix_cmd 'procmgr'

regex 'WATCHER'

Name

Command

'TIBCO iProcess Objects Server'

unix_cmd 'swentobjsv'

'TIBCO iProcess Workspace'

windows_cmd 'staffw'

'TIBCO iProcess Work Queue Server'

unix_cmd 'wqsrpc'

'TIBCO iProcess Work Item Server'

unix_cmd 'wisrpc'

'TIBCO iProcess WIS MBOX Daemon'

unix_cmd 'wismbd'

'TIBCO iProcess RPC Pool Servers'

unix_cmd 'swrpcsvr'

'TIBCO iProcess Deadline Manager'

unix_cmd 'dlmgr'

'TIBCO iProcess RPC Background'

unix_cmd 'staffrpcbg'

'TIBCO iProcess Background'

unix_cmd 'swbgmbd'

'TIBCO iProcess RPC UDP listener'

unix_cmd 'swrpcudp'

'TIBCO iProcess Objects Director'

unix_cmd 'spodirector'

Obtaining install root

The ObjectsServer pattern extracts install root from the process command using regex :

  • "(/\S+)/bin/swentobjsv"

The iProcessEngine pattern extracts install root from the process command using regex :

  • (/\S+)/etc/procmgr

Obtaining the version information

Active versioning

 iProcessEngine pattern runs the command :

  • PRIV_RUNCMD %swdir_home%/etc/procmgr -v

From the command output extracts full version using regex :

  • (\d+(?:\.\d+)+)

 ObjectsServer pattern runs the command :

  • PRIV_RUNCMD %swdir_home%/bin/swentobjsv -v 

From the command output extracts full version using regex :

  • (\d+(?:\.\d+)+)

File versioning

iProcessEngine pattern looks for the <swdir_home>/logs/swinstall.dat file.

If the file exists pattern will extract the full version using regex :

  • '(?i)TIBCO\s+iProcess\s+Engine\s+\(\s*(\d+(?:\.\d+)+)\s*\)'

Registry versioning

iProcessWorkspace would use the registry query like :

  • HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Staffware plc\\TIBCO iProcess Workspace (Windows)\\

From the query output pattern extracts full version using regex :

  •  '(\d+(?:\.\d+)+)'

Package versioning

iProcessWorkspace would look for the package name like :

  • iProcess Workspace

If succeed, full version will be taken from the package version field.

Obtaining database details

iProcessEngine pattern looks for the Oracle DB details in the /home/%process_username%/.profile file.

Like TNS_ADMIN and TNS_ALIAS.

If these two values are found pattern will use getSoftwareNodes() function to find Oracle Database Server SI and create link to it.

Application Model Produced by Software Pattern

Software Pattern Model

Pattern Trigger

The iProcessEngine pattern triggers on a procmgr process with WATCHER option in its arguments.

The ObjectsServer pattern triggers on a swentobjsv process .

The iProcessWorkspace pattern triggers on a staffw process.

SI Depth

 iProcessEngine and  iProcessWorkspace  patterns create an instance-based Software Instance with the key based on SI type, and the host key.

The ObjectsServer pattern creates an instance-based Software Instance with the key based on SI instance, type, and the host key.

Software Instance Modeling

Software Instance details of the TIBCO iProcess generated with this pattern:

Software Context view

The image below is an example of software context view of the TIBCO iProcess and related software:

Relationship creation

The patterns create the following relationships:

  • Client server communication between the TIBCO iProcess Engine and Oracle Database Server
  • Client server communication between the TIBCO iProcess Objects Server and TIBCO iProcess Engine
  • Client server communication between the TIBCO iProcess Workspace and TIBCO iProcess Engine

Subject Matter Expertise

Subject Matter Expert input will be welcome on any other potential approaches not discussed to improving product versioning coverage and depth of
TIBCO iProcess model.

Information Sources

https://docs.tibco.com/products/tibco-iprocess-engine-11-6-0

Open Issues

There are no known open issues with this pattern.

The full text of this page is only available to our customers.

Please login or sign up. You may also need to provide your support ID if you have not already done so.