WAS - WebSphere Application Server

Carefully plan your application server nomenclature. Use a systematic approach to naming to simplify administering the environment.

The deployment manager is the centralized management communication vehicle. It is recommended that the deployment manager be installed on a separate machine than the application server nodes to prevent unmanaged work from occurring on the nodes.

The profile is a separate set of files that define the application server environment. A profile is a separate data partition that contains the files that define the run-time environment for an application server. A default profile is created during the installation of the base product. Create additional profiles using the Profile Creation wizard. [+ make a profile the default] Each profile defines a separate stand-alone application server that has its own administrative interface.

This wizard creates run-time environments that are referred to as profiles. Each profile contains either a deployment manager, a node that is administered by a deployment manager, or a stand-alone application server.

Regardless of the configuration, the WebSphere Application Server is organized based on the concept of cells, nodes, and servers.

WAS 6.0 System Management and Configuration Handbook, SG24-6451.pdf, page 47 of 1040.

Application servers, nodes, and cells

The application server is the primary runtime component in all configurations. It is where an application executes. All WAS configurations can have one or more application servers.
Application servers provide the runtime environment for application code. They provide containers and services that specialize in enabling the execution of specific Java application components. Each application server runs in its own Java Virtual Machine (JVM).

A node is a logical grouping of server processes managed by WebSphere and that share common configuration and operation control. A node is a grouping of managed or unmanaged servers. A node usually corresponds to a logical or physical computer system with a distinct IP host address. Nodes cannot span multiple computers. Node names usually are identical to the host name for the computer.

Nodes in the network deployment topology can be managed or unmanaged. A managed node has a node agent process that manages its configuration and servers. Unmanaged nodes do not have a node agent.

"AC" : A node corresponds to a physical computer system with a distinct IP host address. The node name is usually the same as the host name for the computer. The following table lists the nodes in this cell. You can add new nodes into the cell by clicking on "Add Node" and specifying a remote, running WebSphere Application Server instance

The node agent represents the node in the management cell and keeps the configuration up to date. Node agents are administrative agents that represent a node to your system and manage the servers on that node. Node agents monitor application servers on a host system and route administrative requests to servers.

A node group is a new concept introduced with WebSphere Application Server V6. A node group is a grouping of nodes within a cell that have similar capabilities. A node group is a collection of managed nodes.

If a node agent is managing a WAS, the (re)start parameters are specified here :

A cell is a grouping of nodes into a single administrative domain. A cell is a configuration concept, a way for administrators to logically associate nodes with one another.

Deployment Manager, dmgr

Deployment managers are administrative agents that provide a centralized management view for all nodes in a cell, as well as management of clusters and workload balancing of application servers across one or several nodes in some editions. A deployment manager hosts the administrative console. A deployment manager provides a single, central point of administrative control for all elements of the entire WebSphere Application Server distributed cell. Each cell contains one deployment manager.

Administrative service

The administrative service runs within each server JVM. In Base and Express, the administrative service runs in the application server. In Network Deployment, each of the following hosts an administrative service:

The administrative service provides the necessary functions to manipulate configuration data for the server and its components. The configuration is stored in a repository in the server's file system.

With this configuration, you can create multiple application servers to run unique sets of applications and then manage those applications from a central location. However, more importantly, you can cluster application servers to allow for workload management and failover capabilities. Applications that you install in the cluster are replicated across the application servers. When one server fails, another server in the cluster continues processing. Workload is distributed among Web containers and Enterprise JavaBeans containers in a cluster using a weighted round-robin scheme.

WebSphere Extended Deployment extends WebSphere Application Server Network Deployment Version 6.0.2, providing an enhanced quality of service in four primary areas:

WebSphere Extended Deployment introduces virtualization and automation. It delivers a high performance, easily manageable and dynamically scalable environment for distributed WebSphere applications.

Network Deployment provides an operating environment with advanced performance and availability capabilities in support of dynamic application environments.

IVT - writes
c:\Program Files\IBM\WebSphere\AppServer\profiles\Dmgr01\logs\dmgr\SystemOut.log

The user account that runs the Windows service must have the following user rights :

See it in "Administrative Tools" + "Local Security Policy" + "Local Policies" + "User Rights Assignment"

Change it (to "was1" user) in "Services" + "IBM ... Cell Manager" + boton derecho + "Properties" + "Log On".

IVT - writes
c:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\server1\SystemOut.log

To federate the Application Server, use either the addNode command or the administrative console of the deployment manager. If you use the administrative console, the Application Server must be running.

start server Application Server Server1
open Dmgr01 Administrative Console : http://localhost:9060/ibm/console
open System Administration
open Nodes + select "Add Node"
select "Managed" node
IP de la máquina (or 127.0.0.1) + JMX connector type := SOAP + JMX connector port := 8880 (SOAP port)
include Applications := "yes" ;
run Node Agent as Windows Service := "yes" ;

Adding node
ADMU0001I: Begin federation of node w2kwasNode01 with Deployment Manager at w2kwas:8879.
ADMU0009I: Successfully connected to Deployment Manager Server: w2kwas:8879
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: server1
ADMU2010I: Stopping all server processes for node w2kwasNode01
ADMU0024I: Deleting the old backup directory.
ADMU0015I: Backing up the original cell repository.
ADMU0012I: Creating Node Agent configuration for node: w2kwasNode01
ADMU0014I: Adding node w2kwasNode01 configuration to cell: w2kwasCell01
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0018I: Launching Node Agent process for node: w2kwasNode01
ADMU9990I:
ADMU0300I: Congratulations! Your node w2kwasNode01 has been successfully incorporated into the w2kwasCell01 cell.
ADMU9990I:
ADMU0306I: Be aware:
ADMU0302I: Any cell-level documents from the standalone w2kwasNode01Cell configuration have not been migrated to the new cell.
ADMU0307I: You might want to:
ADMU0303I: Update the configuration on the w2kwasCell01 Deployment Manager with values from the old cell-level documents.
ADMU9990I:
ADMU0003I: Node w2kwasNode01 has been successfully federated.

The new node will not be available in the console until you log in again

Logout from the WebSphere Administrative Console

The later (at Server1) has the snoop application available at http://ip:9080/snoop/

dmgr

Can be reached thru Dmgr Admin Console, System Administration, Deployment manager, Additional Properties, "Ports".

App Srv

Using "Administrative Console", go "Application servers", select a server, then "Ports".

/opt/IBM/WebSphere/AppServer/profiles/<deploy manager>/bin/serverStatus.sh -all

Per administrar el IHS des la consola administrativa de WAS, ha de estar actiu el procés admin, escoltant al port 8008. S'engega així :

Top

Using command line tools

url

All command line tools function relative to a particular profile. If you run a command from a app_server_root/bin directory, the command runs within the default profile. To specify a different profile, use one of the following methods:

Specify the -profileName option.
The profile that you specify with this option will be used instead of the default profile. For example:
1. Change to the app_server_root/bin directory.
2. Type the following command: startServer server1 -profileName AppServerProfile
In this example, the command starts the application server named server1 which exists in the configuration for the AppServerProfile profile.
Run the command from the bin directory of a specific profile.
For example, run the command from the bin directory of the MyProfile profile:
1. Change to the profile_root/bin directory.
2. Type the following command: startServer server1
In this example, the command will function inside the MyProfile profile.

	Server-related
