WebSphere wasprofile.sh Use

Profiles (Profile)

Profile is only available after version 6.0, which is designed to separate the user data from the files of the was itself, so that multiple profiles can be defined, each of which is equivalent to one user, which is equivalent to providing multi-user support.

The command description for profile:

New:

Wasprofile.sh-create
-profilename profile_name
-profilepath Fully_qualified_profile_path
-templatepath Template_path
-nodename Node_name
-cellname Cell_name
-hostname host_name
-server Iseries_server_name
[-startingport Starting_port |-portsfile filepath]
-winservicecheck true | False
-winserviceaccounttype Specifieduser | LocalSystem
-winserviceusername YourUserName
-winservicepassword YourPassword
-winservicestartuptype Manual | Automatic | Disabled
[-debug]

To list existing profiles:

#./wasprofile.sh-listprofiles

To delete a profile:

#./wasprofile.sh-delete
-profilename Profile_name | -profilepath Profile_path
[-debug]

Get the name of an existing profile from the path:
#./wasprofile.sh-getname
-profilepath Profile_path
[-debug]

Get the path to the existing profile from the name:
#./wasprofile.sh-getpath
-profilename profile_name
[-debug]

Check the integrity of your profile registry:
#./wasprofile.sh-validateregistry
[-debug]

Check the integrity of the profile registry, removing the profile that was not found:
#./wasprofile.sh-validateandupdateregistry
[-backup file_name]
[-debug]

Example:

./wasprofile.sh \
-create-profilename test4sop \
-PROFILEPATH/WEBSPHERE/APPSERVER/PROFILES/TEST4SOP \
-templatepath/websphere/appserver/profiletemplates/default \
-nodename test4sopnode \
-cellname Test4sopcell \
-hostname S2_E_YZ_JKCS

./wasprofile.sh-delete-profilename Test4sop

Cluster Profile:
If the application is relatively simple, only one server is required, after creating a default profile, you can then do the application deployment on the console.



When the application is more complex, the cluster needs to be built, and the cluster profile differs from the common point.
The difference is:
-templatepath/websphere/appserver/profiletemplates/default \
If the parameter is default, the description is normal single server,
If it is managed, it means that the profile is managed.
If it is dmgr, it indicates that the profile is of type DM (Deployment Manager).
Adding managed profile to Dmgr management requires a command:
./addmode.sh IP (DM IP) 8879 (if not changed)
To move out of a command:
./removenode.sh
After the start of DM and node, you can do cluster construction on the console, such as the operation, the console address is the DM address, the port default is 9060.

2.cell,node,server
The cell is a grouping concept and there can be more than one node under the cell.
node is a grouping of one or a group of servers. Node cannot cross a physical machine. There can be more than one server under a node.
The server is the actual processing unit, and a server is aThe Java EE container.
node and profile are similar, basically equivalent, but node is used in management, and profiles are the basis of the configuration, and one is the equivalent of a node.
The DM is managed by the node agent for each server instance.

WebSphere wasprofile.sh Use