Création d'un profiles sur WebSphere Application Server.

1. Avant-propos
1.1. Présentation
1.2. Introduction
2. Profiles
2.1. Lister les profiles existants
2.2. Création d'un profile
2.3. Vérification de la création d'un profile
3. Noeuds
3.1. Création d'un noeud
3.2. Vérification de la création du noeud
4. Conclusion
4.1. Lien de la documentation IBM substitution

1. Avant-propos


1.1 - Présentation.


+------------------------------+                                               +-----------------------------+ 
| Serveur RAFW                 |                                               | Serveur WebSphere 8.0.0.5   | 
| Hostname : arecibo           |---(Création d'une action RAF et execution)--->| Hostname : arecibo          | 
| Os : Linux 2.6.32            |                                               | Os : Linux                  | 
|                              |                                               | DMGR : areciboNetwork       | 
|                              |                                               | NODE : areciboNode          | 
+------------------------------+                                               +-----------------------------+ 

1.2 - Introduction


Afin de rajouter un noeud WebSphere, nous allons créer un profile was.

2. Profiles


Les profiles doivent être créés afin de pouvoir rajouter des noeuds.

2.1 - Lister les profiles existants


Pour se faire nous allons lancer la commande suivante :
./manageprofiles.sh -listProfiles
root@arecibo:/apps/WebSphere/AppServer80/bin# ./manageprofiles.sh -listProfiles
15-Oct-2013 14:48:10 java.util.prefs.FileSystemPreferences$2 run
INFO: Created user preferences directory.
[dmgr]
root@arecibo:/apps/WebSphere/AppServer80/bin#

2.2. Création d'un profile


racine_serveur_app/bin/manageprofiles.sh -create
-profileName nom_profil
-profilePath racine_profil
-templatePath chemin_modèle .

Exemple avec la commande suivante:
./manageprofiles.sh -create -profileName profileTURLAN -profilePath /apps/WebSphere/profilesTURLAN
root@arecibo:/apps/WebSphere/AppServer80/bin# ./manageprofiles.sh  -create -profileName profileTURLAN -profilePath /apps/WebSphere/profilesTURLAN

INSTCONFSUCCESS: Success: Profile profileTURLAN now exists. Please consult /apps/WebSphere/profilesTURLAN/logs/AboutThisProfile.txt for more information about this profile.
root@arecibo:/apps/WebSphere/AppServer80/bin#

2.3. Vérification de la création d'un profile


Pour se faire nous allons lancer la commande suivante :
./manageprofiles.sh -listProfiles
root@arecibo:/apps/WebSphere/AppServer80/bin# ./manageprofiles.sh -listProfiles
[dmgr, AppSrv01, profileTURLAN]
root@arecibo:/apps/WebSphere/AppServer80/bin#

3. Noeuds


Lors de l'ajout d'un noeud, nous devons le rattacher à un profile.
Pour se faire nous allons lancer la commande suivante :
./addNode.sh arecibo -profileName profileTURLAN

3.1 - Création d'un noeud.


root@arecibo:/apps/WebSphere/profilesTURLAN/bin# ./addNode.sh arecibo -profileName profileTURLAN
ADMU0116I: Tool information is being logged in file
           /apps/WebSphere/profilesTURLAN/logs/addNode.log
ADMU0128I: Starting tool with the profileTURLAN profile
CWPKI0308I: Adding signer alias "root_1" to local keystore
           "ClientDefaultTrustStore" with the following SHA digest:
           07:EB:B9:99:A7:39:09:FF:E0:B7:35:AF:4C:F3:C2:F9:F5:D3:DA:C4
ADMU0001I: Begin federation of node areciboNode02 with Deployment Manager
           at arecibo:8879.
ADMU0009I: Successfully connected to Deployment Manager Server:
           arecibo:8879
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: server1
ADMU2010I: Stopping all server processes for node areciboNode02
ADMU0512I: Server server1 cannot be reached. It appears to be stopped.
ADMU0024I: Deleting the old backup directory.
ADMU0015I: Backing up the original cell repository.
ADMU0012I: Creating Node Agent configuration for node: areciboNode02
ADMU0014I: Adding node areciboNode02 configuration to cell:
           areciboCell
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0018I: Launching Node Agent process for node: areciboNode02
ADMU0020I: Reading configuration for Node Agent process: nodeagent
ADMU0022I: Node Agent launched. Waiting for initialization status.
ADMU0030I: Node Agent initialization completed successfully. Process id is:
           8621


ADMU0300I: The node areciboNode02 was successfully added to the
           areciboCell cell.


ADMU0306I: Note:
ADMU0302I: Any cell-level documents from the standalone areciboCell
           configuration have not been migrated to the new cell.
ADMU0307I: You might want to:
ADMU0303I: Update the configuration on the areciboCell Deployment Manager
           with values from the old cell-level documents.


ADMU0306I: Note:
ADMU0304I: Because -includeapps was not specified, applications installed on
           the standalone node were not installed on the new cell.
ADMU0307I: You might want to:
ADMU0305I: Install applications onto the areciboCell cell using wsadmin
           $AdminApp or the Administrative Console.


ADMU0003I: Node areciboNode02 has been successfully federated.
root@arecibo:/apps/WebSphere/profilesTURLAN/bin#

3.2 - Vérification de la création du noeud


Nous allons vérifier la création du noeud à la console (capture d'écran), mais également en ligne de commandes.
root@arecibo:/apps/WebSphere/profilesTURLAN/logs/nodeagent# more nodeagent.pid
8621
root@arecibo:/apps/WebSphere/profilesTURLAN/logs/nodeagent# ps -ef | grep 8621
root      8621     1  0 Oct15 ?        00:02:01 /apps/WebSphere/AppServer80/java/bin/java -Xmaxt0.5 -Dwas.status.socket=45574 -Declipse.security -Dosgi.install.area=/apps/WebSphere/AppServer80 -Dosgi.configuration.area=/apps/WebSphere/profilesTURLAN/servers/nodeagent/configuration -Dosgi.framework.extensions=com.ibm.cds,com.ibm.ws.eclipse.adaptors -Xshareclasses:name=webspherev80_%g,groupAccess,nonFatal -Xbootclasspath/p:/apps/WebSphere/AppServer80/java/jre/lib/ext/ibmorb.jar:/apps/WebSphere/AppServer80/java/jre/lib/ext/ibmext.jar -Dorg.osgi.framework.bootdelegation=* -classpath /apps/WebSphere/profilesTURLAN/properties:/apps/WebSphere/AppServer80/properties:/apps/WebSphere/AppServer80/lib/startup.jar:/apps/WebSphere/AppServer80/lib/bootstrap.jar:/apps/WebSphere/AppServer80/lib/jsf-nls.jar:/apps/WebSphere/AppServer80/lib/lmproxy.jar:/apps/WebSphere/AppServer80/lib/urlprotocols.jar:/apps/WebSphere/AppServer80/deploytool/itp/batchboot.jar:/apps/WebSphere/AppServer80/deploytool/itp/batch2.jar:/apps/WebSphere/AppServer80/java/lib/tools.jar -Dorg.osgi.framework.bootdelegation=* -Dibm.websphere.internalClassAccessMode=allow -Xms50m -Xmx256m -Xcompressedrefs -Xscmaxaot4M -Xnoaot -Xscmx90M -Dws.ext.dirs=/apps/WebSphere/AppServer80/java/lib:/apps/WebSphere/profilesTURLAN/classes:/apps/WebSphere/AppServer80/classes:/apps/WebSphere/AppServer80/lib:/apps/WebSphere/AppServer80/installedChannels:/apps/WebSphere/AppServer80/lib/ext:/apps/WebSphere/AppServer80/web/help:/apps/WebSphere/AppServer80/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime -Dderby.system.home=/apps/WebSphere/AppServer80/derby -Dcom.ibm.itp.location=/apps/WebSphere/AppServer80/bin -Djava.util.logging.configureByServer=true -Duser.install.root=/apps/WebSphere/profilesTURLAN -Djava.ext.dirs=/apps/WebSphere/AppServer80/tivoli/tam:/apps/WebSphere/AppServer80/java/jre/lib/ext -Djavax.management.builder.initial=com.ibm.ws.management.PlatformMBeanServerBuilder -Dpython.cachedir=/apps/WebSphere/profilesTURLAN/temp/cachedir -Dwas.install.root=/apps/WebSphere/AppServer80 -Djava.util.logging.manager=com.ibm.ws.bootstrap.WsLogManager -Dserver.root=/apps/WebSphere/profilesTURLAN -Dcom.ibm.security.jgss.debug=off -Dcom.ibm.security.krb5.Krb5Debug=off -Djava.awt.headless=true -Djava.library.path=/apps/WebSphere/AppServer80/lib/native/linux/x86_64/:/apps/WebSphere/AppServer80/java/jre/lib/amd64/default:/apps/WebSphere/AppServer80/java/jre/lib/amd64:/apps/WebSphere/AppServer80/lib/native/linux/x86_64/:/apps/WebSphere/AppServer80/bin:/opt/CA/SharedComponents/JRE/1.5.0_11/lib:/opt/CA/SharedComponents/lib:/opt/CA/CAlib:/opt/CA/SharedComponents/ccs/dia/lib:/opt/CA/SharedComponents/ccs/dia/dna/lib:/opt/CA/SharedComponents/JRE/1.5.0_11/lib/i386:/opt/CA/SharedComponents/JRE/1.5.0_11/lib/i386/client:/opt/CA/SharedComponents/Csam/SockAdapter/lib:/usr/lib: -Djava.endorsed.dirs=/apps/WebSphere/AppServer80/endorsed_apis:/apps/WebSphere/AppServer80/java/jre/lib/endorsed:/apps/WebSphere/AppServer80/endorsed_apis:/apps/WebSphere/AppServer80/java/jre/lib/endorsed -Djava.security.auth.login.config=/apps/WebSphere/profilesTURLAN/properties/wsjaas.conf -Djava.security.policy=/apps/WebSphere/profilesTURLAN/properties/server.policy com.ibm.wsspi.bootstrap.WSPreLauncher -nosplash -application com.ibm.ws.bootstrap.WSLauncher com.ibm.ws.runtime.WsServer /apps/WebSphere/profilesTURLAN/config areciboCell areciboNode02 nodeagent
root     10626  8782  0 10:16 pts/0    00:00:00 grep 8621
root@arecibo:/apps/WebSphere/profilesTURLAN/logs/nodeagent#

4. Conclusion


4.1 - Lien de la documentation IBM substitution


Url ibm pour la création d'un environnement.