WAS

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.

WS Extended Deployment v 6.0.1 Install Guide, SA22-7998.pdf, page 8 of 29.

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.

1. deployment manager profile : a deployment manager administers Application Servers that are federated into its cell.
2. application server profile : the application server can be managed from its own administrative console and function independent of other Application Servers and deployment managers. Alternatively, it can be federated into a cell and managed by the deployment manager.

See wasprofile command.

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.

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:

• Deployment manager
• Node agent
• Application server

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.

WAS 6.0 Technical Overview, REDP3918.pdf, page 15 of 64

     Celula  / Nodo  / Server  / Cluster
     =======   =====   =======   ========
     logico    fisico  fisico    logico

     Nodo   == Maquina             Requiere un Node Agent.
     Server == JVM

     Celula  : agrupa Nodos        Requiere un Deployment Manager = WAS con herramientas.
     Cluster : agrupa Servers

• Community : free, open-source, lightweight J2EE application server. Get it !
• Express : 1 nodo, 1 App Server
• WAS : 1 nodo, N x App Server
• ND (network deployment) : N x nodos (alta disponibilidad, centralized administration).
• Extended Deployment.

WAS product family and products

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.

WAS 6.0 Technical Overview, REDP3918.pdf, page 3 of 64

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

• dynamic operations,
• extended manageability,
• high performance computing,
• business grid

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

What is WS Extended Deployment ? [publib]

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

WAS product family

crear Logs en otro FileSystem crear grupo wasgroup y mqm crear usuarios was1 y mqm con clave instalar MQ y luego parches MQ instalar WAS ( [cd]:\WAS\install.exe ) crear perfil Deployment Manager verificar instalación crear perfil Application Server verificar instalación instalar parches WAS federar nodo a celda crear Virtual Host incorporar DefaultApplication usar snoop activar seguridad

instalar WAS en PC-1. Services log using usr/pwd with "act as ..." & "log as ..." crear perfil Deployment Manager verificar instalación crear perfil Application Server (crea Server1 en PC-1) verificar instalación instalar parches WAS federar nodo a celda instalar WAS en PC-2 (Node02) & instalar parches WAS crear perfil Application Server (crea Server1 en PC-2) crear cluster Clust01 en dmgr (PC1) añadir Server-2 (nuevo) a Clust01 usando Node02 Servers, Clusters, click Cluster-Name, "Cluster Members". "New", Select Node := Node02 "Generate Unique HTTP ports := NO", as we have 2 machines / nodes / IPs.

Use /WAS/install command or launchpad.bat

  Com es tria el idioma ?  
W2K : Control Panel + Regional and Language Options : "General" + Your Locale.
WXP ?
W2k3 : Control Panel + Regional and Language Options : "Regional Options" + Customize "Standards and Formats".

Full install includes :

• the Application Server
• the Administrative interfaces
  • the command-line scripting interface
  • the web-based administrative console
• Embedded Messaging
• IBM HTTPD Server v 1.3.26

Default install locations :

• Linux : /opt/WebSphere/AppServer
• AIX : /usr/WebSphere/AppServer
• Solaris : /opt/WebSphere/AppServer
• Windows : c:\Program Files\WebSphere\AppServer

Deployment Manager := Dmgr01

A deployment Manager administers Application Servers that are federated into its cell.

 Node Name := w2kwasCellManager01
 Host Name := w2kwas
 Cell Name := w2kwasCell01

The Node Name is for administration by the deployment manager. The name must be unique within the cell.
The Host Name is the DNS name or the IP address of this computer.
The Cell Name is a logical name for the group of nodes administered by this deployment manager.

• install product.
• create Deployment Manager profile.
• start Deployment Manager so that other nodes can be federated into its cell.
• create an Application Server profile and federate it to the cell.
• ...
• enable security

First steps v 5 : (firststeps.bat)

• WS Info Center
• Start the Server
• Verify Installation
• Administrative Console
• Application Assembly Tool

First steps v 6 : (firststeps.bat del perfil Dmgr01)

