Smart Assist identifiers and component identifiers
The Smart Assist Identifier and Component Identifiers uniquely identify a particular Smart Assist component within the Smart Assist framework.
The first step in developing a Smart Assist is defining these identifiers. The Smart Assist Identifier reflects the target application such as DB2®, Oracle or WebSphere®. Examples of Smart Assist IDs are "DB2_8.0" for DB2 and "Oracle_10G" for Oracle Application Server and RDBMS. Note that in these particular cases the Identifier also reflects the version of the application. To ensure version compatibility, it may be useful to develop separate Smart Assists for different versions of the target application. The Smart Assist Component Identifiers are used to subclassify a Smart Assist into the various subcomponents of an application, and into the sub-features of the Smart Assist. In the case of DB2 and Oracle, the database instances can be configured in different ways; therefore several Component Identifiers are needed, one for each way the database can be configured. Examples of DB2 Component Identifiers are shown in the table that follows:
| Component Identifier | DB2 Component Name (user visible) |
|---|---|
| DB2_8.0_NON_DPF_SINGLE | DB2 Single Instance |
| DB2_8.0_NON_DPF_MUTUAL | DB2 Mutual Takeover |
In the case of WebSphere, the Component Identifiers consists of several distinct functional components (a web server, a log server, etc.), and so each component has its own Component Identifier. Examples of WebSphere Component IDs are shown in the following table:
| Component Identifier | WebSphere Component Name (user visible) |
|---|---|
| WAS_6.0_IHS_SERVER | IHS HTTP Server |
| WAS_6.0_APP_SERVER | WebSphere Application Server (Standalone) |
| WAS_6.0_DEPLOYMENT_MANAGER | WebSphere Deployment Manager |
| WAS_6.0_TRANSACTION_LOG_ RECOVERY | WebSphere Cluster Transaction Log |