03-IBM-WAS7.0 Creating DMGR and standalone profile and federating to DMGR-by Srikant S. Ande

In this document I tried to write as less as possible English and concentrated to include only Information, ‘How to’, commands and its output. I suggest using Google do read theory from many sites & pdf books.

I am a doer who always believe in learning & sharing, I am not topic expert but tried to cover my knowledge in this document so that person like me can use this document and understand the topic. I am not saying this doc is 100% error proof. If you find any error or want to share some thing to add or feedback, please write to Srikant.Ande@Gmail.com

Srikant Ande

1. Lab setup info

[wsadm@WASHOST1 ~]$ arch

i686

[wsadm@WASHOST1 ~]$

[wsadm@WASHOST1 ~]$ cat /etc/redhat-release

Red Hat Enterprise Linux Server release 5.4 (Tikanga)

[wsadm@WASHOST1 ~]$

[wsadm@WASHOST1 ~]$ uname -a

Linux WASHOST1 2.6.18-164.el5 #1 SMP Tue Aug 18 15:51:54 EDT 2009 i686 i686 i386 GNU/Linux

[wsadm@WASHOST1 ~]$

[wsadm@WASHOST1 ~]$ id

uid=500(wsadm) gid=500(wsadm) groups=500(wsadm) context=user_u:system_r:unconfined_t:s0

[wsadm@WASHOST1 ~]$

[wsadm@WASHOST1 ~]$ df -Ph /opt/

Filesystem Size Used Avail Use% Mounted on

/dev/sda2 4.9G 139M 4.5G 3% /opt

[wsadm@WASHOST1 ~]$

[wsadm@WASHOST1 ~]$ ls -rlth /opt

total 32K

drwx------ 2 root root 16K Apr 14 01:50 lost+found

drwxr-xr-x 2 wsadm wsadm 4.0K Apr 14 21:04 IHS

drwxr-xr-x 2 wsadm wsadm 4.0K Apr 14 21:05 WAS70

[wsadm@WASHOST1 ~]$

[wsadm@WASHOST1 ~]$ hostname

WASHOST1

[wsadm@WASHOST1 ~]$

[wsadm@WASHOST1 ~]$ ping -c2 `hostname`

PING WASHOST1 (192.168.123.111) 56(84) bytes of data.

64 bytes from WASHOST1 (192.168.123.111): icmp_seq=1 ttl=64 time=1.06 ms

64 bytes from WASHOST1 (192.168.123.111): icmp_seq=2 ttl=64 time=0.068 ms

--- WASHOST1 ping statistics ---

2 packets transmitted, 2 received, 0% packet loss, time 1000ms

rtt min/avg/max/mdev = 0.068/0.568/1.069/0.501 ms

[wsadm@WASHOST1 ~]$

<~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~>

2. Creating DMGR (Management) profile.

[wsadm@WASHOST1 ~]$ /opt/WAS70/bin/manageprofiles.sh -create -templatePath /opt/WAS70/profileTemplates/cell/dmgr -nodeProfilePath /opt/WAS70/profiles -profileName WASHOST1DMGR1 -cellName WASHOST1Cell -nodeName WASHOST1DMGR1Node

INSTCONFSUCCESS: Success: Profile WASHOST1DMGR1 now exists. Please consult /opt/WAS70/profiles/WASHOST1DMGR1/logs/AboutThisProfile.txt for more information about this profile.

[wsadm@WASHOST1 ~]$

[wsadm@WASHOST1 manageprofiles]$ tailf /opt/WAS70/logs/manageprofiles/WASHOST1DMGR1_create.log

<logger>com.ibm.wsspi.profile.WSProfileCLI</logger>

<class>com.ibm.wsspi.profile.WSProfileCLI</class>

<method>invokeWSProfile</method>

<message>Returning with return code: INSTCONFSUCCESS</message>

</record>

</log>

[wsadm@WASHOST1 manageprofiles]$

[wsadm@WASHOST1 profiles]$ cat /opt/WAS70/profiles/WASHOST1DMGR1/logs/AboutThisProfile.txt

Application server environment to create: Cell Deployment manager

Location: /opt/WAS70/profiles/WASHOST1DMGR1

Disk space required: 30 MB

Profile name: WASHOST1DMGR1

Make this profile the default: True

Cell name: WASHOST1Cell

