|
Problem |
WebSphere® Application Server Enterprise Edition
Extensions (EEX) is a collection of separately installed components, each
with separate methods for verifying a correct installation |
|
Solution |
WebSphere® Application Server Enterprise Edition is a
collection of components, each installed and tested separately:
- Extended Messaging
Support
Support for monitoring and managing incoming messages from a JMS queue.
- Business Rules
Beans
A trigger point framework that allows the application developer to
encapsulate frequently changed code into rules that can be called at
runtime. Support for developing and managing the rules is provided by the
a rule management tool.
- Work Area
A mechanism for passing arbitrary data elements without using the
parameter list of the calling method. It is very similar to a transaction
context.
- Internationalization
A mechanism for passing the locale and timezone information without using
the parameter list of the calling method. It is a specialization of the
Work Area.
- CORBA Services
CORBA Services consists of samples and documentation for tested
interoperability scenarios along with a software development toolkit for
developing C++ CORBA clients and servers.
- Business Process
Beans
This is a preview feature.
- ActiveX Client
Tools, samples and documentation for creating ActiveX clients that can be
clients to WebSphere Application Server Enterprise JavaBeans™ (EJB™)
server objects. The ActiveX tools create a wrapper that makes calls to the
Java EJB client either by way of the proxy directly or through the J2EE™
client container.
To see if EEX is installed from the AE Administrative Console GUI, select
Managed Server > Custom > Workarea Service >
Internationalization Service > Extended Messaging Support Service
> JMS_listener_name
Extended Messaging Support - requires JMS
support
Prerequisites:
- MQ Series® 5.2 is a prerequisite for the Extended
Messaging Service (JMS Listener).
- In Windows®, typically installed in the directory,
Program Files\MQSeries.
- MA88 (Java™ for MQ) typically installed in "Program
Files\IBM\MQ Series"
- You must have a "Java" subdirectory for MQ.
- This will cause a lot of confusion. Remember that MQ
supports many languages and the JMS is for Java and the primary interest
is in Java, so make sure you are pointing to the one that has the Java
subdirectory.
- If MQ Samples will not run, MQ support provides install
support.
- \MQSeries\Java\Samples\sample*
A big point of confusion:
- The JMS resources are independent of the Extended
Messaging Services. They are part of the base JMS support that should be
configured before you ever install the Extended Messaging support. It is
not mandatory but reduces confusion.
JMS Providers
-> IBM MQ Series
-> JMS Connection Factories
-> JMS Destinations
Skills transfer class has 2 tutorials covering JMS and MQ:
- One for AE and one for AEs
- The main difference is that in AEs there is no assurance
that the JNDI will be available because it is typically part of the
Application Server. The Application Server is very transient in the AEs
model. To deal with this, there is a way you can tell Extended Messaging
Service to use the Operating System File system for the JNDI repository.
This is described in the AEs lab.
JMS verification:
- Entry in the file, product.xml.
- Entry in each new application server (Managed Server, custom tab can
be enabled or disabled manually)
- Samples in
install_root/Enterprise/Samples/messaging
- Using command line interface with DumpJNDINamespace utility.
- Can be tested after MQ Installed and configured, then JMS
Configured
Notes:
- When configuring the Extended Messaging Support, you must
click Apply in order for changes to be saved. One of the common
mistakes is for the user to specify the configuration URL for the Extended
Messaging Service and then to not Apply. This will give a warning when the
Application Server starts but will not prevent it from starting
successfully. The Server will be running but the JMS listener will not be
listening.
- Not all of the EEX components are visible from the
Administrative Console, look at the product.xml
file.
- Components only show up in a Managed Server, when the
application is deployed after EEX has been installed.
Business Rules Beans (BRB)
- Has GUI started from the Start Menu.
- You might need to validate a data source in order to
verify BRB.
Business Rule Beans verification:
- Entry in the file, product.xml.
- Entries in:
-
install_root/Enterprise/BRBeans
-
install_root/Enterprise/samples/BRBeans
- install_root/lib/BRB*.jar (4
files)
WorkArea
WorkArea verification:
- Entry in the file, product.xml.
- install_root/Enterprise/samples/WorkArea
Internationalization
Note: Programming support only, no installation testing available.
Internationalization verification:
- Entry in the file, product.xml.
- install_root/Enterprise/samples/il8nctx
CORBA Services
Interoperability with EJBs.
Note: Programming support only.
CORBA Services Verification:
- Entry in the file, product.xml.
-
install_root/Enterprise/samples/sampcppsdk
Business Process Beans (BPB)
Installation:
- Installed from the root directory of the CD:
BPBeansSetup.exe
- Command line installation only.
- Adds entries to the Start Menu.
Notes:
- Preview available on Windows® only.
- Stand-alone product.
- BPB can be installed on the same system as WebSphere
Application Server without interference.
Business Process Beans verification:
- Creation of WebSphere\Enterprise folder.
- Entries in the Start Menu.
- Verify the graphical user interface will start.
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
WebSphere Application Server Enterprise |
EE Install |
|
|
|
|
|
|
|