wasprofile	wasprofile -lstProfiles : [Dmgr01, AppSrv01] wasprofile -delete -profileName AppSrv01
startServer	reads the configuration file for the specified application server and starts the server
stopServer
serverStatus	serverstatus -all
	Node-related
addNode	to a Cell
startNode
stopNode	stop nodeAgent
syncNode
removeNode
cleanupNode
	dmgr-related
startManager
stopManager
status	...\profiles\Dmgr01\bin > serverstatus dmgr
	other
backupConfig
restoreConfig
EARExpander
GenPluginCfg
versionInfo	displays the product version and Fix Packs installed.
genVersionReport
historyInfo
genHistoryReport

Node Agent does not seem to work :

make sure the node agent has been added to the NDM : open "System Admin -> Node Agent" list.
see if that node agent is running : serverstatus -all
start it using /AppServer/bin/StartNode.bat command

url

Start / stop commans

See \\T430\sebas\WAS\scripts\Start_Stop>

Display profiles

Interesting command :

C:\IBM\WebSphere\AppServer\bin> manageprofiles.bat -help ; deix un log detallat a c:\IBM\WebSphere\AppServer\logs\manageprofiles\ Function: Creates, lists, alters or deletes profiles Syntax: manageprofiles - - ... The available modes are: create augment delete unaugment unaugmentAll deleteAll listProfiles listAugments backupProfile restoreProfile getName getPath validateRegistry validateAndUpdateRegistry getDefaultName setDefaultName response help Note: Command-line arguments are case sensitive. Note: If argument accepts a parameter containing spaces, the parameter must be enclosed in "double quotes". Note: The default profile template is "default" and may be overridden by the -templatePath switch. Note: Mode specific arguments are described in the detailed help for each mode. To see the detailed help on each mode enter: - -help

En el nostre cas:

C:\IBM\WebSphere\AppServer\bin> manageprofiles -listProfiles [STSCDMgrProfile, STSCAppProfile, proxy-sunSTPPNProfile1, meeting-sSTMPNProfile1, st852-sunSTMSPNProfile1]

Surt el mateix que

c:\> dir C:\IBM\WebSphere\AppServer\profiles\ 02/29/2012 04:12 PM <DIR> proxy-sunSTPPNProfile1 02/28/2012 01:54 PM <DIR> STSCAppProfile 02/24/2012 01:55 PM <DIR> STSCDMgrProfile

Profile registry exists:

type C:\IBM\WebSphere\AppServer\properties\profileRegistry.xml <?xml version="1.0" encoding="UTF-8"?><profiles> <profile isAReservationTicket="false" isDefault="true" name="STSCDMgrProfile" path="C:\IBM\WebSphere\AppServer\profiles\STSCDMgrProfile" template="C:\IBM\WebSphere\AppServer\profileTemplates\management"/> <profile isAReservationTicket="false" isDefault="false" name="STSCAppProfile" path="C:\IBM\WebSphere\AppServer\profiles\STSCAppProfile" template="C:\IBM\WebSphere\AppServer\profileTemplates\default"/> <profile isAReservationTicket="false" isDefault="false" name="proxy-sunSTPPNProfile1" path="C:\IBM\WebSphere\AppServer\profiles\proxy-sunSTPPNProfile1" template="C:\IBM\WebSphere\AppServer\profileTemplates\default"/> <profile isAReservationTicket="false" isDefault="false" name="meeting-sSTMPNProfile1" path="C:\IBM\WebSphere\AppServer\profiles\meeting-sSTMPNProfile1" template="C:\IBM\WebSphere\AppServer\profileTemplates\default"/> <profile isAReservationTicket="false" isDefault="false" name="st852-sunSTMSPNProfile1" path="C:\IBM\WebSphere\AppServer\profiles\st852-sunSTMSPNProfile1" template="C:\IBM\WebSphere\AppServer\profileTemplates\default"/> </profiles>

Display SERVERs for every profile:

c:\IBM\WebSphere\AppServer\profiles\STSCAppProfile\bin> serverStatus.bat -all ADMU0116I: Tool information is being logged in file C:\IBM\WebSphere\AppServer\profiles\STSCAppProfile\logs\serverStatus.log ADMU0128I: Starting tool with the STSCAppProfile profile ADMU0503I: Retrieving server status for all servers ADMU0505I: Servers found in configuration: ADMU0506I: Server name: nodeagent ADMU0506I: Server name: STConsoleServer ADMU0508I: The Node Agent "nodeagent" is STARTED ADMU0508I: The Application Server "STConsoleServer" is STARTED

Top

WAS administration

Engrunes d'administració de WAS

Error log language

-Duser.language=en

abrir WAS script console :
c:\> wsadmin -lang jython
ver que hay en un server :
AdminTask.showJVMProperties('[-serverName DCRules1 -nodeName WODMDCenterNode01]');
configurar language :
AdminTask.setGenericJVMArguments('[-serverName DCRules1 -nodeName WODMDCenterNode01 -genericJvmArguments "-Duser.language=en -Dcom.ibm.cacheLocalhost=true"]');

De nuevo, gracias, Bruno !

VERBOSEGC

How to disable the garbage collector verbose output ? Es un parametre a la JVM ? Quin fitxer és ?

ISC = open Integrated Solutions Console
[+] Servers
[+] Server Types
click "WebSphere application servers"
on the right-panel, click on specific server name
on right-hand panel, expand [+] Java and Process Management and click on "Process Definition"
on next screen, click on "Java Virtual Machine", under "Additional Properties"
you can see the "Verbose garbage collection" checkbox, as well as "Generic JVM arguments"

Per assignar mes memoria a Eclipse (from-0-2-hero), posem:

-Xmx1024m

jython & console commands

obrir la consola de WAS
expandir System Administration
escollim Console Preferences
activem "Enable command assistance notifications"
activem "Log command assistance commands"
cuan modifiquem el WAS i fem "Save", veurem els resultats en una finestra a la dreta, sota "Help", en jython

article

A la dreta, dins el quadre "Help", a sota de Page help", hi ha una entrada anomenada "Command Assitance" on hi surt un link "View administrative scripting command for last action" !

Change user's password

obrim la consola de WAS
expandim "Users and groups"
escollim "Manage Users"

(sag 20121108) "simone2012" -> no jython

wsadmin

You can start the scripting client when no server is running, if you want to use only local operations. To run in local mode, use the wsadmin.bat -conntype NONE option to start the scripting client. You receive a message that you are running in the local mode

If you are deploying an application in the local mode, you must modify the wsadmin.bat or wsadmin.sh command file in the install_root/bin directory. Add the following lines of code to the wsadmin file, right after the call to the setupCmdLine.bat file:

SET PATH=%WAS_PATH%;%PATH%

Top

Administrative security

Disabling administrative security

If you can't log onto Sametime Console, disable security.

There are 2 methods for disabling security

by way of wsadmin command

stop the servers, as we will work in local mode
<WAS_HOME>/bin/> wsadmin -conntype NONE { usually at c:\IBM\WebSphere\AppServer\bin }
wsadmin> securityoff
wsadmin> exit
restart the servers
enable the security from administrative console
restart the servers