Node name: WASHOST1DMGR1Node

Host name: WASHOST1

Enable administrative security (recommended): False

Administrative console port: 9060

Administrative console secure port: 9043

Bootstrap port: 9809

SOAP connector port: 8879

Run deployment manager as a service: False

Create a Web server definition: False

[wsadm@WASHOST1 profiles]$

<~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~>

3. Creating default (Application server) profile & federating to DMGR.

An application server profile runs your enterprise applications and makes them available to the internet or to an intranet. It contains a stand-alone application server by default. It create server named “server1” when we create default profile.

[wsadm@WASHOST1 ~]$ /opt/WAS70/bin/manageprofiles.sh -create -templatePath /opt/WAS70/profileTemplates/default -profileName WASHOST1AppSrv01 -ProfilePath /opt/WAS70/profiles -nodeName WASHOST1AppSrv01Node

INSTCONFSUCCESS: Success: Profile WASHOST1AppSrv01 now exists. Please consult /opt/WAS70/profiles/WASHOST1AppSrv01/logs/AboutThisProfile.txt for more information about this profile.

[wsadm@WASHOST1 ~]$

[wsadm@WASHOST1 manageprofiles]$ tailf /opt/WAS70/logs/manageprofiles/WASHOST1AppSrv01_create.log

<logger>com.ibm.wsspi.profile.WSProfileCLI</logger>

<class>com.ibm.wsspi.profile.WSProfileCLI</class>

<method>invokeWSProfile</method>

<message>Returning with return code: INSTCONFSUCCESS</message>

</record>

</log>

[wsadm@WASHOST1 ~]$

[wsadm@WASHOST1 ~]$ /opt/WAS70/profiles/WASHOST1AppSrv01/bin/addNode.sh WASHOST1 8879 -conntype SOAP

ADMU0116I: Tool information is being logged in file

/opt/WAS70/profiles/WASHOST1AppSrv01/logs/addNode.log

ADMU0128I: Starting tool with the WASHOST1AppSrv01 profile

CWPKI0308I: Adding signer alias "root" to local keystore

"ClientDefaultTrustStore" with the following SHA digest:

AC:73:16:3C:26:F3:D7:53:2B:DC:08:F8:15:5E:3F:28:14:41:1C:5F

CWPKI0308I: Adding signer alias "datapower" to local keystore

"ClientDefaultTrustStore" with the following SHA digest:

A9:BA:A4:B5:BC:26:2F:5D:2A:80:93:CA:BA:F4:31:05:F2:54:14:17

ADMU0001I: Begin federation of node WASHOST1AppSrv01Node with Deployment

Manager at WASHOST1:8879.

ADMU0009I: Successfully connected to Deployment Manager Server: WASHOST1:8879

ADMU0505I: Servers found in configuration:

ADMU0506I: Server name: server1

ADMU2010I: Stopping all server processes for node WASHOST1AppSrv01Node

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: WASHOST1AppSrv01Node

ADMU0014I: Adding node WASHOST1AppSrv01Node configuration to cell: WASHOST1Cell

ADMU0016I: Synchronizing configuration between node and cell.

ADMU0018I: Launching Node Agent process for node: WASHOST1AppSrv01Node

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:

4486

ADMU0300I: The node WASHOST1AppSrv01Node was successfully added to the

WASHOST1Cell cell.

ADMU0306I: Note:

ADMU0302I: Any cell-level documents from the standalone WASHOST1Cell

configuration have not been migrated to the new cell.

ADMU0307I: You might want to:

ADMU0303I: Update the configuration on the WASHOST1Cell 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 WASHOST1Cell cell using wsadmin

$AdminApp or the Administrative Console.

ADMU0003I: Node WASHOST1AppSrv01Node has been successfully federated.

[wsadm@WASHOST1 ~]$

System administration > Nodes > You should see - Name = WASHOST1AppSrv01Node + Host Name = WASHOST1

Servers > Server Types > WebSphere application servers > you should see Application server Name = Server1

Start Server1 from DMGR:

Servers > Server Types > WebSphere application servers > Select server1 > start > Start few time & start started we should see server1 as green status.

<~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~>

4. Creating managed (custom) profile & federating to DMGR.

Managed Profile templete will not create any application server (JVM), then later we need to create new JVM (say like server1) for that profile.

Also is will not install any "defaultapplication"