• Installation verification
• Stop the deployment manager
• Administrative console
• Profile creation wizard
• Information center for WAS
• Migration wizard

First steps v 6 : (firststeps.bat del perfil AppSrv01)

• Installation verification
• Stop the server
• Administrative console
• Profile creation wizard
• Samples galery
• Information center for WAS
• Migration wizard

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

Profile Name := AppSrv01 A deployment Manager administers Application Servers that are federated into its cell. Node Name := w2kwasNode01 Host Name := w2kwas The Node Name is used for administration. If the node is federated, the name must be unique within the cell. The Host Name is the DNS name or the IP address of this computer.

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

• act as part of the operating system
• log on as a service

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

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

Now we can see cell w2kwasCell01 has 2 nodes :

w2kwasCellManager01 --------- Deploy Manager w2kwasNoder01 --------------- Application Server

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

dmgr

Those are the Default values

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".

So, for next server (Server2) those values (in alphabetical order) would be :

Veure la versió del WAS :

/opt/IBM/WebSphere/AppServer/bin/versionInfo.sh o versionInfo.bat

Veure la versió del IHS :

/opt/IBM/IHS/bin/apachectl -version

Veure la versió del PLUGIN :

/opt/IBM/WebSphere/Plugins/bin/versionInfo.sh

Veure el estat del Deploy Manager :

/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í :

/opt/IBM/IHS/bin # ./adminctl start

La seva configuració es troba a

/opt/IBM/IHS/conf/admin.conf

Administració "command line" de la consola administrativa :

/opt/IBM/WebSphere/AppServer/bin/wsadmin.sh

Bon consell : learn Python !

• VMware(was), 20022006 : Version 6.0.0.1 at versioninfo

• 364.305.498 6.0-WS-WAS-WinX32-RP0000002.zip

• c:\temp\fp606\unzip\update.exe => A suitable JVM could not be found. Please run the program again using the option -isjavahome <Java Home Dir>

• The preferred method of setting the JAVA_HOME environment variable is using the setupCmdLine.bat script provided with the WebSphere Application Server product or ./update -is:javahome install_root/java/jre

  The JAVA_HOME environment variable should be set to the directory where your JDK is installed.

• C:\Temp\Go_6.0.2\unzip\updateinstaller>
  .\update -is:javahome "C:\Program Files\IBM\WebSphere\AppServer\java\jre"

  The Update Installer is being run from an incorrect path. It should be run from the <product>\updateinstaller directory.

• Extract .zip file into C:\Program Files\IBM\WebSphere\AppServer

• Run c:\Program Files\IBM\WebSphere\AppServer\updateinstaller\update.exe

• VMware(was), 20022006 : Version 6.0.2.0 at versioninfo

• Clear c:\Program Files\IBM\WebSphere\AppServer\updateinstaller\ directory !

• Repeat with 257,587,045 6.0.2-WS-WAS-WinX32-FP0000007.zip

• VMware(was), 20022006 : Version 6.0.2.7 at versioninfo

Top

Heap Size

Conveniently, WebSphere Application Server (WAS) supports updating JVM parameters using its administration APIs, specifically, AdminConfig object.

import sys """ Change JVM heap size for all application servers in a cell """ # New heap size is passed as a parameter to the script max_heap_size=sys.argv[0] # Get the string with config ids of all serves server_confids=AdminConfig.list("Server") # Iterate over all servers - config ids are separated by \n for server_confid in server_confids.split("\n"): server_confid=server_confid.strip() # obtain the type - types are APPLICATION_SERVER, DEPLOYMENT_MANAGER, NODE_AGENT, WEB_SERVER server_type=AdminConfig.showAttribute(server_confid, "serverType") # we're changing the heap size for application servers - we want to exclude node agents, etc. if server_type == "APPLICATION_SERVER": server_name=AdminConfig.showAttribute(server_confid, "name") # this is the query to get JavaVirtualMachine configuration object for a particular server jvm_path="/Server:%s/JavaProcessDef:/JavaVirtualMachine:/" % server_name jvm_confid=AdminConfig.getid(jvm_path) # "modify" accepts a list of lists - each list contains name and value (odd choice I must say, why not use tuples?) AdminConfig.modify(jvm_confid, [["maximumHeapSize", max_heap_size]]) # Commit our changes to the repository AdminConfig.save()

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.

