WAS non-root user scheme

1.1.1    Create users and groups

1, Now we log in with the root user and create users and groups. Now create a user  wasadmin belonging to the group  wasgroup 

 

create user

 Enter useradd wasadmin   in the terminal to create a password  passwd 1234rewq

 

useradd user1 ; echo "password1" | passwd --stdin user1

Create group

Type groupadd wasgroup   then usermod -g wasgroup wasadmin

1.1.2    Process execution settings

a), start Deployment Manager as root user

run ./startManager

b)  Enter the was management console for example: http://10.10.10.22:9060/admin

 

 1. Set up DM

 Enter " System Management "->" Deployment Manager "->java Process Management "- > " Process Definition "->" Process Execution "->" Other Properties / Process Execution " , change the " General properties" to fill in:

Run as user: wasadmin

Run as group: wasgroup

 

2, Set up Node Agent

Go to Node Agent > nodeagent >  Process Definition  >  Process Execution

Same as above

Run as user: wasadmin

Run as group: wasgroup

 

3, set up Server1

Enter

Application Server  > server1 >  Process Definition  >  Process Execution

Revise

Run as user: wasadmin

Run as group: wasgroup

 

d) .save configuration and sync 

 

 

Enter the websphere installation directory

/usr/IBM/WebSphere/AppServer/profiles

 

Modify the permissions of the user group to which the websphere directory belongs

 

Modify owning users and groups

Execute as root 

[root@localhost profiles]# chown -R wasadmin.wasgroup Dmgr1/

[root@localhost profiles]# chown -R wasadmin.wasgroup AppSrv01/

As shown above, modify the AppSrv01  and  Dmgr1  directories and subdirectories to the user wasadmin  group  wasgroup

start DM

Su  to the wasadmin user

[root@localhost profiles]# su - wasadmin

[wasadmin@localhost bin]$ ./startManager.sh

 

Started successfully

 

 

 

Guess you like

Origin http://10.200.1.11:23101/article/api/json?id=326721408&siteId=291194637