BMC Software, Inc., Confidential and Proprietary Information
Product Components and Capabilities 1-17
Application Instance Naming Conventions
The application classes in this product use the naming conventions shown
in Table 1-2 for labeling icons to differentiate each application class
instance.
Table 1-2 Instance Naming Conventions (Part 1 of 2)
Application Instance Naming Convention Example
BEAWLS_EJB_
HOME
full JNDI name of bean, or display
name (for 7.0 and 8.1)
portal.PortalGroupHierarchyHome,
theory.smart.ebusiness.tax.
TaxCalculator,
TheCart
BEAWLS_EXEC
_QUEUE
unique name for the execute queue;
these are created at startup
MyAppQueue
BEAWLS_JCA the JCA application name which is
the name of its resource adapter
archive file (.rar)
BlackBoxNoTx
BEAWLS_JDBC unique user-defined name specified
when creating JDBC connection pool
commercePool, docPool
BEAWLS_
JMSSERVER
unique instance name of the JMS
server
exampleJMSServer
BEAWLS_JOLT unique user-defined name specified
when creating Jolt connection pool
ccjoltPool, demoJoltPool
BEAWLS_LOG user-defined name specified in Log
Name Alias field of the dialog box
that appears when setting up
monitoring for another log
by default, the application creates
instances for the JDBC, HTTP,
DOMAIN, and Server log files, as
defined in the WebLogic MBean
server configuration
JDBC, HTTP, SERVER, DOMAIN
BEAWLS_
MANAGED
name of the remote managed server
(remote to this PATROL Agent)
sales_server2
BEAWLS_ PROBE role of the server (admin or local
managed) being monitored
Admin_PROBE, LocalMgr_PROBE
BEAWLS_PROF_
CLASS
name of the Java class being profiled weblogic.managementAdmin