How to Create a Profile in WebSphere ND?

Creating a profile in IBM WebSphere is an initial step to setup the application environment.  Knowing the procedure is essential for WebSphere administrator.

In this post, I’ll explain how to create a profile in IBM WebSphere Application Server Network Deployment.

This assumes you’ve installed the IBM WAS in Linux environment.

Before jumping into profile creation, let’s understand what is a profile in IBM WAS?

The profile is a complete runtime environment which combines the WAS binary and Profile (User data/configuration).

There are multiple types of profile available in WebSphere.

• Cell – a combination of DMGR and federated application server
• Standalone
• Management
• Custom profile

You can create a WebSphere Application Server profile in two ways.

1. GUI – using Profile Management Tool
2. Silent – using manageprofile.sh script

In this post, will use GUI to create a Cell profile.

• Login to server where WAS is installed
• Go to WAS binary location >> bin >> ProfileManagement (in default installation location, it will be /opt/IBM/WebSphere/AppServer/bin/ProfileManagement)
• Launch Profile Management Tool

./pmt.sh

• It will open a “WebSphere Customization Toolbox” window, click Create

• Select “Cell” environment and click Next

In next screen, you will have the option to select the profile creation process. There are two processes.

1. Typical profile creation – profile will be created with the default configuration and port numbers. In most of the cases, you can select this.
2. Advanced profile creation – If you are looking to customize the default ports, configuration then you will need to use this.

• Let’s proceed with “Typical” profile creation, click Next
•  Enter the user and password for DMGR, if you don’t want DMGR to be password protected then you can uncheck the “Enable administrative security” box.

•  Review the profile summary and click “Create”. If you want you can copy the information from this screen as it will contain a lot of useful information like.

Location
Profile name
Cell name
Node name
Ports
Profile type

•  It will take few minutes for profile creation and once done, you should see a confirmation.

If you notice, I’ve kept default option “Launch the First steps console” in above screen.

This will open first steps wizard where you can verify the installation. Verification is essential so you know your profile is functional and ready to deploy the necessary application for your business.

•  Click “Installation verification”

The verification process involves starting and stopping the DMGR and you should see something like below.

Server name is:dmgr
Profile name is:Dmgr01
Profile home is:/opt/IBM/WebSphere/AppServer/profiles/Dmgr01
Profile type is:dmgr
Cell name is:localhostCell01
Node name is:localhostCellManager01
Current encoding is:UTF-8
Start running the following command:/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/startManager.sh -profileName Dmgr01
>ADMU0116I: Tool information is being logged in file
>           /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr/startServer.log
>ADMU0128I: Starting tool with the Dmgr01 profile
>ADMU3100I: Reading configuration for server: dmgr
>ADMU3200I: Server launched. Waiting for initialization status.
>ADMU3000I: Server dmgr open for e-business; process id is 32013
Server port number is:9060
IVTL0010I: Connecting to the localhost WebSphere Application Server on port: 9060
IVTL0015I: WebSphere Application Server localhost is running on port: 9060 for profile Dmgr01
IVTL0035I: The Installation Verification Tool is scanning the /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr/SystemOut.log file for errors and warnings.
[11/20/16 4:53:38:556 PST] 00000001 WSKeyStore    W   CWPKI0041W: One or more key stores are using the default password.
[11/20/16 4:53:47:225 PST] 00000001 HostNameMap   W   HMGR0064W: Resolution of IP Addresses for host name localhost found only the loopback address. The loopback address will be used.
[11/20/16 4:53:53:571 PST] 00000001 SibMessage    W   [:] CWSJY0003W: MQJCA5001: WMQ messaging : '9.0.0.0-p900-L160509.1'.
[11/20/16 4:53:55:298 PST] 0000007a AuthConfigFac W   SECJ8032W: AuthConfigFactory implementation is not defined, using the default JASPI factory implementation class: com.ibm.ws.security.jaspi.ProviderRegistry.
[11/20/16 4:54:00:239 PST] 00000078 AbstractInjec W   CWNEN0070W: The javax.ws.rs.HeaderParam annotation class will not be recognized because it was loaded from the file:/opt/IBM/WebSphere/AppServer/systemApps/isclite.ear/kc.war/WEB-INF/lib/jsr311-api-1.1.1.jar location rather than from a product class loader.
[11/20/16 4:54:00:242 PST] 00000078 AbstractInjec W   CWNEN0070W: The javax.ws.rs.MatrixParam annotation class will not be recognized because it was loaded from the file:/opt/IBM/WebSphere/AppServer/systemApps/isclite.ear/kc.war/WEB-INF/lib/jsr311-api-1.1.1.jar location rather than from a product class loader.
[11/20/16 4:54:00:243 PST] 00000078 AbstractInjec W   CWNEN0070W: The javax.ws.rs.core.Context annotation class will not be recognized because it was loaded from the file:/opt/IBM/WebSphere/AppServer/systemApps/isclite.ear/kc.war/WEB-INF/lib/jsr311-api-1.1.1.jar location rather than from a product class loader.
[11/20/16 4:54:00:244 PST] 00000078 AbstractInjec W   CWNEN0070W: The javax.ws.rs.CookieParam annotation class will not be recognized because it was loaded from the file:/opt/IBM/WebSphere/AppServer/systemApps/isclite.ear/kc.war/WEB-INF/lib/jsr311-api-1.1.1.jar location rather than from a product class loader.
[11/20/16 4:54:00:245 PST] 00000078 AbstractInjec W   CWNEN0070W: The javax.ws.rs.PathParam annotation class will not be recognized because it was loaded from the file:/opt/IBM/WebSphere/AppServer/systemApps/isclite.ear/kc.war/WEB-INF/lib/jsr311-api-1.1.1.jar location rather than from a product class loader.
[11/20/16 4:54:00:246 PST] 00000078 AbstractInjec W   CWNEN0070W: The javax.ws.rs.QueryParam annotation class will not be recognized because it was loaded from the file:/opt/IBM/WebSphere/AppServer/systemApps/isclite.ear/kc.war/WEB-INF/lib/jsr311-api-1.1.1.jar location rather than from a product class loader.
[11/20/16 4:54:02:982 PST] 00000001 TcpTransport  W   ADMD0025W: In process discovery, the 127.0.0.1 IP address is used to advertise an endpoint. This usage might cause problems in a network environment.
[11/20/16 4:54:03:213 PST] 00000051 FfdcProvider  W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/ffdc/dmgr_917750c5_16.11.20_04.54.03.0579098089159114197997.txt com.ibm.ws.management.discovery.DiscoveryService.sendQuery 189
IVTL0040I: 12 errors/warnings are detected in the /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr/SystemOut.log file
IVTL0070I: The Installation Verification Tool verification succeeded.
IVTL0080I: The installation verification is complete.

This concludes profile is created successfully.

Let’s try to access the DMGR URL

Well done! you’ve created a cell environment profile and ready for you to deploy an application and do the necessary configuration.

I hope this is useful to a WebSphere Administrator. Let me know what you think.