BAS logical scope considerations

One of the benefits of using BAS to define and install user business application suites, is that users may then scope their object views to the resources pertinent to their installed application instances. For example, if a business application comprises of a particular set of files, transactions, and programs, the LOCTRAN, LOCFILE and PROGRAM views will be isolated to instances of only the matching objects on the regions where they are installed. The facility to allow this restricted object view is know as "logical scoping". The CorbaServer and DJAR objects may participate in logical scoping in exactly the same way as other traditional BAS definitions.
Note: Enterprise beans are not defined to CICS® as such. They become identified to CICS when their associated DJARs come into service after installation in a CICS region. Therefore, enterprise beans may "adopt" a logical scope through the association of their DJAR. However, the Enterprise JavaBean specification allows the enterprise beans for different applications, to be installed in a single DJAR. If you follow this practice, it will be impossible for the logical scope process to differentiate between the installed enterprise beans and the appropriate business application names. As such, if users want to exploit BAS logical scoping to augment their CICSPlex® views of enterprise bean objects, separate DJARs should be employed to contain enterprise beans discrete to the scoped business applications.