WebSphere V8.5 Silent Install upgrade (iii)-command view create delete was profile

Source: Internet
Author: User
Tags websphere application server

"Command to view the built was profile":
/opt/ibm/websphere/appserver/bin/manageprofiles.sh-listprofiles
"Command to delete the was profile":
Programme one:

1. Locate the profileregistry.xml, and in the directory/opt/ibm/websphere/appserver/properties, remove the profile that you want to delete.
2. Delete profilename.sh in directory/opt/ibm/websphere/appserver/properties/fsdb, delete
3. Delete the actual directory and contents of the profile, such as:/OPT/IBM/WEBSPHERE/APPSERVER/PROFILES/APPSRV01


Scenario Two:
To delete a profile:
Was_home/bin/manageprofiles. [Sh|bat]-delete-profilename profile Name
Refresh the Profile registry (for example, after deleting a profile):
Was_home/bin/manageprofiles. [Sh|bat]-validateandupdateregistry
List existing profiles:
Was_home/bin/manageprofiles. [Sh|bat]-listprofiles
Delete Profile Example:
/opt/ibm/websphere/appserver/bin/manageprofiles.sh-delete-profilename APPSRV01
/opt/ibm/websphere/appserver/bin/manageprofiles.sh-delete-profilename Dmgr01
/opt/ibm/websphere/appserver/bin/manageprofiles.sh-validateandupdateregistry

Command Creation Profile: The following cases create dmgr and node on the same host.
Create Dmgr01:
Mode one (do not set the port):
/opt/ibm/websphere/appserver/bin/manageprofiles.sh \
-create \
-templatepath/opt/ibm/websphere/appserver/profiletemplates/dmgr \
-hostname was \
-profilename Dmgr01 \
-profilepath/opt/ibm/websphere/appserver/profiles/dmgr01 \
-cellname wasCell01 \
-nodename wasCellManager01 \
-enableadminsecurity true \
-adminusername wpsadmin \
-adminpassword Passw0rd

Mode two (set port):
Port file _portdef_dmgr.props as follows:
csiv2_ssl_serverauth_listener_address=9403
wc_adminhost=9060
dcs_unicast_address=9352
bootstrap_address=9809
sas_ssl_serverauth_listener_address=9401
CELL_ discovery_address=7277
soap_connector_address=8879
orb_listener_address=9100
Csiv2_ssl_mutualauth_ listener_address=9402
wc_adminhost_secure=9043
Executes the Create DMGR01 command:
/opt/ibm/websphere/appserver/bin/ manageprofiles.sh-create \
-templatepath/opt/ibm/websphere/appserver/profiletemplates/dmgr \
-hostName was\
-profilename Dmgr01 \
-profilepath/opt/ibm/websphere/appserver/profiles/dmgr01 \
-portsfile/opt/ibm/ Websphere/appserver/profiles/_portdef_dmgr.props \
-cellname wasCell01 \
-nodename wasCellManager01 \
- Enableadminsecurity true \
-adminusername wpsadmin \
-adminpassword passw0rd

Create APPSRV01:
Mode One (do not set port):
Federated dmgr:
/opt/ibm/websphere/appserver/bin/manageprofiles.sh \
-create \
-templatepath/opt/ibm/websphere/appserver/profiletemplates/managed \
-hostname was\
-profileName APPSRV01 \
-profilepath/opt/ibm/websphere/appserver/profiles/appsrv01 \
-cellname wasCell02 \
-nodename WASNODE01 \
-dmgrhost 192.168.182.100 \
-dmgrport 8879 \
-dmgradminusername wpsadmin \
-dmgradminpassword Passw0rd
-isdefault

Do not federate dmgr:
/opt/ibm/websphere/appserver/bin/manageprofiles.sh \
-create \
-templatepath/opt/ibm/ websphere/appserver/profiletemplates/managed \
-hostname was\
-profilename AppSrv01 \
-profilepath/opt/ IBM/WEBSPHERE/APPSERVER/PROFILES/APPSRV01 \
-cellname wasCell02 \
-nodename wasNode01 \
- Enableadminsecurity true \
-adminusername wasadmin \
-adminpassword passw0rd \
-isdefault
Then add the node to dmgr with the AddNode command:
/opt/ibm/websphere/appserver/profiles/appsrv01/bin/addnode.sh 192.168.182.100 8879- Username Wpsadmin-password passw0rd

Mode two (set port):
Port file _portdef_appsvr.props as follows:
csiv2_ssl_serverauth_listener_address=9201
Dcs_unicast_ address=9353
node_discovery_address=7272
node_ipv6_multicast_discovery_address=5001
BOOTSTRAP_ADDRESS =2809
sas_ssl_serverauth_listener_address=9901
soap_connector_address=8878
Node_multicast_discovery_ address=5000
orb_listener_address=9101
csiv2_ssl_mutualauth_listener_address=9202
Execute create APPSRV01 command:
Federated Dmgr:
/opt/ibm/websphere/appserver/bin/manageprofiles.sh \
-create \
-templatepath/opt/ibm/websphere/ appserver/profiletemplates/managed \
-hostname was\
-profilename AppSrv01 \
-profilepath/opt/ibm/ WEBSPHERE/APPSERVER/PROFILES/APPSRV01 \
-portsfile/opt/ibm/websphere/appserver/profiles/_portdef_ Appsvr.props \
-cellname wasCell02 \
-nodename wasNode01 \
-dmgrhost 192.168.182.100 \
-dmgrport 8879 \
-dmgradminusername wpsadmin \
-dmgradminpassword passw0rd
-isdefault

Non-Union Dmgr:
/opt/ibm/websphere/appserver/bin/manageprofiles.sh \
-create \
-templatepath/opt/ibm/websphere/appserver/profiletemplates/managed \
-hostname was\
-profilename AppSrv01 \
-PROFILEPATH/OPT/IBM/WEBSPHERE/APPSERVER/PROFILES/APPSRV01 \
-portsfile/opt/ibm/websphere/appserver/profiles/_portdef_appsvr.props \
-cellname wasCell02 \
-nodename wasNode01 \
-enableadminsecurity true \
-adminusername wasadmin \
-adminpassword passw0rd \
-isdefault
Then add the node to dmgr with the AddNode command:
/opt/ibm/websphere/appserver/profiles/appsrv01/bin/addnode.sh 192.168.182.100 8879-username Wpsadmin-password Passw0rd

Issue one: Start Dmgr01 times Java.lang.NoClassDefFoundError:com.ibm.ws.xd.heapdetect.HeapUsageListener
Cause: WebSphere is a non-root deployment that uses root to start the profile after it is created with a un-root account, and this error occurs when you stop using a non-root account to start.
Workaround:
Initialize the instance:
/app/ibm/websphere/appserver/profiles/dmgr01/bin/osgicfginit.sh


Reference Documentation:
Create a WebSphere application Server Network Deployment profile
Https://www.ibm.com/support/knowledgecenter/zh/SSLKT6_7.6.0/com.ibm.mam.inswas.doc/install/t_ccmdb_manconfigj2ee.html
For information on how to switch JDK versions, please refer to:
Https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/rxml_managesdk.html

WebSphere V8.5 Silent Install upgrade (iii)-command view create delete was profile

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.