C:\IBM\WebSphere\AppServer\bin> wsadmin -conntype NONE WASX7357I: By request, this scripting client is not connected to any server process. Certain configuration and application operations will be available in local mode. WASX7029I: For help, enter: "$Help help" wsadmin> securityoff LOCAL OS security is off now but you need to restart server1 to make it affected. wsadmin> exit

by editing security.xml file

create a copy for security.xml file, in case you need to roll back.
disable the security from the security.xml file
Change the very first occurrence of enabled="true" to enabled="false"
restart the servers
enable the security from administrative console
restart the servers

url

Enabling administrative security from admin console

Log into ISC, without a password now.
expand "Security" on the left pane
click "Global Security"
check the box "Enable administrative security"
uncheck "Enable application security"
uncheck "use Java 2 security"
Apply, Save and Logout
restart servers

En quin moment es posa usr/pwd ?

Problem : wasdmin usr/pwd stopped working

https://st852-suno.bar.es.hal.com:8701/ibm/console/ :

[10/31/12 15:38:11:265 CET] 00000037 WebCollaborat A SECJ0129E: Authorization failed for user wasadmin:default WIMFileBasedRealm while invoking GET on admin_host:/ibm/console/, Authorization failed, Not granted any of the required roles: administrator operator configurator monitor nobody [10/31/12 15:38:11:359 CET] 00000037 webcontainer E com.ibm.ws.webcontainer.WebContainer handleRequest SRVE0255E: A WebGroup/Virtual Host to handle /favicon.ico has not been defined.

Changing wasadmin password

If your system is configured to use the internal user registry and you have a stand-alone installation, do not use the web console to change the WAS administrator password.

stop WAS
change the password by using the DirectoryAdmin command:
Linux: /opt/IBM/InformationServer/ASBServer/bin/DirectoryAdmin.sh -user -userid wasadmin -password password Windows: C:\IBM\InformationServer\ASBServer\bin\DirectoryAdmin.bat -user -userid wasadmin -password password
run the AppServerAdmin command with the -was option to update the credentials across your configuration :
Linux: /opt/IBM/InformationServer/ASBServer/bin/AppServerAdmin.sh -was -user wasadmin1 -password mypassword Windows : C:\IBM\InformationServer\ASBServer\bin\AppServerAdmin.bat -was -user wasadmin1 -password mypassword

url

After server1 is running, the Snoop sample application is available at http://localhost:9080/snoop/

In order to have it available, Server1 must be running, as snoop servlet is part of Default Applications module.

WAS 6.0 System Management and Configuration Handbook, SG24-6451.pdf, ch 5.8.11, page 254, 278 of 1040.

The URL for a servlet or JSP is the path used to access it from a browser. The URL is partly defined in the deployment descriptor provided in the EAR file and partly defined in the deployment descriptor for the Web module containing the servlet or JSP.

When security is disabled, WebSphere Application Server performance is increased between 10-20%.

A server cluster consists of a group of application servers. If one of the member servers fails, requests will be routed to other members of the cluster.

A cluster is a logical collection of application server processes that provides workload balancing and high availability. Application servers in a cluster are members of that cluster and must all have identical application components on them. Other than the applications on them, cluster members do not have to share any other configuration data.

Now, the snoop application is also available on Server2 at URL http://localhost:9081/snoop/

WS Application Server zone - tons of links.
Product Overview

WS Application Server library [***] & related libraries. [ \\WAS\Llibres_WAS\6.0\Documentation ]

Migrating, coexisting, and interoperating	wasv600nd_mig.pdf
Installing your application serving environment	wasv600nd_gs.pdf
Administering applications and their environment	wasv600nd_app.pdf
Setting up the application serving environment	wasv600nd_env.pdf
Using the administrative clients	wasv600nd_admin.pdf
Securing applications and their environment	wasv600nd_security.pdf
Developing and deploying applications	wasv600nd_devdep.pdf
Troubleshooting and support	wasv600nd_trb.pdf
Tuning guide	wasv602nd_tune.pdf

And more

WAS version 6.0 Information Center [*** publib ***] Top !

welcome_base.htm : Getting started, How do I ? ... perform key tasks,

Tutorials : (1) Education Assistant :

(2) developerWorks.

WS Application Server support - forums, fixes, etc

The base URL for WebSphere Application Server fixes.
V 6. Go from 6.0.0 to 6.0.2. Go from 6.0.2 to 6.0.2.7.

Instalació

Best practices tutorials - curs audio-visual.

Install v 5.1 - docu [boulder]

v 6, 6.1, v 7.

WS Application Server performance info - guides, redbooks, articles, etc.

WS Application Server RedBooks

As SG24-6451 = WAS 6.0 System Management and Configuration HandBook Top !
[\\WAS\Llibres_WAS\6.0\]

Part 1. The basics Chapter 1. WebSphere Application Server V6 for distributed platforms Chapter 2. WebSphere Application Server V6 architecture Chapter 3. System management: A technical overview Chapter 4. Getting started with profiles Chapter 5. Administration basics Chapter 6. Administration with scripting Chapter 7. Configuring WebSphere resources Chapter 8. Managing Web servers Chapter 9. Problem determination Part 2. Messaging with WebSphere Chapter 10. Asynchronous messaging Chapter 11. Default messaging provider Part 3. Working with applications Chapter 12. Session management Chapter 13. WebSphere naming implementation Chapter 14. Understanding class loaders Chapter 15. Packaging applications Chapter 16. Deploying applications Chapter 17. WebSphere Rapid Deployment

As SG24-6446 = WAS 6.0 Planning and Design
[\\WAS\RedBooks\v 6]

As SG24-6963 = WAS 6.0_Product Family Overview And Achitecture
[\\WAS\RedBooks\v 6]

Best ! : redp3918 = WAS 6.0 Technical Overview
[\\WAS\RedBooks\v 6]

IBM Systems Journal, vol 43, No 2, 2004 : WebSphere Application Server.
See \\WS\RevistesWS\SystemsJournal\Vol43No2

From {developerworks}

New to Application Server Information Center Documentation library WebSphere Redbooks domain Techdocs Best practices Access Safari's e-reference library Training & certification Technical enablement Information roadmaps Process choreographer articles WebSphere and Adobe WebSphere Technical Journal [***]

WS Extended Deployment library or On-Line [publib]

Top

J2EE

J2EE contains the Java Message Service (JMS) specification, which defines an API that applications can utilize to access a messaging provider (a product implementation that provides the infrastructure that supports messaging, such as IBM WebSphere MQ or the Messaging engine component used here). JMS is the API specification only and does not describe the actual messaging product or provider. This is similar to accessing relational databases through JDBC, where JDBC defines the access mechanism but does not define the actual relational database product. All the interaction with the J2EE server so far was over HTTP. How do you access J2EE over messaging?

Client side: A program creates a message and sends it to a JMS queue, in this case a local queue—the message stays on the source system and is not forwarded to a remote system, and then terminates. The program does not know when (or if) the message is actually read, only that the message is persisted in the queue. In this scenario the program is a standalone Java program, but you could put the same basic code inside J2EE server side artifacts (such as servlets or EJBs) if you wanted to send a message from one J2EE server to another, or even to another component in the same J2EE server.
J2EE server side: An EJB container is configured to listen to a queue through a definition called an activation specification. An EJB artifact called a message-driven bean (MDB) is created, with a method called onMessage that contains the user defined business logic, and deployed to this EJB container, referencing the same activation specification. When the EJB container starts, it opens the activation specification and issues a receive against the queue. When a message is placed on the queue, the activation specification receives the message and calls the associated MDB onMessage method, which runs the user defined business logic.

