WebSphere Application Server is a key SOA building block. We can build a complete SOA application only using WAS. But If we look at the SOA reference Architecture, WAS can be used to develop and deploy Business Application Services. WAS(WebSphere Application Server comes in different packaging with different application server capabilities. Major packages are Base, Express, and Network Deployment.
11/23/2014
11/20/2014
Условие - проверка вхождения сотрудника в группу сотрудников (Condition - person is a member of person group)
:&PERSONID& in (select respparty from persongroupteam where persongroup in ('<GROUPNAME>')
11/08/2014
Setting up a Cluster/Integration Framework for Maximo 7.1 on WebSphere 6.1
Technote (FAQ)
Question
What are the steps required to set up a clustered Maximo application along with a stand-alone Maximo Integration Framework application for best performance?
Answer
When using the Maximo Integration Framework (IF) in a clustered environment the following should be considered. Note that this document does not cover all possible scenarios and many other configurations can be used that satisfy your particular requirements.
· For best performance with minimal impact to users, the IF can be configured to run on a single instance of Maximo while users log in and work with User Interface (UI) Instances of Maximo. In this case, you will need separate application servers (IF and UI instances).
· To share these resources, all resources will need to be defined at the cell level within the WebSphere console. The reason for this is although the IF instance will do all of the processing of inbound transactions, outbound transaction events will still occur from the UI instances upon saving Maximo records. This means that the UI instances need to have access to the JMS resources such as connection factories in order to be able to send outbound messages.
· The IF instance which will be responsible for processing inbound IF transactions from the continuous queue will need to have the Message Driven Bean (MDB) deployed along with the Maximo application to it's own application server and therefore will need a maximo.ear build that is slightly different than the UI instances which will not need the Message Driven Bean running within them.
· In this example configuration, there are two distinct buses. Specific resources exist only on their respective buses. To prevent problems with stranded messages on remote queue points, crontasks are configured to run on a server instance that is local to the bus it is a member of. In the case of outbound JMS transactions, the seqqout crontask instance runs on the UI server instance since the sqout queue is defined on the UI bus, however there is no performance impact observed with this crontask in a typical environment as it has very little processing to do on messages.
Below you will find instructions for setting up a cluster environment for UI instances of Maximo and a stand-alone application server for Maximo IF transaction processing.
· For best performance with minimal impact to users, the IF can be configured to run on a single instance of Maximo while users log in and work with User Interface (UI) Instances of Maximo. In this case, you will need separate application servers (IF and UI instances).
· To share these resources, all resources will need to be defined at the cell level within the WebSphere console. The reason for this is although the IF instance will do all of the processing of inbound transactions, outbound transaction events will still occur from the UI instances upon saving Maximo records. This means that the UI instances need to have access to the JMS resources such as connection factories in order to be able to send outbound messages.
· The IF instance which will be responsible for processing inbound IF transactions from the continuous queue will need to have the Message Driven Bean (MDB) deployed along with the Maximo application to it's own application server and therefore will need a maximo.ear build that is slightly different than the UI instances which will not need the Message Driven Bean running within them.
· In this example configuration, there are two distinct buses. Specific resources exist only on their respective buses. To prevent problems with stranded messages on remote queue points, crontasks are configured to run on a server instance that is local to the bus it is a member of. In the case of outbound JMS transactions, the seqqout crontask instance runs on the UI server instance since the sqout queue is defined on the UI bus, however there is no performance impact observed with this crontask in a typical environment as it has very little processing to do on messages.
Below you will find instructions for setting up a cluster environment for UI instances of Maximo and a stand-alone application server for Maximo IF transaction processing.
Subscribe to:
Posts (Atom)