Finding the URL for a servlet or JSP

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.

To find the URL for a servlet or JSP:

1. Find the context root of the Web module containing the servlet.
2. Find the URL for the servlet.
3. Find the virtual host where the Web module is installed.
4. Find the aliases by which the virtual host is known.
5. Combine the virtual host alias, context root, and URL pattern to form the URL request of the servlet/JSP.

For example, to look up the URL for the snoop servlet :

1. Find the context root of the Web module DefaultWebApplication of the DefaultApplication enterprise application. This Web module contains the snoop servlet.
   • a. From the console navigation tree, select Applications -> Enterprise Applications.
   • b. Click the application that you are interested in, in our case DefaultApplication.
   • c. On the Configuration tab, select View Deployment Descriptor under Additional Properties.

     In the deployment descriptor window for the DefaultApplication enterprise application you can see:

     • i. There is only one Web module in this application, DefaultWebApplication.
     • ii. The context root for the DefaultWebApplication Web module is "/". We will use this later.

     <context-root> /</context-root>

   • d. Click Back to return to the DefaultApplication configuration.

2. Find the URL for the snoop servlet:
   • a. In the DefaultApplication configuration page, select Web Modules under Related Items.
   • b. Click the DefaultWebApplication Web module to see the general properties.
   • c. Click View Deployment Descriptor under Additional Properties. This displays the Web module properties window. Note that the URL pattern for the snoop servlet starting from the Web module context root is "/snoop/*". The Web module context root was "/".

     <url-pattern> /snoop/*</url-pattern>

   • d. Note that as you navigate through the windows, a navigation path is displayed below the Messages area. Click DefaultApplication to return to the application configuration page.

3. Find the virtual host where the DefaultWebApplication Web module is installed:
   • In the DefaultApplication configuration page, select Map virtual hosts for web modules under Additional Properties. This will display all of the Web modules contained in the enterprise application, and the virtual hosts in which they have been installed. Note that the DefaultWebApplication Web module has been installed on the default_host virtual host.

4. Find the host aliases for the default_host virtual host.
   • a. From the console navigation tree, select Environment Virtual Hosts.
   • b. Click default_host.
   • c. Select Host Aliases under Additional Properties. This shows the list of aliases by which the default_host virtual host is known.

     Note that the aliases are composed of a DNS host name and a port number. The host aliases for the default_host virtual host are *:80, *:9080 and *:9443, "*" meaning any host name.

5. Combine the virtual host alias, context root and URL pattern to form the URL request of the snoop servlet. Requests for the servlet with any of the following URLs will map to the default_host virtual host:

   http://<hostname>:80/snoop http://<hostname>:9080/snoop https://<hostname>:9443/snoop

Código instalado :

 c:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\installedApps\
       w2kwasCell01\DefaultApplication.ear\DefaultWebApplication.war\WEB-INF\classes\SnoopServlet.class

Get the code or write it ! (Feb 2006)

Start at developerWorks [***]

url + "Configuring security with scripting" : url

Or was600nd_security.pdf, chapter 13 !

 .../IBM/WebSphere/AppServer/etc                    en c:\temp\save\global\
 .../IBM/WebSphere/AppServer/profiles/Dmgr01/etc    en c:\temp\save\Dmgr01\
 .../IBM/WebSphere/AppServer/profiles/AppSrv01\etc  en c:\temp\save\AppSrv\

com.ibm.SOAP.securityEnabled=true
com.ibm.SOAP.loginUserid=
com.ibm.SOAP.loginPassword=

 Ahora, una IE hacia
   http://localhost:9060/ibm/console/secure/logon.do
 nos redirige a
   https://localhost:9043/ibm/console/logon.jsp
 y hay campo de PWD ...

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.

• create cluster Cluster01 : WAC + Servers + Clusters + "New"
• add a new member : click "Cluster members" + "New"
• provide a Name and Select a Node + "Generate unique HTTP ports"

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

Mind Virtual Host for port 9081 !

High Availability Solutions, SG24-6688.pdf

URL If the node is not federated, WAS Administrative console can be found here http://localhost:9061/ibm/console/ It is removed when the node is federated, and it becomes managed by Deploy Manager : http://localhost:9060/ibm/console/ La URL en versión 5 és http://servidor:9090/admin/ o http://servidor:9060/ibm/console/ en versión 6 ! Se sap mirant el fitxer <installation_root>/profiles/<profile_name>/config/cells/<cell_name>/nodes/<node_name>/serverindex.xml i el fitxer <installation_root>/profiles/<profile_name>/config/cells/<cell_name>/virtualhosts.xml. Per defecte és WC_adminhost = 9060 i WC_adminhost_secure = 9443 Ha engegat be quan al fitxer SystemOut.log hi trobem el missatge CWWSR0221I: Application started: isclite How to change administrative console port ? If you cannot start the administrative console because the console port conflicts with an application that is already running on the machine, change the port number in the <install_root>/profiles/<profile name>/config/cells/<cell_name>/nodes/<node_name>/servers/<server_name>/server.xml file and the <install_root>/profiles/<profile name>/config/cells/<cell_name>/virtualhosts.xml files. WAS ND v 6, Using the administrative clients, wasv600nd_admin.pdf, page 21 [29/591] You can find it using was console by the path ... servers type := was select "server1" click on "port" scroll down to find "WC_adminhost" Trassa en engegar : Deploy Manager : C:\WAS51\DMgr\logs\dmgr\StartServer.log Server : C:\WAS51\AppServer\logs\server1\startServer.log

Console requirements for the Browser ?

Menu structure From f:\MQ\Projects\BBVA\WAS\Consola\MENUS.TXT => CD 1.- Servidores 1.1.- Servidores de aplicaciones 1.1.1.- < select server > 1.1.2.- propiedades adicionales 1.1.2.1.- Servicio de transacciones 1.1.2.2.- Contenedor Web 1.1.2.2.1.- Agrupación de hebras 1.1.2.2.2.- Gestión de sesiones 1.1.2.2.3.- Transportes de HTTP 1.1.2.2.3.1.- "6680" - puerto para comunicar peticiones al contenedor Web 1.1.2.2.4.- Propiedades personalizadas 1.1.2.3.- Contenedor de EJB 1.1.2.4.- Servicio de antememoria dinámica 1.1.2.5.- Registro cronológico y rastreo 1.1.2.5.1.- Rastreo de diagnóstico 1.1.2.5.2.- Anotaciones cronológicas de JVM 1.1.2.5.3.- Anotaciones cronológicas de proceso 1.1.2.5.4.- Anotaciones cronológicas de servicio de IBM 1.1.2.6.- Servicio de receptor de mensajes 1.1.2.6.1.- Puertos receptores < Nombre > Nombre JNDI de la fábrica de conexiones Nombre JNDI del destino 1.1.2.6.2.- Agrupación de hebras 1.1.2.6.3.- Propiedades personalizadas 1.1.2.7.- Servicio ORB 1.1.2.8.- Propiedades personalizadas 1.1.2.9.- Servicios de administración Autónomo ? Conector preferido ? SOAP_Connector/ RMI_Connector 1.1.2.9.1.- Conectores JMX 1.1.2.9.2.- Proveedores de MBean de extensión 1.1.2.9.3.- Servicios de depósito 1.1.2.9.4.- Propiedades personalizadas 1.1.2.10.- Servicio de rastreo de diagnóstico Salida de rastreo - Nombre de archivo = $(SERVER_LOG_ROOT)/trace.log 1.1.2.11.- Servicio de depuración Puerto de depuración de JVM = 7777 Puerto de depuración de BSF = 4444 1.1.2.12.- Anotaciones cronológicas de servicio de IBM Nombre de archivo = $(LOG_ROOT)/activity.log 1.1.2.13.- Servicios personalizados 1.1.2.14.- Componentes de servidor 1.1.2.14.1.- Servidor de nombres 1.1.2.14.2.- Servidor de aplicaciones 1.1.2.14.2.1.- Servicio de transacciones 1.1.2.14.2.2.- Contenedor Web 1.1.2.14.2.3.- Contenedor de EJB 1.1.2.14.2.4.- Servicio de antememoria dinámica 1.1.2.14.2.5.- Registro cronológico y rastreo 1.1.2.14.2.6.- Servicio de receptor de mensajes 1.1.2.14.2.7.- Servicio ORB 1.1.2.14.2.8.- Propiedades personalizadas 1.1.2.14.2.9.- Servicios de administración 1.1.2.14.2.10.- Servicio de rastreo de diagnostico 1.1.2.14.2.11.- Servicio de depuración 1.1.2.14.2.12.- Anotaciones cronológicas de IBM 1.1.2.14.2.13.- Servicios personalizados 1.1.2.14.2.14.- Componentes del servidor 1.1.2.14.2.15.- Definición de proceso 1.1.2.14.2.16.- Servicio de supervisión del rendimiento 1.1.2.14.2.17.- Puntos finales 1.1.2.14.2.18.- Cargador de clases 1.1.2.14.2.19.- Servicios Web : enlaces por omisión para Web Services Security 1.1.2.14.2.20.- Configuración del Asesor de rendimiento de tiempo de ejecución 1.1.2.14.3.- Servidores JMS Nombre de colas 1.1.2.14.3.1.- Punto final del puerto de seguridad Numero del puerto TCP/IP del puerto receptor utilizado internamente. 1.1.2.14.3.2.- Propiedades personalizadas 1.1.2.14.3.3.- Componentes de servidor 1.1.2.14.3.4.- Servicios de administración 1.1.2.14.3.5.- Servicios de rastreo de diagnóstico 1.1.2.14.3.6.- Anotaciones cronológicas de servicio de IBM 1.1.2.14.3.7.- Definición de proceso 1.1.2.14.3.8.- Puntos finales 1.1.2.15.- Definición de proceso Nombre ejecutable : $(JAVA_HOME)/bin/java Directorio de trabajo : $(USER_INSTALL_ROOT) 1.1.2.15.1.- Máquina virtual Java 1.1.2.15.2.- Ejecución de proceso 1.1.2.15.3.- Anotaciones cronológicas de proceso 1.1.2.15.4.- Entradas de entorno 1.1.2.15.5.- Politicas de supervisión 1.1.2.15.6.- Registro cronológico y rastreo 1.1.2.16.- Servicio de supervisión del rendimiento 1.1.2.17.- Puntos finales SOAP_CONNECTOR_ADDRESS := 8880 1.1.2.18.- Cargador de clases 1.1.2.19.- Servicios Web : enlaces por omisión para Web Services Security 1.1.2.19.1.- Anclas de confianza 1.1.2.19.2.- Almacen de certificados de colecciones 1.1.2.19.3.- Localizadores de claves 1.1.2.19.4.- Evaluadores de ID de confianza 1.1.2.19.5.- Correlaciones de inicio de sesión 1.1.2.20.- Configuración del asesor de rendimiento de tiempo de ejecución 1.1.2.21.- Seguridad del servidor 1.2.- Servidores JMS 1.3.- Clusteres 1.4.- Topologia de clusteres 2.- Aplicaciones 2.1.- Aplicaciones de empresa 2.2.- Instalar una nueva aplicación 3.- Recursos 3.1.- Proveedores de JDBC 3.2.- Proveedores genéricos de JMS 3.3.- Proveedores de JMS de WebSphere 3.4.- Proveedores de JMS de WebSphere MQ 3.5.- Proveedores de correo 3.6.- Proveedores de entorno de recursos 3.7.- Proveedores de URL 3.8.- Adaptadores de recursos 4.- Seguridad 4.1.- Seguridad global 4.2.- SSL 4.3.- Mecanismos de autenticación 4.3.1.- LTPA 4.4.- Registros de usuarios 4.4.1.- Sistema operativo local 4.4.2.- LDAP 4.4.3.- Personalizado 4.5.- Configuración de JAAS 4.5.1.- Inicios de sesión de la aplicación 4.5.2.- Inicios de sesión del sistema 4.5.3.- Datos de autenticación de J2C 4.6.- Protocolo de autenticación 4.6.1.- Autenticación de entrada CSIv2 4.6.2.- Autenticación de salida CSIv2 4.6.3.- Transporte de entrada CSIv2 4.6.4.- Transporte de salida CSIv2 4.6.5.- Transporte de entrada SAS 4.6.6.- Transporte de salida SAS 4.7.- Servicios Web 4.7.1.- Propiedades 4.7.2.- Anclas de confianza 4.7.3.- Almacen de certificados de colecciones 4.7.4.- Localizadores de claves 4.7.5.- Evaluadores de ID de confianza 4.7.6.- Correlaciones de inicio de sesión 5.- Entorno 5.1.- Actualizar el plug-in del servidor Web 5.2.- Sistemas principales virtuales 5.2.1.- < seleccionar nombre lógico > 5.2.2.- Propiedades adicionales 5.2.2.1.- Alias de sistema principal 5.2.2.1.1.- "6680" - alias de DNS por los que se conoce el sistema principal 5.2.2.2.- Tipos de MIME 5.3.- Gestionar variables de WebSphere 5.4.- Bibliotecas compartidas 5.5.- Dominios de duplicación interna 5.6.- Denominación 5.6.1.- Enlaces de espacio de nombres 5.6.2.- Usuarios de CORBA Naming Service 5.6.3.- Grupos de CORBA naming Service 6.- Administración del sistema 6.1.- Célula 6.2.- Gestor de despliegue 6.3.- Nodos 6.4.- Agentes de nodo 6.5.- Usuarios de consola 6.6.- Grupos de consola 7.- Resolución de problemas 7.1.- Anotaciones cronológicas y rastreo 7.2.- Problemas de configuración 7.3.- PMI Request Metrics

Per a tenir "Consola Administrativa" (Portal Server + Content Manager) [ que us cal per engegar el "Verbose Garbage Collector" ] només cal que engegueu el server1. Es a dir, la comanda "màgica" es startserver server1 Després de una curta estoneta, tindreu la consola administrativa a la URL http://ip_de_la_maquina:9090/admin/ versio 5 http://ip_de_la_maquina:9060/ibm/console/ versio 6

From [*** publib.boulder ***]

Or
  Installing WebSphere MQ as the JMS provider
or
  Installing WebSphere embedded messaging as the JMS provider

SSO - Curs Admin Lotus Dec'2009

url.

• configuration time :
  • export LTPA key from WAS
  • import LTPA key into Lotus LDAP

  Looks like Lotus can manage Lotus keys and WAS keys, whilst WAS can only manage WAS keys.

• run time :
  • user logs into Portal screen
  • usr+pwd go into LDAP, and LTPA key comes back if known and correct
  • when another portlet goes into WAS applications, the LTPA key is sent to WAS, so user is known at WAS, and no more logins are required.

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

Thread Analyzer tool - url
[T42:\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

1. create "{wp_root}\update\fixes\" directory.
2. put DTT.jar/PK18903.jar into this directory
3. shutdown Portal
4. install Portal Update Installer : url - unzip into "{wp_root}\update\" directory.
5. install fix using Portal Update Installer :
   call updatePortal -fix -installdir "c:\IBM\PortalServer" -fixDir "{wp_root}\update\fixes" -install -fixes PK18903
6. restart Portal - "startserver Server1"
7. install {wp_root}\jcr\installableApps\icmjcr.ear to the Portal Server using WAS admin console
8. update 174.923 icmdtt.jar in {wp_root}\jcr\lib directory ! [fix 20-04-2006]
9. restart Portal
10. edit {wp_root}\jcr\admin\export.properties to include
    jcr.export.maxFileLength=20 jcr.exportToFile=false jcr.export.path=C:/Exportar_Documentos/ROOTWORKSPACE
11. 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\".
12. on the destination machine, edit {wps_home}\jcr\admin\import.properties
13. 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

1. Stop the Portal Server
2. Backup and clear out the log files in {wp_root}\log
3. 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
4. Start the Portal Server
5. 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.
6. 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:

1. stop the WebSphere_Portal server running on the virtual machine.
   /opt/IBM/WebSphere/wp_profile/bin/stopServer.sh WebSphere_Portal –user wpadmin –password claudepas
2. 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
3. update the host name for the virtual machine instance per the instructions of the operating system.
   $
4. 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.
5. 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.
6. 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.
7. run the command
   ./ConfigEngine.sh action-clean-scheduled-tasks -DWasPassword=password
   to clear any scheduled tasks. Existing scheduled tasks might reference the old hostname.
8. 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.

---

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

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" ;

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.

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 LOG

LOG ubication

Logs can be found under install_root/profiles/profile_name/logs/server_name. The default profile name is AppSrv01 and the default server name is server1.

Example: /usr/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1. SystemOut.log is the file containing everything that was logged to standard out.

Logs can also be viewed from the admin console by navigating to Troubleshooting/Logging and Tracing/server_name/Runtime.

dislay LOG

C:\cmds> type tail_logs.bat @echo off SET CDM_WAS_HOME=c:\was C:\eines\tail -f %CDM_WAS_HOME%\profiles\AppSrv01\logs\server1\Systemout.log

WAS error

If we find in Event Log viewer ... WAS service terminated with service-specific error 134218516 (0x8000314) all we have to do is to delete server1.pid file at c:\Program Files\IBM\WebSphere\AppServer\profiles\CDM572\logs\server1\ !!!

---

Dubtes

Top of page

• How to start WAS as a Service ? So it starts with power-on, and not at Logon time (as with BAT in Startup folder).

• You should not be using MDB for a request / reply model. You CANNOT use the CCDT for the MDBs. {mr fjb saper}

• com es configura el WAS per accedir a un MQ Server remot ?

  Messaging resources; Configuring JMS resources for the WebSphere MQ messaging provider;

• és cert "WAS 5.1 fa servir MQ Client. WAS 6, no." ?

  Trobo "JMS 1.1" i "JCA 1.5".

• que és una "Connection Factory" ? Es un Gestor de Cues en terminologia JNDI.

  To create a new connection factory, complete the following steps:

  1. Click New in the content pane.
  2. Specify the following required properties. You can specify other properties, as described in a later step.
     • Name
       The name by which this connection factory is known for administrative purposes within WAS.
     • JNDI name
       The JNDI name that is used to bind the connection factory into the namespace.
     • CCSID
       The coded character set identifier for use with the WebSphere MQ queue manager; for example: 850.
  3. Click Apply. This defines the JMS connection factory to WebSphere Application Server, and enables you to browse or change additional properties.

  url

---

Links

Top of page

• Alberto : SG24-6195-00 - Abstract : WAS V5.1 System Management and Configuration WebSphere Handbook Series (13 MB)
  [T42:\MQ\WAS\Llibres_WAS\5.1]
• WAS v6 System Management & Configuration Handbook
• Monitoring
• Tech Journal & RedBooks.
• jBoss - open source App Server.
• Potential risk when using Web based applications on WebSphere Application Server (PK81387) {03/2009}
• WAS6.1 Installation on SUSE11 64-bit ESE url (int)
• Using WebSphere MQ binding with a client channel definition table url (developerWorks +++ paper)
• WebSphere Application Server V7: Concepts, Planning and Design : Redbook, pdf,
• Google, a9
• Tinet
• Back to main page
• Site map
• Escriu-me !

---

Site under construction.

Updated 22/5/2012 (a).

---