Note that MDBs have little in common with entity EJBs and session EJBs except for executing in the same J2EE container. The MDB is invoked by the overall J2EE infrastructure and does not have any external home or local interfaces.

Experience J2EE using WAS 6.1, SG24-7297, page 357 [376/472]

Top

SAG Application

VM (Rosa) : Lola(8.137.164.13)+F:\r_dias_win2k\

Objectiu : tenir un MDB que faci "eco" a un RFH2 amb "ADP_ECO_WAS" o cridi un EJB que faci eco a un "EJB_ECO" dins un RFH2.

General objectives are :

Experience with WAS v4.0, v5.0 or v5.1
Basic understanding of the Java programming language
Intermediate understanding of J2EE fundamentals
Know how to create Enterprise JavaBeans, Servlets, and JSPs
Understanding of Web services fundamentals
Understand the architecture and systems management of WAS

Gain an understanding of J2EE fundamentals by

browsing http://java.sun.com/j2ee,

The name of the Java platform for the enterprise has been simplified. Formerly, the platform was known as Java 2 Platform, Enterprise Edition (J2EE), and specific versions had "dot numbers" such as J2EE 1.4. The "2" is dropped from the name, as well as the dot number. So the latest version of the Java platform for the enterprise is Java Platform, Enterprise Edition 5 (Java EE 5).
reading "Designing Enterprise Applications with the Java 2 Platform, Enterprise Edition" ISBN 0201702770,
reading "Enterprise Java Programming with IBM WebSphere, Second Edition" ISBN 032118579X.
"J2EE simplified" - page 7 [25/472], Experience J2EE! Using WAS V6.1, SG24-7297-01

ADP_ECO_WAS : MDBsvrBean

