Creating application server profiles
Create an application server profile so that you can make applications available to the Internet or to an intranet, typically using Java™ technology. You can create an application server profile using the Profile Management Tool.
Before you begin
Before you use the Profile Management Tool, install the product files.
The Profile Management Tool is the graphical user interface for the manageprofiles command. See the description of the manageprofiles command for more information.
You must provide enough system temporary space to create a profile. For information, read about the file system requirements for profiles.
Eclipse*spacing:0
Eclipse*fontList:-misc-fixed-medium-r-normal-*-10-100-75-75-c-60-iso8859-1
After
adding the lines, run the following command before launching the Profile Management Tool:
xrdb -load user_home/.Xdefaults
About this task
After installing the core product files for the WebSphere® Application Server Network Deployment product, you must create a profile. This procedure describes creating an application server profile using the graphical user interface provided by the Profile Management Tool. You can also use the manageprofiles command to create an application server profile. See the description of the manageprofiles command for more information.
An application server profile has a default server, which is server1, and the default application that includes the Snoop servlet and the Hitcount servlet. You can federate the application server or use it as a standalone application server.
You can create profiles with the Profile Management Tool using the typical profile creation process or the advanced profile creation process. The typical profile creation process uses default settings and assigns unique port values. You can optionally set values as allowed. For the advanced profile creation process you can accept the default values, or specify your own values.
Procedure
Results
You created an application server profile. The node within the profile has an application server named server1.
Refer to the description of the manageprofiles command to learn about creating a profile using a command instead of the Profile Management Tool.
What to do next
Deploy an application to get started.
Read about fast paths for the product to get started deploying applications.
When you create the application server profile, a default server1 process is created. You can federate the server1 node into the deployment manager cell with the addNode command or from the administrative console of the deployment manager. The server1 process must be running to begin the federation from the deployment manager.
If you include all of the applications from the application server, then the act of federation installs the applications on the deployment manager where they can be redeployed.