Date Created: Tue 10-Feb-2009

Related Document Categories:

Get my WebSphere Application Server course here >> http://www.themiddlewareshop.com/products/





 Creating a new profile for use with Application Server toolkit

Let’s say you have RSA or RAD installed, so you have WebSphere runtimes. What you want to be able to do is use application server toolkit to use a profile from you 6.1 runtimes.

Run the PMT tool as located in your runtimes bin directory.

C:\Program Files\IBM\SDP\runtimes\base_v61\bin\ProfileManagement



Click create to start the profile creation wizard



Click Next




Select Application Server


Click Next



Click advanced profile creation so we have more choice during later screens.




Select Admin Console, but you can choose whether you want samples or not.



Select directory that is outside of your runtimes to keep it clean for other RSA projects.




You can override t host to use local host if you wish.



Enter wasadmin/wasadmin or whatever you want for global security, this will secure the administrative console.



Note: If you have other profiles in other runtimes there could be a conflict if you try to run them at the same time.


Next




Do not run as a windows service, this is a real pain. You want control. There is a good article on this site if you require more information about the wasservice tool.

Next

Do not create web-server definition

Next




Read summary and click create.






If you get an error like “Profile creation failed” the consul the logs.

In my case the was found : <was runtime root>\logs\manageprofiles



After looking at the logs they said that the profile already existed.



<level>WARNING</level>
<class>com.ibm.ws.install.configmanager.logging.LogUtils</class>
<method>logException</method>
<thread>10</thread>
<message>The translated exception message is: Cannot create the profile: The profile already exists.</message>
</record>
<record>
<date>2009-02-09T17:24:16</date>
<millis>1234200256956</millis>
<sequence>3368</sequence>
<logger>com.ibm.ws.profile.cli.WSProfileCLICreateProfileInvoker</logger>
<level>WARNING</level>
<class>com.ibm.ws.install.configmanager.logging.LogUtils</class>
<method>logException</method>
<thread>10</thread>
<message>The stack trace follows</message>
</record>
<record>
<date>2009-02-09T17:24:16</date>
<millis>1234200256956</millis>
<sequence>3369</sequence>
<logger>com.ibm.ws.profile.cli.WSProfileCLICreateProfileInvoker</logger>
<level>WARNING</level>
<class>com.ibm.ws.install.configmanager.logging.LogUtils</class>
<method>logException</method>
<thread>10</thread>
<message>com.ibm.wsspi.profile.WSProfileException: Cannot create the profile: The profile already exists.
at com.ibm.ws.profile.registry.ProfileRegistryMarshaller.throwExceptionIfTheGivenProfileIsAlreadyRegistered(ProfileRegistryMarshaller.java:306)
at com.ibm.wsspi.profile.WSProfile.throwExceptionIfTheGivenProfileIsAlreadyRegistered(WSProfile.java:3358)
at com.ibm.wsspi.profile.WSProfile.create(WSProfile.java:195)
at com.ibm.ws.profile.cli.WSProfileCLICreateProfileInvoker.executeWSProfileAccordingToMode(WSProfileCLICreateProfileInvoker.java:86)


So I then used the manageprofiles.bat tool.

C:\Program Files\IBM\SDP\runtimes\base_v61\bin>manageprofiles.bat -help
The available modes are: create, augment, delete, unaugment, deleteAll, listProf
iles, getName, getPath, validateRegistry, validateAndUpdateRegistry, getDefaultN
ame, setDefaultName, backupProfile, restoreProfile, response, help
For detailed help on each mode enter: -<mode> -help. For example, -create -help.



The command I used was –listProfiles, the –delete –profileName AppSrv01 to delete the listed profile.

I have other articles which explain how to create and delete profiles.


One the profile was created I was then able to go into the Application Server Toolkit and create a server definition that used this profile.













If you don’t already have a server runtime pointing to the RSA runtime you can change it to point to the correct base binaries.









Lets say we have done this before then we choose the runtime we want.





This will ensure that you can select the appropriate profiles that re linked to that runtime. We can now see our new AppSrv01 profile



Click Finish and the server will be created





Right-mouse click on the server to restart the WAS server to test it works. You can now run a jython project against this server.









The first time you try to run your jython you will be asked to configure which server you are going to run the script on.







We can no login to the admin console and see the J2C Authentication Data and our new alias will be listed





Get my WebSphere Application Server course here >> http://www.themiddlewareshop.com/products/


Steve Robinson - IBM Champion 2013

About Me

Steve Robinson has been working in IT for over 20 years and has provided solutions for many large-enterprise corporate companies across the world. Steve specialises in Java and Middleware.

In January 2013, I was awarded the prestigous 'IBM Champion' accolade.


  • Linked In
  • Twitter
  • About Me
  • My Blog
  • Contact Me

Read my books?

IBM WebSphere Application Server 8.0 Administration Guide

IBM WebSphere Application Server 8.0 Administration Guide

WebSphere Application Server 7.0 Administration Guide

WebSphere Application Server 7.0 Administration Guide

WebSphere Categories

Other Categories