StrEntDst = (String) properties.get("COD_ENT_DST"); StrCodSvr = (String) properties.get("COD_SERVEI"); if (StrCodSvr.equals("ADP_ECO_WAS")) { rspmq.exec_snd ( StrEntDst, StrEntOrg, StrTypMsg, "C", DatUsr, "Eco mdb j2ee " + DtaMsg ) ; } else { if ( StrTypSrv.equals("EJB") ) { EJBHome EJBIntf =(javax.ejb.EJBHome) javax.rmi.PortableRemoteObject.narrow(ctx.lookup(PathUrlSrv), EJBHome.class); EJBMetaData md = EJBIntf.getEJBMetaData(); Class homeClass = md.getHomeInterfaceClass(); Class remoteClass = md.getRemoteInterfaceClass(); EJBObject EJBIntfRemote = (EJBObject) invoke(homeClass,EJBIntf,"create"); String DtaRsp = (String) invokeProc ( remoteClass, EJBIntfRemote, "MessageBrokerProcess", DtaMsg ) ; } else { if ( StrTypSrv.equals("WS") ) { String StrRsp = callWebService ( PathUrlSrv, DtaMsg, null ) ;

EJB_ECO : EcoBrokerEJBBean

Oracle :

"EJB_ECO","ejb/es.bcn.idj.test.ejb.broker.EcoBrokerEJBHome","EJB" "WS_ECO", "http://rweb201/APPS/idjtest/services/DummyMessageBroker?wsdl///operation=eco","WS"

WAS admin console

The server is managed like this:

call C:\IBM\WebSphere\AppServer\profiles\DevAppSrv01\bin\serverStatus.bat server1 C:\IBM\WebSphere\AppServer\profiles\DevAppSrv01\logs\server1\serverStatus.log C:\IBM\WebSphere\AppServer\profiles\DevAppSrv01\bin>startServer.bat server1 C:\IBM\WebSphere\AppServer\profiles\DevAppSrv01\logs\server1\startServer.log https://99.137.164.57:9043/ibm/console/ (u/p : admin/admin)

Install

copiar idjBroker_idjrutinesug.jar en opt/IBM/WebSphere/AppServer/imi-shared/int
editar el fichero XConexioJMS.xml que se halla en opt/IBM/WebSphere/AppServer/imi-shared/conf
Añadir la línea
<attr>targetClient</attr>
editar el fichero XConexioJMSDescriptor.xml que se halla en opt/IBM/WebSphere/AppServer/imi-shared/conf
Añadir el servicio BRK01
configurar WAS :
1. crear una biblioteca compartida para contener el nuevo adaptador de WMQ
2. crear y configurar una fábrica de conexiones.
3. crear y configurar una cola de destino de MQ.
4. crear y configurar el listener para el MDB.
5. configurar appserver.bootstrap.port
6. realizar el despliegue del MDB.
Resum de fitxers d'entrada :
- [a] idjbroker_idjrutinesug.jar {T60:\C:\entorno_desa\proyectos\was_ext_lib\imi}
- [b] idjrutinesugCommon.jar {T60:\C:\entorno_desa\proyectos\was_ext_lib\imi}
- [c] MdbBroker.ear {T60:\C:\entorno_desa\wtk60}
- [d] idjBroker.ear {T60:\C:\entorno_desa\was60\profiles\default\config\cells\ES212520Node01Cell\applications\idjbroker.ear\}
Compte ! [c] i [d] ambdos contenen nomes que idjBrokerEJB.jar !
Veamos los detalles :
- [1] crear y configurar biblioteca compartida
  - > Entorno > Bibliotecas compartidas
  - Ámbito : Célula + Nodo.
  - Nueva (bibioteca)
  - Configurar :
    1. Nombre: WMB_IdjRutinesUg
    2. Descripción: "Libreria interfaz MQ - Broker"
    3. Classpath:
      ${LLIBRERIES_INTERNES}/idjbroker_idjrutinesug.jar [a] ${LLIBRERIES_INTERNES}/idjrutinesugCommon.jar [b]
- [2] crear y configurar una fábrica de conexiones.
  - > Recursos > Proveedores de JMS > WebSphere MQ
  - Ámbito : Célula + Nodo.
  - seleccionar Fábricas de conexiones de MQ, y escoger "Nuevo"
  - Configurar :
    1. nombre: facConBrokerMdb
    2. nombre JNDI : jms/facConBrokerMdb
    3. gestor de colas : queue manager name
    4. sistema principal : hostname, IP o nombre DNS
    5. puerto : 1414
    6. canal : nombre de canal tipo SVRCONN
    7. tipo de transporte : Cliente
- [3] configurar una cola de destino de MQ.
  - > Recursos > Proveedores de JMS > WebSphere MQ
  - Ámbito : Célula + Nodo + Servidor.
  - seleccionar Destinos de cola de WebSphere MQ y escoger "Nuevo"
  - Configurar :
    1. nombre: qRecBrokerMdb
    2. nombre JNDI : jms/qRecBrokerMdb
    3. nombre de cola básico : queue name
    4. gestor de colas : queue manager name
    5. cliente destino : JMS
    6. sistema principal : hostname, IP o nombre DNS
    7. puerto : 1414
    8. canal : nombre de canal tipo SVRCONN
    9. ID de usuario : para acceso MQ
    10. contraseña : para acceso MQ
- [4] crear y configurar el listener para el MDB.
  - > Servidores > Servidores de Aplicaciones
  - En la lista de servidores definidos, seleccionar el servidor donde se desea crear el Listener {dwasca}
  - > Comunicaciones > Mensajeria > Servicio de receptor de mensajes
  - selecciones Puertos Receptores y luego "Nuevo".
  - Configurar :
    1. nombre: ListenerBrokerMdb
    2. nombre JNDI de la fabrica de conexiones : jms/facConBrokerMdb
    3. nombre JNDI del destino : jms/qRecBrokerMdb
- [5] configurar appserver.bootstrap.port
  - > Servidores > Servidores de Aplicaciones
  - En la lista de servidores definidos, seleccionar el servidor donde se desea crear el Listener {dwasca}
  - > Comunicaciones > Puertos
    Anotar el valor asignado a BOOTSTRAP_ADDRESS
  - seleccionar > Infraestructura del servidor > Definicion de proceso
    Expandir Máquina Virtual Java
    Seleccionar Propiedades adicionales y luego Propiedades personalizadas
    Crean un valor "Nuevo", de nombre appserver.bootstrap.port y de valor el que hayamos apuntado anteriormente de BOOTSTRAP_ADDRESS
- [6] desplegar el MDB.
  1. copiar el fichero MdbBroker.ear [c] en el directorio temporal
  2. > Aplicaciones > Aplicaciones de empresa > Instalar
  3. especificar la ubicación del fichero idjBroker.ear [d]
  4. pulsar "Siguiente"
  5. verificar que se ha elegido "no sobreescribir enlaces existentes"
  6. pulsar "Siguiente"
  7. revisar los "Avisos de seguridad de la aplicación"
  8. pulsar "Siguiente"
  9. en el "Paso 1: seleccionar las opciones de instalación" poner idjBroker en el campo "Nombre de aplicación"
  10. pulsar "Siguiente"
  11. en el "Paso 2: correlacionar módulos con servidores" se debe seleccionar el servidor donde se debe desplegar el MDB {IMIapps}
  12. pulsar "Aplicar" y "Siguiente"
  13. en el "Paso 3: facilitar enlaces receptores para los Beans controlados por mensajes", verificar que el enlace al puerto receptor sea correcto.
  14. pulsar "Siguiente"
  15. en el "Paso 4: Resumen", pulsar "Finalizar".
  16. seleccionamos "Guardar en configuración maestra"
  17. seleccionamos "Sincronizar cambios con nodos" y "Guardar".
  18. Referenciar la libreria que contiene el adaptador :
    - > Aplicaciones > Aplicaciones de empresa > click en el nombre idjBroker
    - en la ventana de propiedades, escogemos Bibliotecas
    - escogemos "Nueva" y configuramos WMB_IdjRutinesUg de la lista desplegable.
ADP_ECO_WAS se halla en el fichero MdbsvrBean.java que se halla en J2EE\mdb\idjbrokerEJB\ejbModule\es\bcn\idj\broker\ejb\
al código de servicio EJB_ECO se le asocia -mediante Oracle- el EJB de PATH ejb/es.bcn.idj.test.ejb.broker.EcoBrokerEJBHome

Curs Admin Portal Dec'2009

Portal wiki -> (best doc) Master Table of Contents for wiki - Building a website using WCM 6.1.

JCP.

Creix sens limit : C:\IBM\WebSphere\wp_profile\PortalServer\deployed

Portal (multiplatform) Information Center

WS Portal for Multiplatforms 5.1.x docu

Notes.net = developerWorks site

Portal base url

Portal update installer

Unpack "7.822.085 PortalUpdateInstaller.zip" into {wp_root}\update.
Interim fixes can be downloaded to the {wp_root}\fixes directory.
Fix packs can be downloaded to the {wp_root}\fixpacks directory.

Comandos interesantes

SetupCmdLine.bat	E:\WebSphere\AppServer\bin	estableix el entorn de la JVM.
versionInfo.bat	E:\WebSphere\AppServer\bin	mostra la versió del WAS.
WPVersionInfo.bat	E:\WebSphere\PortalServer\bin	mostra la versió del Portal, etc etc
WPHistoryInfo.bat	E:\WebSphere\PortalServer\bin	mostra el historial de parches del Portal
./WPVersionInfo.sh	SuSE 9 + /opt/WebSphere/PortalServer/bin/	mostra la versió del Portal, Web Content Management, etc en Linux
type VersionInfo.log	C:\IBM\WebSphere\wp_profile\PortalServer\log\	mostra la versió del Portal que s'ha engegat

Run stopNode for all nodes

Place fixes in /update/fixes/ and run updateWizard from /update/ directory

Display applied fixes :

updateSilent -fix -installDir "d:\WebSphere\AppServer" -fixDir "d:\WebSphere\AppServer\update\fixes"

Mind {wp_home}/version/history/event.history

Must Gather info : url or url

wsadmin command prompt :

wsadmin.bat - get a prompt
get a handle to the problem application server :
wsadmin> set jvm [$AdminControl] completeObjectName type=JVM,process=server1
generate a thread dump : { WebSphere\AppServer\javacore.date.time.id.txt files}
wsadmin> $AdminControl invoke $jvm dumpThreads

RedBook WAS for developers v7

C:\IBM\WebSphere\AppServer\bin> wsadmin.bat

Thread Analyzer tool - url
[T400:\Java\ThreadAnalyzer]

How to enable verboseGC - url

Logs CM (content manager) : d:\WebSphere\PortalServer\wcm\connect\log

Export / import users

c:\Archivos de programa\WebSphere\PortalServer\doc\xml-samples\ExportAllUsers.xml

* Export users from source server: xmlaccess.bat -in ExportAllUsers.xml -user wpsadmin -password wpsadmin -url http://source_portal_server:port/wps/config -out Export_Users_Results.xml * Import into target server: xmlaccess.bat -in Export_Users_Results.xml -user wpsadmin -password wpsadmin -url http://target_portal_server:port/wps/config -out Import_Users_Results.xml

Export / Import more than 200 users

Try increasing the value in {wp_home}/wmm/wmm.xml: maximumSearchResults="200"

Problem: XML import might fail with out-of-memory error An XML import of portal resources might fail with an OutOfMemoryError. Cause: This error results from a limited heap size. Solution: Proceed by the following steps: 1. Start server1 and log in; url = http://localhost:9090/admin/ 2. Navigate to Servers > Application Servers > WebSphere_Portal > Process Definition > Java Virtual Machine 3. Determine the configured maximum heap size; for example, this might be 512 MB. 4. Increase the maximum heap size, for example to 1024 MB. 5. Restart your portal. 6. Run the XML import script again. The OutOfMemoryError should disappear.

Portal, v 5.1.x url "out-of-memory error"

Creating a new portal : (1) and (2)

Installing an empty portal - url

In some situations it is possible that you might want to install an empty portal, where WebSphere Portal is installed normally but no portlets are installed or deployed and no pages are created. This can be useful if you want to transfer an entire portal configuration from one portal to another. For example, you might want to transfer a portal from your test environment to a production environment.

To install an empty portal with the WebSphere Portal installation program, enter the following command from the root directory of the setup CD :

* UNIX: ./install.sh -W installPortletsSequence.active="false" * Windows: install.bat -W installPortletsSequence.active="false"

Before continuing, be sure to have all of your necessary files in place. That is, if you are installing a theme, place the folder containing the theme on the PortalServer in the correct location. The same goes for skins, portlet WARs, etc.

Theme folders go into:
C:\WebSphere\AppServer\installedApps\<nodename>\wps.ear\wps.war\themes\html\

Skin folders go into:
C:\WebSphere\AppServer\installedApps\<nodename>\wps.ear\wps.war\skins\html\

By default, portlet WAR files need to be placed in:
C:\WebSphere\PortalServer\installableApps\

Com "buidar" un portal ? XML para desinstalar todos los portlets.

Portlets that can be removed.

Portal virtual

Move the Portal configuration from a test server to production server

(3 times the same)

using the XML configuration interface or url [***]
Moving users and groups : url
See local text
using xmlaccess (SkyWayRadio copy)
portal troubleshooting [T42:\MQ\Portal\Redbooks\wp_sec_pdf.pdf]
XML configuration interface : reference

* Export configuration from source server: xmlaccess.bat -in ExportRelease.xml -user wpsadmin -password wpsadmin -url http://soure_portal_server.com:port/wps/config -out Source_Server_Cfg.xml * Import into target server: xmlaccess.bat -in Source_Server_Cfg.xml -user wpsadmin -password wpsadmin -url http://destination_portal_server.com:port/wps/config -out Import_Cfg_Results.xml

Nice (and complete) articles : 1, 2

Import errors

XmlAccess import ends with :

EJPDB0001E - DataBackendException
SQL0803N - DuplicateKeyException

due to delayed cleanup

Read fix

To solve the immediate problem, use XMLAccess to import the file <wps_home>/doc/xml-samples/Task.xml. This should start the cleanup task immediately and it will run only once. Then try the XMLAccess import again. You can edit Task.xml and import it again to reconfigure the delayed cleanup process. By default, the delete will run on Saturday evening. You may consider disabling delayed cleanup so that Portal pages are removed immediately but be aware that this can have a performance penalty.

Read about delayed cleanup

All samples description

-xmx1024m Java flag

VMware image (WP5101.zip + 01 + 02 = 3,6 GB)
Otra url (WPS: Portal Standalone = 11 GB)

Fixes

Interim FTP
url

Portal 5.1 cumulative fix 2 - upgrade document

Document transfer

create "{wp_root}\update\fixes\" directory.
put DTT.jar/PK18903.jar into this directory
shutdown Portal
install Portal Update Installer : url - unzip into "{wp_root}\update\" directory.
install fix using Portal Update Installer :
call updatePortal -fix -installdir "c:\IBM\PortalServer" -fixDir "{wp_root}\update\fixes" -install -fixes PK18903
restart Portal - "startserver Server1"
install {wp_root}\jcr\installableApps\icmjcr.ear to the Portal Server using WAS admin console
update 174.923 icmdtt.jar in {wp_root}\jcr\lib directory ! [fix 20-04-2006]
restart Portal
edit {wp_root}\jcr\admin\export.properties to include
jcr.export.maxFileLength=20 jcr.exportToFile=false jcr.export.path=C:/Exportar_Documentos/ROOTWORKSPACE
run "ant -f export.xml" :
java -jar C:\IBM\AppServer\lib\ant.jar -f C:/IBM/PortalServer/jcr/admin/export.xml
This creates a directory tree at "C:\Exportar_Documentos\rootworkspace\".
on the destination machine, edit {wps_home}\jcr\admin\import.properties
run "ant -f import.xml" :
java -jar C:\IBM\AppServer\lib\ant.jar -f C:/IBM/PortalServer/jcr/admin/import.xml

updatePortal syntax :

For EFix Processing:

updatePortal <propertiesFile> ( -installDir <product install root> [ -fix ] [ -fixDir <ifix repository root> ] [ -install | -uninstall | -uninstallAll ] [ -fixes <space delimited list of ifixes> ] [ -fixJars <space delimited list of ifix jars> ] [ -fixDetails ] [ -wpcpOnly ( -wpcpInstallDir <Content Publisher install root> ) | -skipWPCP ] [ -configProperties propertiesFile ] [ -prereqOverride ] ) | ( -help | -? | /help | /? | -usage )

For FixPack Processing:

updatePortal <propertiesFile> ( -installDir <product install root> [ -fixpack ] [ ( -install | -uninstall -fixpackDir <fixpack repository root> ] -fixpackID <FixPack ID> ] [ -wpcpOnly ( -wpcpInstallDir <Content Publisher install root> ) | -skipWPCP ] [ -includeOptional <space delimited list of components> ] [ -configProperties propertiesFile ] [ -fixpackDetails ] ) | ( -help | -? | /help | /? | -usage )

Enable PDM tracing

Stop the Portal Server
Backup and clear out the log files in {wp_root}\log
Go to the file {wp_root}\shared\app\config\log.properties and append the following line to it:
traceString=com.ibm.wps.pdm.*=all=enabled:com.ibm.dm.*=all=enabled: com.ibm.icm.*=all=enabled:com.ibm.wps.services.puma.*=all=enabled: com.ibm.wps.puma.*=all=enabled
Start the Portal Server
When the Portal comes back up, reproduce the problem and please provide us with the time on the Portal Server machine when the error occurs.
After reproducing the problem, zip up all the files from the {wp_root}\log directory.

Another way

Enable tracing in the PortalServer\shared\app\config\log.properties file: com.ibm.icm.*=all=enabled: com.ibm.wps.services.puma.*=all=enabled: com.ibm.wps.puma.*=all=enabled

Few configuration files

{wp_root}\config\wpconfig.properties

{wp_root}\wmm\wmm.xml

Upgrade Portal de 5.1.0.1 a 5.1.0.2 (to use nested groups)

url

poner WAS a 5.1.1.8 - url
poner BI a 5.1.1.3 url
poner PS a 5.1.0.2
para acabar, ejecutar WPSconfig.bat, que actualiza las aplicaciones.

(1) WAS 5.1.1.8 WAS511_CF8_win.zip 83.261.514 (2) BI 5.1.1.3 WBISF511_CF3_win.zip 210.539.626 (3) WPS 5.1.0.2 + Fix_Pack_22155 WP_PTF_5102.zip 450.635.656

Derby

Portal uses a "derby" database that you better backup once in a while. Read here.

Default ubication : c:\IBM\WebSphere\wp_profile\PortalServer\derby\wpsdb

URLs

URL portal - WebSphere_Portal	http://localhost:9081/wps/portal
URL consola administrativa - server1	http://localhost:9090/admin

Top

Portal hostname change

Perform the following steps to localize a new virtual machine instance:

stop the WebSphere_Portal server running on the virtual machine.
/opt/IBM/WebSphere/wp_profile/bin/stopServer.sh WebSphere_Portal –user wpadmin –password claudepas
verify that the server1 server is running on the virtual machine. If it is not running, start the server.
/opt/IBM/WebSphere/wp_profile/bin/startServer.sh server1
update the host name for the virtual machine instance per the instructions of the operating system.
$
to update the WebSphere Portal host name in the WAS configuration, run the command
wsadmin.sh -c "\$AdminTask changeHostName {-nodeName node_name -hostName new_host_name}"
from the wp_profile_root\bin directory. node_name is the node name of the current configuration and new_host_name is the TCP/IP host name of the new virtual machine instance.
optional: Perform the following steps to update the node name in the WAS configuration:
1. run the command
  wsadmin.sh -c "\$AdminTask renameNode {-nodeName old_node_name -newNodeName new_node_name}"
  to update the node name in the WAS configuration. old_node_name is the original node name of the current configuration and new_node_name is the new node name you will use for this instance.
  Remember: This step is necessary to create a unique node name if you will be federating and clustering this node.
2. edit the ./setupCmdLine.sh file, located in the wp_profile_root\bin directory and modify the SET WAS_NODE=node_name entry to specify the updated node name.
3. from the wp_profile_root/ConfigEngine directory, run the command
  ./ConfigEngine.sh rename-node-in-cell-registry -DWasPassword=password -DpreviousNodeName=oldNodeName
  where oldNodeName is the prior value of the node name.
from the wp_profile_root/ConfigEngine directory, run the command
./ConfigEngine.sh localize-clone -DWasPassword=password
to update WebSphere Portal with the information from the WAS configuration.
run the command
./ConfigEngine.sh action-clean-scheduled-tasks -DWasPassword=password
to clear any scheduled tasks. Existing scheduled tasks might reference the old hostname.
restart the server1 server and start the WebSphere_Portal server on the virtual machine.

WebSphere Portal is now ready to be used in this virtual machine instance.

url

Problem we locally have :

[5/22/12 8:58:13:354 EDT] 00000000 LdapRegistryI A SECJ0418I: Cannot connect to the LDAP server ldap://portal.demos.hal.com:389.

Solution [disable security] :

vi /opt/IBM/WebSphere/wp_profile/config/cells/portal/security.xml 2-nd line ... <security:Security xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" ... enabled="false">

And we can start Admin Console to change LDAP settings ...
Security + Global security + General Properties + *Host
"Test Connection" : The test connection operation for LDAP host portalv7.demos.hal.com on port 389 was successful.

But Portal does not start properly :

Error 404: javax.servlet.UnavailableException: Initialization of one or more services failed. [5/22/12 9:47:29:691 EDT] 00000016 SchedulerImpl E SCHD0124E: Unable to initialize wps/Scheduler due to error: com.ibm.ws.extensionhelper.exception.UnableToInitializeException: com.ibm.websphere.ce.cm.StaleConnectionException: [jcc][t4][10380][11951][4.8.87] Required property "portal.demos.hal.com" is unknown host. ERRORCODE=-4222, SQLSTATE=08001DSRA0010E: SQL State = 08001, Error Code = -4,222

There are issues connecting to the database server.

Un altre error similar (/opt/IBM/WebSphere/wp_profile/logs/WebSphere_Portal/SystemErr.log):

[6/11/12 5:36:35:224 EDT] 00000040 SystemErr R com.ibm.websphere.ce.cm.StaleConnectionException: [jcc][t4][2043][11550][4.8.87] Exception java.net.ConnectException: Error opening socket to server portal.demos.ibm.com/127.0.0.1 on port 50,000 with message: Connection refused. ERRORCODE=-4499, SQLSTATE=08001DSRA0010E: SQL State = 08001, Error Code = -4,499

Verify 2 points : have a line in /etc/services file:

db2c_db2inst1 50000/tcp

and

[root@portal /home]$ su - db2inst1 -bash-3.2$ -bash-3.2/home/db2inst1$ db2 get dbm cfg | grep SVCENAME TCP/IP Service name (SVCENAME) = db2c_db2inst1 -bash-3.2/home/db2inst1$ db2set -all [i] DB2COMM=tcpip [i] DB2AUTOSTART=YES [g] DB2SYSTEM=portal.demos.hal.com [g] DB2INSTDEF=db2inst1 [g] DB2ADMINSERVER=db2admin -bash-3.2$

Top

JMS Topologies

When developing and testing JMS applications in WebSphere Studio V5, you have several JMS provider options:

By default, WebSphere Studio is configured to run a special JMS Provider called MQ for Java Developers (MQJD). Unlike the normal Embedded Messaging Server, this MQJD simulator is a pure Java JMS provider, so it avoids installation issues and the overhead of separate C processes running in the development environment. MQJD implements all of the JMS APIs, but it does not support security checks, persistence, or JMS communications across process boundaries. As a result, it does not work with application clients.
You can set up the WebSphere Test Environment Application Server running within WebSphere Studio to run its own Embedded Messaging Server.
You can configure WebSphere Studio V5 to connect to an Embedded Messaging Server that is installed with Application Server V5 on another computer.
JMS code running in the WebSphere Studio V5 test server can connect to a full WMQ provider running on a separate server.
Finally, you can configure the WebSphere Studio unit test server to connect to third-party JMS providers.

url

For monitoring and checking the status of resources, {WAS base with Embedded Messaging} such as queue depths, there are a couple of options. The preferred option is to use the JMX Mbeans provided with Application Serve for monitoring: JMSBasicFunction, JMSAdministration, and EmbeddedJMSAdministration.

V5 - use runmqsc and dspmq. Everything changes in WAS 6 and 7, unless you configure those to use normal MQ *instead of* the embedded SIBus messaging engine.

JMS providers

The JMS functionality that WebSphere v6 provides includes support for three types of JMS providers:

Default messaging provider (service integration bus)
WebSphere MQ provider
Generic JMS providers (implementing the ASF component of the JMS 1.0.2 specification)

url

"embedded" versus "MQ" JMS providers

The embedded JMS provider provides a robust implementation for WAS V6.1 to WAS V6.1 interaction, but it is not capable of supporting other environments, such as non-Java or non-JMS applications. For those environments, a product called WebSphere MQ is provided, which provides both a JMS and non-JMS messaging infrastructure for a wide variety of clients and platforms.

Experience J2EE using WAS 6.1, SG24-7297, page 389, [407/472]

WAS 6 Service integration

The service integration functionality within WebSphere Application Server V6 supports supports both message-oriented and service-oriented applications. The primary component of this functionality is the service integration bus, which provides the support for messaging and Web services applications. One or more application servers or clusters join a bus to become bus members. The service integration bus becomes a component of the Enterprise Service Bus (ESB).
The service integration functionality provides:

A fully compliant J2EE 1.4 JMS messaging provider, integrated within the application server. This messaging provider is the default messaging provider for the application server. It can support multi-server configurations and can be linked to WebSphere MQ, appearing as a queue manager. This new JMS provider replaces the embedded JMS provider available in WebSphere Application Server V5.

WAS V6 System Management and Configuration Handbook, SG24-6451-00, page 17 [41/1040]

Top

WAS and MQ

In WAS V6 the WebSphere MQ Client came with WAS as part of the lib directory structure and was referenced with the use the WebSphere environment variable MQ_INSTALL_ROOT.

In WAS V7, the client has been replaced with the WebSphere MQ V7 JCA 1.5 RA and is installed as a resource adapter. The MQ_INSTALL_ROOT variable is no longer used. Instead the native library path for the RA is used to identify the location of the required native libraries.

MQ Configuration

Connection Factory : {gestor de cues}

Connection Factory name := "MQCF1" ;
JNDI name := "MQCF1jndi" ;
Queue Manager := " " ;
Host := "localhost" ;
Port := 1491 ;
Channel := "SAG.SVRCONN" ;
Transport Type := "Client" ;

Custom Properties :

Name := "CCDTURL" ;
Value := "file://F1" ;

Queue Destinations :

Queue name := "QD1" ;
JNDI name := "QD1jndi" ;
Base Queue name := "QL1" ;

CCDT

String ccdtPath = "http://ccdtsrver/ccdts/qmgrp.tab"; String qmgrName = "*QMGRP"; // ok for MQCONNX, not for a MQOPEN/MQPUT1 ; MQQueueConnectionFactory factory = new MQQueueConnectionFactory(); factory.setCCDTURL(new URL(ccdtPath)); factory.setQueueManager(qmgrName); factory.setTemporaryModel("JMS.TEMPQ.MODEL"); conn = factory.createQueueConnection(); conn.start(); session = conn.createQueueSession(false, Session.AUTO_ACKNOWLEDGE); TemporaryQueue tempQ = session.createTemporaryQueue();

.bindings

Creating a .bindings file for UNIX, for InfoSphere Master Data Management Collaboration Server, Version 10.0.0

Issue <MQ_INSTALL_DIR>\Java\bin\JMSAdmin.bat, then this sequence:

InitCtx> def q(INBOUND_QUEUE_NAME)
InitCtx> def q(OUTBOUND_QUEUE_NAME)
InitCtx> def qcf(QUEUE_CONNECTION_FACTORY_NAME) transport(CLIENT) channel(java.channel) host(WMQ_SERVER_IP)
port(WMQ_SERVER_DEFINED_PORT) qmgr(QUEUE_MANAGER_NAME)
InitCtx> end

[publib]

How to test it

get the application : MessageProducerSSBBean {JMSExample.ZIP @ [1]}
configure MQ :
- define qmgr : jms/JMSExampleConnectionFactoryRef
- define queue : jms/JMSExampleQueueRef
- configure MQ for publish/subscribe
configure Application Server
- start the application server
- view the WebSphere MQ messaging provider panel
- define the JMS connection factory
- define the JMS queue
- (define the JMS topic)
- define the listener ports
deploy the application :
- Open the administrative console and navigate to Applications => Install New Application.
- Use the Application Installation panels to install the JMSExample.ear file :
  Path to the new application := local file system (JMSExample.ear) ;
restart the server :
C:\WebSphere Application Server\bin> stopServer/startServer server1

When you start the server, a number of status messages are printed to System.out (the console or in the SystemOut.log file)
Test the application
So far, we have configured the server, deployed the application, and successfully restarted the server. Now, we will test our application using the Universal Test Client (UTC), an IBM tool included with Rational Application Developer, the Application Server Toolkit (ASTK), and WebSphere Application Server. We will use the UTC to run our stateless session bean, and then watch System.out to see what the MDBs do.
The UTC is a J2EE application called IBMUTC.
http://localhost:9080/UTC/

If this URL doesn't work, verify that the application is deployed and running.
When you open the UTC using its URL, you need to locate the home for the EJB component you wish to test.

Pointer to Samples : [1] 0505_woolf & [2] 0504_barcia.

JMSAdmin.bat

Used to manage JMS objects.

MQ error logs

If Embedded Messaging is used, then AMQERR01.LOG file contents is written into :
SystemOut.log and SystemErr.log, located at <WAS_INSTALL>/profiles/profilename/logs/server1

WAS and MQ links

(WAS) Interoperation with WebSphere MQ
Dos puntos interesantes:
- comparison of WebSphere Application Server and WebSphere MQ messaging
- interoperation with WebSphere MQ: Comparison of architectures
Bruno es genial !

Commerce Bus Review - MQ integration

There are three different ways to integrate Commerce with WebSphere MQ:

WebSphere MQ as an external provider (no bus required)
WebSphere MQ server as a Service Integration Bus member
WebSphere MQ as a foreign bus (WebSphere MQ Link)

Interoperation with WebSphere MQ: comparison of architectures

The third approach seems the simplest way to integrate MQ and Commerce. With this solution applications can continue to send messages (store and forward) even if the MQ network is not available (and vice versa). Using MQ links require a bus to be defined in WCS. Messages in the Service Integration Bus can be stored in a database or a file system (shared and highly available), but the former option is preferred. MQ Link facilitates the interactions between applications since WCS messaging engine sees MQ queue manager as a foreign bus and MQ network sees messaging engine as a MQ queue manager. MQ Link transforms message formats from MQ to SIBus and vice versa. WebSphere MQ Link also provides high availability in WebSphere Commerce thanks to the HA Manager services. There will be multiple MQ Links that will connect to different queue managers (active/active) that will later consolidate these messages into a common queue. MQ Link cannot directly connect to cluster channel, it must connect to a gateway queue manager.

infocenter

Message exchange through a WebSphere MQ link

How service integration converts messages to and from WebSphere MQ format

Sequencia completa :
Configuring WebSphere MQ for use with WebSphere Commerce, Commerce se conectaría a través de un WebSphere MQ messaging provider queue connection factory al queue manager de MQ Creating a WebSphere MQ messaging provider queue connection factory.
Y habría una correspondencia directa entre las WebSphere MQ messaging provider queue destinations y las colas creadas en MQ Creating WebSphere MQ messaging provider queue destinations

Hasta aquí no hay ningún SIBus por medio.

Siguiendo la configuración aconsejada en el infocenter no se va a utilizar el SIBus; se define la comunicación con la infraestructura MQ. Sobre esta configuración que solo establece la comunicación general entre Commerce y MQ, vienen las posibles opciones que ofrece el conector JCA que viene con Commerce.

Primero la posibilidad de procesar los mensajes inbound de manera paralela o serializados (o las dos cosas) Inbound messages over WebSphere MQ
Pero también es posible activar más de un listener FAQ on custom configurations of WebSphere Commerce with WebSphere MQ
o conectar más de un MQ queue manager.

En general la mayoría de estos cambios de configuración se manejan simplemente modificando el fichero de instancia de Commerce (wc-server.xml). Pero siempre es posible personalizar los conectores JCA: aquí viene un ejemplo de como modificar los de salida (outbound) Customizing the outbound JCA HTTP web service adapter in WebSphere Commerce V7.0

error : eCommerce has no DDBB but gets a MQ msg

Asumiendo que Commerce está recibiendo los mensajes inbound a través de un listener para Websphere MQ ( inbound messages over WebSphere MQ ), en el caso que la petición inbound genere un error la documentación es muy generica ( Working with the Listener for WebSphere MQ ) : "If an error with the inbound request occurs, the message generating the error is placed on the error queue"

Colas

Concepts	Family	CheckList	Instalació	Ports	Commands	Fixes	Virtual Host
JVM tuning	Samples / Snoop	Seguridad - activar	Cluster	HA	Biblio	MQ	Consola
Seguridad Avanzada	SAG APP	CM & PS	hostname change	WAS log	v 8.5	Dubtes	Links