[wsadm@WASHOST1 ~]$ /opt/WAS70/bin/manageprofiles.sh -create -templatePath /opt/WAS70/profileTemplates/managed -profileName WASHOST1AppSrv02 -ProfilePath /opt/WAS70/profiles -nodeName WASHOST1AppSrv02Node

INSTCONFSUCCESS: Success: Profile WASHOST1AppSrv02 now exists. Please consult /opt/WAS70/profiles/WASHOST1AppSrv02/logs/AboutThisProfile.txt for more information about this profile.

[wsadm@WASHOST1 ~]$

[wsadm@WASHOST1 manageprofiles]$ tail /opt/WAS70/logs/manageprofiles/WASHOST1AppSrv02_create.log

<logger>com.ibm.wsspi.profile.WSProfileCLI</logger>

<class>com.ibm.wsspi.profile.WSProfileCLI</class>

<method>invokeWSProfile</method>

<message>Returning with return code: INSTCONFSUCCESS</message>

</record>

</log>

[wsadm@WASHOST1 manageprofiles]$

[wsadm@WASHOST1 bin]$ cat /opt/WAS70/profiles/WASHOST1AppSrv02/logs/AboutThisProfile.txt

Application server environment to create: Custom

Location: /opt/WAS70/profiles/WASHOST1AppSrv02

Disk space required: 10 MB

Profile name: WASHOST1AppSrv02

Make this profile the default: False

Node name: WASHOST1AppSrv02Node

Host name: WASHOST1

Federate to deployment manager: False

[wsadm@WASHOST1 bin]$

[wsadm@WASHOST1 bin]$ ./addNode.sh WASHOST1

ADMU0116I: Tool information is being logged in file

/opt/WAS70/profiles/WASHOST1AppSrv02/logs/addNode.log

ADMU0128I: Starting tool with the WASHOST1AppSrv02 profile

CWPKI0308I: Adding signer alias "root" to local keystore

"ClientDefaultTrustStore" with the following SHA digest:

AC:73:16:3C:26:F3:D7:53:2B:DC:08:F8:15:5E:3F:28:14:41:1C:5F

CWPKI0308I: Adding signer alias "datapower" to local keystore

"ClientDefaultTrustStore" with the following SHA digest:

A9:BA:A4:B5:BC:26:2F:5D:2A:80:93:CA:BA:F4:31:05:F2:54:14:17

ADMU0001I: Begin federation of node WASHOST1AppSrv02Node with Deployment

Manager at WASHOST1:8879.

ADMU0009I: Successfully connected to Deployment Manager Server: WASHOST1:8879

ADMU0507I: No servers found in configuration under:

/opt/WAS70/profiles/WASHOST1AppSrv02/config/cells/WASHOST1Node01Cell/nodes/WASHOST1AppSrv02Node/servers

ADMU2010I: Stopping all server processes for node WASHOST1AppSrv02Node

ADMU0024I: Deleting the old backup directory.

ADMU0015I: Backing up the original cell repository.

ADMU0012I: Creating Node Agent configuration for node: WASHOST1AppSrv02Node

ADMU0014I: Adding node WASHOST1AppSrv02Node configuration to cell: WASHOST1Cell

ADMU0016I: Synchronizing configuration between node and cell.

ADMU0018I: Launching Node Agent process for node: WASHOST1AppSrv02Node

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:

4030

ADMU0300I: The node WASHOST1AppSrv02Node was successfully added to the

WASHOST1Cell cell.

ADMU0306I: Note:

ADMU0302I: Any cell-level documents from the standalone WASHOST1Cell

configuration have not been migrated to the new cell.

ADMU0307I: You might want to:

ADMU0303I: Update the configuration on the WASHOST1Cell 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 WASHOST1Cell cell using wsadmin

$AdminApp or the Administrative Console.

ADMU0003I: Node WASHOST1AppSrv02Node has been successfully federated.

[wsadm@WASHOST1 bin]$

<~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~><~>

Saturday, January 9, 2016

03-IBM-WAS7.0 Creating DMGR and standalone profile and federating to DMGR-by Srikant S. Ande

1. Lab setup info

2. Creating DMGR (Management) profile.

3. Creating default (Application server) profile & federating to DMGR.

4. Creating managed (custom) profile & federating to DMGR.

No comments:

Post a Comment

About Me

Blog Archive