- 1 Product Description
- 1.1 Known Versions
- 2 Software Pattern Summary
- 3 Platforms Supported by the Pattern
- 4 Identification
- 4.1 Software Instance Triggers
- 4.2 Avoiding false positives
- 4.2.1 Obtaining the base directory
- 4.2.2 Checking for a file
- 4.3 Software Instance Type Attributes Created
- 5 Versioning
- 5.1 File versioning
- 5.2 Path versioning
- 6 Application Model Produced by Software Pattern
- 6.1 Product Architecture
- 6.2 Software Pattern Model
- 6.2.1.1 Pattern Trigger
- 6.2.1.2 SI Depth
- 6.2.1.3 Relationship Creation
- 7 Subject Matter Expertise
- 8 Testing
- 9 Open Issues
- Discover with BMC ADDM
-
This product can be discovered by any edition of BMC Atrium Discovery and Dependency Mapping. Download our free Community Edition to try it out, or see what else it can discover!
- What is this?
- This is a product information page, containing details of the information that BMC Atrium Discovery gathers about a product and how it is obtained.
- Product Name
- JBoss Portal
- Publisher Page
- Category
- Release
- TKU 2009-Mar-1
- Change History
- Reports & Attributes
- Publisher Link
- Red Hat
Product Description
JBoss Enterprise Portal Platform provides an integrated open source platform for hosting and serving a portal's web interface, aggregating, publishing, and managing its content, and personalizing its experience.
Known Versions
- 2.2.1
- 2.4.2
- 2.6.4
- 2.6.6
- 2.7
Software Pattern Summary
| Product Component | OS Type | Versioning | Pattern Depth |
|---|---|---|---|
| JBossPortal | Windows, UNIX | File, Path | Instance-based |
Platforms Supported by the Pattern
The pattern supports both the Windows and UNIX platforms.
Identification
Software Instance Triggers
| Pattern | Trigger Node | Attribute | Condition | Argument |
|---|---|---|---|---|
| JBossPortal | DiscoveredProcess | cmd | matches | regex '\bjava(?:\.exe)?$' |
| args | matches | regex 'org\.jboss\.Main' |
Avoiding false positives
The trigger is the same trigger as Red Hat JBoss Application Server. To ensure the pattern only generated on a JBoss Portal instance the following additional checking as carried out before an SI is created.
Obtaining the base directory
The pattern parses the trigger process argument using one of the following regular expressions:
- (?i)(?:cp|classpath).*[\s":](.+?)/bin/run\.jar for UNIX
- (?i)(?:cp|classpath).*[\s";](\w\:\\.+?)\\bin\\run\.jar[\s";] for Windows
Checking for a file
The pattern checks for the existence of a file <base_directory>/server/default/deploy/jboss-portal.sar/portal-aop.xml. If it cannot find this file it assumes it is not looking at a JBoss Portal instance so exits without creating an SI
Software Instance Type Attributes Created
The pattern in this module will set the following attribute:
| Pattern Name | SI Type |
|---|---|
| JBossPortal | Red Hat JBoss Portal |
Versioning
Versioning is attempted using file and path versioning.
File versioning
The pattern has already obtained details of the base directory when checking for false positives
For file versioning, the pattern looks at the following file
- <base directory>/docs/portal/quickstartGuide/eclipse/toc.xml
The pattern then extracts the version information from the file using the following regular expression
- <toc label="JBoss Portal (\d+(?:\.\d+)*)
Path versioning
The pattern has already obtained details of the base directory when checking for false positives
If file versioning is unsuccessful the pattern attempts path versioning. It does this by parsing the base directory using the following regular expression:
- (?i)jboss-portal-(\d+(?:\.\d+)*)
Application Model Produced by Software Pattern
Product Architecture
Software Pattern Model
Pattern Trigger
The JBossPortal pattern triggers on the JBoss Application Server (java or java.exe with 'org.jboss.Main' in its arguments) process.
SI Depth
If a server is identified, the JBossPortal pattern creates an instance-based Software Instance, its key being based on server name, type (i.e. Red Hat JBoss Portal) and host key.
If no server is identified, the JBossPortal pattern creates a grouped instance-based Software Instance, its key being based on the base path, and the full version
Relationship Creation
If a server name has been identified, a relationship is created between the Portal SI and the Application Server SI that share this server name.
The Application Server SI is identified by using the following query:
- *search Host traverse Host:HostedSoftware:RunningSoftware:SoftwareInstance where type has substring 'RedHat JBoss Application Server' and server_name = '%server_name%' *
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 Red Hat JBoss Portal.
Testing
Testing was performed against a live installation of JBoss Portal on both Windows and Linux
Open Issues
There are no known open issues with this pattern.
| TOP |
|---|
Created by: Chris Blake 25 Sep 2008
Updated by: Chris Blake 10 Feb 2009
Reviewed by: Rebecca Shalfield 1 Oct 2008
Tideway Blog