Topic
  • 8 replies
  • Latest Post - ‏2011-07-27T13:55:14Z by Scott Johnston
CGBT_SHIVANSH_RASTOGI
5 Posts

Pinned topic How to install WAS 8 on 64 bit Solaris 10 after successfully installation

‏2011-07-19T07:36:32Z |
Hi

I have installed Installation Manager for WAS 8 on Solaris (by running ./install), however I don't see profiles folder under appserver, as I need to configure the WAS further and verify the setup by deploying a WAR file.

Please guide me how to go about domain/profile creation as the installation manager compelted installing and unpacking WAS packages and did not specify any link for domain/profile creation.

Please let me know from where can I resume WAS installation, Domain/profile creation.
Thanks

Shivansh Rastogi
+91 770 974 22 00
Updated on 2011-07-27T13:55:14Z at 2011-07-27T13:55:14Z by Scott Johnston
  • Scott Johnston
    Scott Johnston
    101 Posts

    Re: How to install WAS 8 on 64 bit Solaris 10 after successfully installation

    ‏2011-07-20T20:46:15Z  
    In version 8, WebSphere Application Server changed the installation technology to use IBM Installation Manager. That change brought with it a clean separation between installation and configuration processes. That is, there are discretely separate processes for getting the product installed and then configuring application servers. This separation of processes is beneficial for a number of reasons, such as facilitating problem determination.

    The initial installation to a clean system is a two-step process. The first step is to install IBM Installation Manager. This step only has to be done once per machine. After Installation Manager is on the system, it can be used to install and update many different IBM products or install the same product one or more times to the same machine.

    Based on the information provided, it seems that the first step of the installation process is complete. For others who might need the information, here is a link to the information center article that provides an overview of installing IBM Installation Manager to your system.

    > Installing and Uninstalling the product on distributed systems:
    > http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.installation.nd.doc/info/ae/ae/tins_installation_dist.html

    The second installation step is to use Installation Manager to install WebSphere Application Server to the system. Run Installation Manager in either graphical (GUI) mode or using the command line tool (imcl) with a response file to install WebSphere Application Server. The following two Information Center article begin with steps for installing Installation Manager, and then continues with detailed steps for installing WebSphere Application Server using either the GUI or imcl.

    > Installing the product on distributed systems using the GUI:
    > http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.installation.nd.doc/info/ae/ae/tins_installation_dist_gui.html

    > Installing the product on distributed systems silently:
    > http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.installation.nd.doc/info/ae/ae/tins_installation_dist_silent.html

    After Installation Manager installs the WebSphere Application Server code to the system, the installation phase is complete. The next phase is configuring WebSphere Application Server by creating a profile. Similar to installation, profile creation can be done using either a graphical or a command line tool. The following article provides an overview of profile creation:

    > Configuring the product after installation
    > http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.installation.nd.doc/info/ae/ae/tins_configpostinstall.html

    The graphical tool is called the Profile Management Tool (PMT), which is housed in the WebSphere Customization Toolbox (WCT). The WCT is installed automatically with the WebSphere Application Server code. Note that there is a separate stand-alone WCT that houses a Profile Management Tool for z/OS. This version of the tool is not needed for distributed systems because it only creates jobs for managing profile in WebSphere Application Server for z/OS systems. Launch WCT and then choose to run the PMT. From the PMT, choose to create a profile and then step through the wizard to complete the process. The following Information Center article describes the profile creation process, and there are several additional articles that detail the process for each type of profile that can be created:

    > Managing profiles using the graphical user interface:
    > http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.installation.nd.doc/info/ae/ae/tpro_instances.html

    Alternatively, profiles can be created using the command line tool: manageprofiles.bat / manageprofile.sh

    > Managing profiles using commands:
    > http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.installation.nd.doc/info/ae/ae/tpro_setup.html

    > The manageprofiles commands
    > http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.installation.nd.doc/info/ae/ae/rxml_manageprofiles.html

    After one or more profiles are created, you can start up the application server and deploy your WAR files.

    If you encounter issues completing any of the steps above for installing the product or creating profiles, then let us know which one of the processes (product installation or profile creation) has the issue and then describe the issue.
    Regards,
    Scott Johnston
    WebSphere Application Server
    Install & Configuration User Experience Lead
  • CGBT_SHIVANSH_RASTOGI
    5 Posts

    Re: How to install WAS 8 on 64 bit Solaris 10 after successfully installation

    ‏2011-07-21T09:43:41Z  
    In version 8, WebSphere Application Server changed the installation technology to use IBM Installation Manager. That change brought with it a clean separation between installation and configuration processes. That is, there are discretely separate processes for getting the product installed and then configuring application servers. This separation of processes is beneficial for a number of reasons, such as facilitating problem determination.

    The initial installation to a clean system is a two-step process. The first step is to install IBM Installation Manager. This step only has to be done once per machine. After Installation Manager is on the system, it can be used to install and update many different IBM products or install the same product one or more times to the same machine.

    Based on the information provided, it seems that the first step of the installation process is complete. For others who might need the information, here is a link to the information center article that provides an overview of installing IBM Installation Manager to your system.

    > Installing and Uninstalling the product on distributed systems:
    > http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.installation.nd.doc/info/ae/ae/tins_installation_dist.html

    The second installation step is to use Installation Manager to install WebSphere Application Server to the system. Run Installation Manager in either graphical (GUI) mode or using the command line tool (imcl) with a response file to install WebSphere Application Server. The following two Information Center article begin with steps for installing Installation Manager, and then continues with detailed steps for installing WebSphere Application Server using either the GUI or imcl.

    > Installing the product on distributed systems using the GUI:
    > http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.installation.nd.doc/info/ae/ae/tins_installation_dist_gui.html

    > Installing the product on distributed systems silently:
    > http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.installation.nd.doc/info/ae/ae/tins_installation_dist_silent.html

    After Installation Manager installs the WebSphere Application Server code to the system, the installation phase is complete. The next phase is configuring WebSphere Application Server by creating a profile. Similar to installation, profile creation can be done using either a graphical or a command line tool. The following article provides an overview of profile creation:

    > Configuring the product after installation
    > http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.installation.nd.doc/info/ae/ae/tins_configpostinstall.html

    The graphical tool is called the Profile Management Tool (PMT), which is housed in the WebSphere Customization Toolbox (WCT). The WCT is installed automatically with the WebSphere Application Server code. Note that there is a separate stand-alone WCT that houses a Profile Management Tool for z/OS. This version of the tool is not needed for distributed systems because it only creates jobs for managing profile in WebSphere Application Server for z/OS systems. Launch WCT and then choose to run the PMT. From the PMT, choose to create a profile and then step through the wizard to complete the process. The following Information Center article describes the profile creation process, and there are several additional articles that detail the process for each type of profile that can be created:

    > Managing profiles using the graphical user interface:
    > http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.installation.nd.doc/info/ae/ae/tpro_instances.html

    Alternatively, profiles can be created using the command line tool: manageprofiles.bat / manageprofile.sh

    > Managing profiles using commands:
    > http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.installation.nd.doc/info/ae/ae/tpro_setup.html

    > The manageprofiles commands
    > http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.installation.nd.doc/info/ae/ae/rxml_manageprofiles.html

    After one or more profiles are created, you can start up the application server and deploy your WAR files.

    If you encounter issues completing any of the steps above for installing the product or creating profiles, then let us know which one of the processes (product installation or profile creation) has the issue and then describe the issue.
    Regards,
    Scott Johnston
    WebSphere Application Server
    Install & Configuration User Experience Lead
    Thanks Scott for the detailed explainantion.

    However when I tried installing the WAS code through installation manager as per the instructions given here:

    http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=%2Fcom.ibm.websphere.installation.nd.doc%2Finfo%2Fae%2Fae%2Ftins_installation_dist_gui.html

    Upon checking connect to passport advantage I get the message:

    IBM Passport advantage does not contain active entitlements for IBM Installation manager enabled offerings
    And the process halts there, Can you let me know what is being referred here and how can I get the active entitlement to begin WAS installation from the ibm repository.

    Regards
    Shivansh
  • Scott Johnston
    Scott Johnston
    101 Posts

    Re: How to install WAS 8 on 64 bit Solaris 10 after successfully installation

    ‏2011-07-21T15:56:26Z  
    Thanks Scott for the detailed explainantion.

    However when I tried installing the WAS code through installation manager as per the instructions given here:

    http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=%2Fcom.ibm.websphere.installation.nd.doc%2Finfo%2Fae%2Fae%2Ftins_installation_dist_gui.html

    Upon checking connect to passport advantage I get the message:

    IBM Passport advantage does not contain active entitlements for IBM Installation manager enabled offerings
    And the process halts there, Can you let me know what is being referred here and how can I get the active entitlement to begin WAS installation from the ibm repository.

    Regards
    Shivansh
    The short answer is that the credentials Installation Manager requests to install the trial products are your IBM.com credentials; the same user name and password that you use to log into this developerWorks forum or that you provided when you downloaded Installation Manager (hint: the user name usually is an email address).

    The Information Center article describes the process for installing the purchased and fully licensed versions of the product rather than the trial version. IBM Passport Advantage is not used to install the trial version.

    If your business purchased a WebSphere Application Server v8.0 solution and you do not know or have Passport Advantage credentials, then contact your IBM representative to assist you. Issues using Passport Advantage go beyond the scope of this forum.

    To install a trial version of WebSphere Application Server, first launch Installation Manager and check the preferences. Look in the Repositories area and you should see a repository location listed that looks something like this:

    http://www.ibm.com/software/repositorymanager/XXX

    ...where XXX is a version and short name for the trial product code repository, such as V8WASBASETrial is the name for the WebSphere Application Server v8.0 trial. If the repository is not listed, then use the Add Repository dialog to manually add the repository location. When adding the repository, you will be prompted for your IBM download site credentials. The user name and password that are being requested are your IBM.com credentials, the same ones you use to log into this developerWorks support forum. If the credentials are incorrect, you will be told that they are invalid and given a chance to enter your IBM ID and password again.

    Additional WebSphere v8.0 product repositories can be added by looking in the "More downloads" section of the WebSphere Trials webpage:
    http://www.ibm.com/developerworks/downloads/ws/was/index.html

    For instance, to add the IBM HTTP Server v8, click on the link. You might be prompted for your IBM credentials again. Afterwards, you will go to a page to download IBM Installation Manager again. Download and start the installation again. Because Installation Manager is already installed, the installation will only update the repository list to include the IBM HTTP Server repository.

    After making sure there is one or more product repositories listed, then you can exit the preferences section.

    From the Installation Manager launchpad, click the Install icon to launch the installation wizard. Installation Manager immediately scans the list of repositories in its preferences and then connects to each of them in the same order they are listed. When it tries to connect to the WebSphere trials repository for the first time, you will be prompted for your IBM download site credentials. The user name and password that are being requested are your IBM.com credentials, the same ones you use to log into this developerWorks support forum. You will only be prompted for these credentials one time while interacting with Installation Manager. If you close then restart Installation Manager, you will have to reauthenticate with the remote repository again unless you check the checkbox to save the password.

    After authenticating successfully, Installation Manager will display a list of products that are in the repositories. Select the ones you want to install and follow the wizard to choose where to install each of them and the features to include.

    Regards,
    Scott Johnston
    WebSphere Application Server
    Install & Configuration User Experience Lead
  • CGBT_SHIVANSH_RASTOGI
    5 Posts

    Re: How to install WAS 8 on 64 bit Solaris 10 after successfully installation

    ‏2011-07-22T10:46:20Z  
    The short answer is that the credentials Installation Manager requests to install the trial products are your IBM.com credentials; the same user name and password that you use to log into this developerWorks forum or that you provided when you downloaded Installation Manager (hint: the user name usually is an email address).

    The Information Center article describes the process for installing the purchased and fully licensed versions of the product rather than the trial version. IBM Passport Advantage is not used to install the trial version.

    If your business purchased a WebSphere Application Server v8.0 solution and you do not know or have Passport Advantage credentials, then contact your IBM representative to assist you. Issues using Passport Advantage go beyond the scope of this forum.

    To install a trial version of WebSphere Application Server, first launch Installation Manager and check the preferences. Look in the Repositories area and you should see a repository location listed that looks something like this:

    http://www.ibm.com/software/repositorymanager/XXX

    ...where XXX is a version and short name for the trial product code repository, such as V8WASBASETrial is the name for the WebSphere Application Server v8.0 trial. If the repository is not listed, then use the Add Repository dialog to manually add the repository location. When adding the repository, you will be prompted for your IBM download site credentials. The user name and password that are being requested are your IBM.com credentials, the same ones you use to log into this developerWorks support forum. If the credentials are incorrect, you will be told that they are invalid and given a chance to enter your IBM ID and password again.

    Additional WebSphere v8.0 product repositories can be added by looking in the "More downloads" section of the WebSphere Trials webpage:
    http://www.ibm.com/developerworks/downloads/ws/was/index.html

    For instance, to add the IBM HTTP Server v8, click on the link. You might be prompted for your IBM credentials again. Afterwards, you will go to a page to download IBM Installation Manager again. Download and start the installation again. Because Installation Manager is already installed, the installation will only update the repository list to include the IBM HTTP Server repository.

    After making sure there is one or more product repositories listed, then you can exit the preferences section.

    From the Installation Manager launchpad, click the Install icon to launch the installation wizard. Installation Manager immediately scans the list of repositories in its preferences and then connects to each of them in the same order they are listed. When it tries to connect to the WebSphere trials repository for the first time, you will be prompted for your IBM download site credentials. The user name and password that are being requested are your IBM.com credentials, the same ones you use to log into this developerWorks support forum. You will only be prompted for these credentials one time while interacting with Installation Manager. If you close then restart Installation Manager, you will have to reauthenticate with the remote repository again unless you check the checkbox to save the password.

    After authenticating successfully, Installation Manager will display a list of products that are in the repositories. Select the ones you want to install and follow the wizard to choose where to install each of them and the features to include.

    Regards,
    Scott Johnston
    WebSphere Application Server
    Install & Configuration User Experience Lead
    Hi Scott

    Since its a trial version I tried running:

    bash-3.00# ./firststeps.sh
    ./firststeps.sh: /opt/IBM/WebSphere/AppServer/properties/version/install/bin/sdk /_setupSdk.sh: not found

    I found that directory structure (bin folder) itself is missing:
    bash-3.00# cd /opt/IBM/WebSphere/AppServer/properties/version/install/
    bash-3.00# ls
    firststeps

    > further I do not see prfoiles folder here and even profile management tool could not be started as there is no such directory or script:
    Can you please suggest from the files seen below if the installation of WAS 8 was upto the mark as I did get a successful message in the end, however there was no mention to start the profile management tool in that window but finished button.

    bash-3.00# pwd
    /opt/IBM/WebSphere/AppServer
    bash-3.00# ls -alrt
    total 298
    drwxr-xr-x 2 root root 20 Jul 18 16:59 lafiles
    drwxr-xr-x 9 root root 15 Jul 18 17:01 java
    drwxr-xr-x 2 root root 3 Jul 18 17:01 uninstall
    drwxr-xr-x 3 root root 5 Jul 18 17:01 instutils
    drwxr-xr-x 4 root root 4 Jul 18 17:04 profileTemplates
    drwxr-xr-x 5 root root 5 Jul 18 17:04 web
    drwxr-xr-x 4 root root 4 Jul 18 17:04 installedConnectors
    drwxr-xr-x 2 root root 18 Jul 18 17:05 sar2war_tool
    drwxr-xr-x 3 root root 3 Jul 18 17:05 firststeps
    drwxr-xr-x 7 root root 7 Jul 18 17:05 UDDIReg
    drwxr-xr-x 2 root root 3 Jul 18 17:05 temp
    drwxr-xr-x 2 root root 25 Jul 18 17:06 installableApps
    drwxr-xr-x 6 root root 7 Jul 18 17:06 derby
    drwxr-xr-x 3 root root 3 Jul 18 17:06 universalDriver
    drwxr-xr-x 2 root root 38 Jul 18 17:06 Scheduler
    drwxr-xr-x 3 root root 3 Jul 18 17:06 tivoli
    drwxr-xr-x 2 root root 5 Jul 18 17:07 endorsed_apis
    drwxr-xr-x 6 root root 7 Jul 18 17:07 etc
    drwxr-xr-x 2 root root 3 Jul 18 17:07 links
    drwxr-xr-x 4 root root 4 Jul 18 17:11 deploytool
    drwxr-xr-x 3 root root 3 Jul 18 17:13 samples
    drwxr-xr-x 6 root root 6 Jul 18 17:13 optionalLibraries
    drwxr-xr-x 6 root root 7 Jul 18 17:13 dev
    drwxr-xr-x 10 root root 10 Jul 18 17:14 scriptLibraries
    drwxr-xr-x 16 root root 16 Jul 18 17:14 features
    drwxr-xr-x 5 root root 20 Jul 18 17:14 util
    drwxr-xr-x 17 root root 17 Jul 18 17:14 systemApps
    drwxr-xr-x 8 root root 144 Jul 18 17:14 bin
    drwxr-xr-x 4 root root 20 Jul 18 17:24 runtimes
    drwxr-xr-x 5 root root 212 Jul 18 17:24 plugins
    drwxr-xr-x 6 root root 48 Jul 18 17:24 lib
    drwxr-xr-x 3 root root 3 Jul 18 17:25 logs
    drwxr-xr-x 17 root root 47 Jul 18 17:25 properties
    drwxr-xr-x 6 root root 8 Jul 19 13:52 configuration
    drwxr-xr-x 4 root root 4 Jul 22 10:40 ..
    drwxr-xr-x 36 root root 36 Jul 22 12:37 .
  • SystemAdmin
    SystemAdmin
    64 Posts

    Re: How to install WAS 8 on 64 bit Solaris 10 after successfully installation

    ‏2011-07-22T18:05:55Z  
    Hi Scott

    Since its a trial version I tried running:

    bash-3.00# ./firststeps.sh
    ./firststeps.sh: /opt/IBM/WebSphere/AppServer/properties/version/install/bin/sdk /_setupSdk.sh: not found

    I found that directory structure (bin folder) itself is missing:
    bash-3.00# cd /opt/IBM/WebSphere/AppServer/properties/version/install/
    bash-3.00# ls
    firststeps

    > further I do not see prfoiles folder here and even profile management tool could not be started as there is no such directory or script:
    Can you please suggest from the files seen below if the installation of WAS 8 was upto the mark as I did get a successful message in the end, however there was no mention to start the profile management tool in that window but finished button.

    bash-3.00# pwd
    /opt/IBM/WebSphere/AppServer
    bash-3.00# ls -alrt
    total 298
    drwxr-xr-x 2 root root 20 Jul 18 16:59 lafiles
    drwxr-xr-x 9 root root 15 Jul 18 17:01 java
    drwxr-xr-x 2 root root 3 Jul 18 17:01 uninstall
    drwxr-xr-x 3 root root 5 Jul 18 17:01 instutils
    drwxr-xr-x 4 root root 4 Jul 18 17:04 profileTemplates
    drwxr-xr-x 5 root root 5 Jul 18 17:04 web
    drwxr-xr-x 4 root root 4 Jul 18 17:04 installedConnectors
    drwxr-xr-x 2 root root 18 Jul 18 17:05 sar2war_tool
    drwxr-xr-x 3 root root 3 Jul 18 17:05 firststeps
    drwxr-xr-x 7 root root 7 Jul 18 17:05 UDDIReg
    drwxr-xr-x 2 root root 3 Jul 18 17:05 temp
    drwxr-xr-x 2 root root 25 Jul 18 17:06 installableApps
    drwxr-xr-x 6 root root 7 Jul 18 17:06 derby
    drwxr-xr-x 3 root root 3 Jul 18 17:06 universalDriver
    drwxr-xr-x 2 root root 38 Jul 18 17:06 Scheduler
    drwxr-xr-x 3 root root 3 Jul 18 17:06 tivoli
    drwxr-xr-x 2 root root 5 Jul 18 17:07 endorsed_apis
    drwxr-xr-x 6 root root 7 Jul 18 17:07 etc
    drwxr-xr-x 2 root root 3 Jul 18 17:07 links
    drwxr-xr-x 4 root root 4 Jul 18 17:11 deploytool
    drwxr-xr-x 3 root root 3 Jul 18 17:13 samples
    drwxr-xr-x 6 root root 6 Jul 18 17:13 optionalLibraries
    drwxr-xr-x 6 root root 7 Jul 18 17:13 dev
    drwxr-xr-x 10 root root 10 Jul 18 17:14 scriptLibraries
    drwxr-xr-x 16 root root 16 Jul 18 17:14 features
    drwxr-xr-x 5 root root 20 Jul 18 17:14 util
    drwxr-xr-x 17 root root 17 Jul 18 17:14 systemApps
    drwxr-xr-x 8 root root 144 Jul 18 17:14 bin
    drwxr-xr-x 4 root root 20 Jul 18 17:24 runtimes
    drwxr-xr-x 5 root root 212 Jul 18 17:24 plugins
    drwxr-xr-x 6 root root 48 Jul 18 17:24 lib
    drwxr-xr-x 3 root root 3 Jul 18 17:25 logs
    drwxr-xr-x 17 root root 47 Jul 18 17:25 properties
    drwxr-xr-x 6 root root 8 Jul 19 13:52 configuration
    drwxr-xr-x 4 root root 4 Jul 22 10:40 ..
    drwxr-xr-x 36 root root 36 Jul 22 12:37 .
    A First Steps console is created during profile creation and is specific to the profile that is created because different types of profiles have different options available.

    So, let's back up a step to getting a profile created.

    If the option to launch the Profile Management Tool (PMT) is not selected at the end of installation or silent installation was performed, then the PMT has to be launched manually. If your operating system is Windows or some flavors of Linux, let there are shortcuts available to launch the graphical PMT. For other supported operating systems, the graphical PMT can be launched from the command line.

    Navigate to the location where WebSphere Application Server is installed, then into the following directory:
    <WAS_Install_Directory>/bin/ProfileManagment/
    ... and then run pmt.sh or pmt.bat, whichever is appropriate for your operating system.

    This will start up the PMT. Next, click Create... to start the profile creation wizard.

    Alternatively, profiles can be created with the command line tool called manageprofiles, which is located in the bin directory:
    <WAS_Install_Directory>/bin/

    Run manageprofiles with the -help argument to get a list of the input arguments or more detailed help on any of the supported arguments.
    For example, to get a list of valid arguments, run: ./manageprofiles.sh -help
    Or, to get help on argument to create a profile, run: ./manageprofiles.sh -create -help
    Or, to get help on running the command using a response file, run: ./manageprofiles.sh -response -help

    For the purposes here, let's assume I launched the PMT and created a default application server profile called AppSrv01. At the end to the graphical PMT, an option is displayed to launch First Steps. Alternatively, similar to PMT, shortcuts are created on Windows and some flavors of Linux to launch First Steps. For other supported operating systems, First Steps can be launched from the command line.

    Navigate to the firststeps directory located under the directory where the profile was created:
    <WAS_Install_Directory>/profiles/AppSrv01/firststeps/

    ...and then run firststeps.sh or firststeps.bat, whichever it appropriate for your operating system.
    Regards,
    Scott Johnston
    WebSphere Application Server
    Install & Configuration User Experience Lead
  • CGBT_SHIVANSH_RASTOGI
    5 Posts

    Re: How to install WAS 8 on 64 bit Solaris 10 after successfully installation

    ‏2011-07-26T12:28:22Z  
    A First Steps console is created during profile creation and is specific to the profile that is created because different types of profiles have different options available.

    So, let's back up a step to getting a profile created.

    If the option to launch the Profile Management Tool (PMT) is not selected at the end of installation or silent installation was performed, then the PMT has to be launched manually. If your operating system is Windows or some flavors of Linux, let there are shortcuts available to launch the graphical PMT. For other supported operating systems, the graphical PMT can be launched from the command line.

    Navigate to the location where WebSphere Application Server is installed, then into the following directory:
    <WAS_Install_Directory>/bin/ProfileManagment/
    ... and then run pmt.sh or pmt.bat, whichever is appropriate for your operating system.

    This will start up the PMT. Next, click Create... to start the profile creation wizard.

    Alternatively, profiles can be created with the command line tool called manageprofiles, which is located in the bin directory:
    <WAS_Install_Directory>/bin/

    Run manageprofiles with the -help argument to get a list of the input arguments or more detailed help on any of the supported arguments.
    For example, to get a list of valid arguments, run: ./manageprofiles.sh -help
    Or, to get help on argument to create a profile, run: ./manageprofiles.sh -create -help
    Or, to get help on running the command using a response file, run: ./manageprofiles.sh -response -help

    For the purposes here, let's assume I launched the PMT and created a default application server profile called AppSrv01. At the end to the graphical PMT, an option is displayed to launch First Steps. Alternatively, similar to PMT, shortcuts are created on Windows and some flavors of Linux to launch First Steps. For other supported operating systems, First Steps can be launched from the command line.

    Navigate to the firststeps directory located under the directory where the profile was created:
    <WAS_Install_Directory>/profiles/AppSrv01/firststeps/

    ...and then run firststeps.sh or firststeps.bat, whichever it appropriate for your operating system.
    Regards,
    Scott Johnston
    WebSphere Application Server
    Install & Configuration User Experience Lead
    Thanks a ton Scott, the entire confusion was cause I was expecting the GUI to give me the option to create the profile, since here there is no script I could not commence with profile management/creation.

    bash-3.00# ls -alrt
    total 14
    drwxr-xr-x 8 root root 144 Jul 18 17:14 ..
    drwxr-xr-x 2 root root 2 Jul 18 17:25 .
    bash-3.00# pwd
    /opt/IBM/WebSphere/AppServer/bin/ProfileManagement

    However i concentrated on the other option specified by you, and now I have my task done
    bash-3.00# ./manageprofiles.sh -create -templatePath /opt/IBM/WebSphere/AppServer/profileTemplates/default -AppSrv01 -profilePath /opt/IBM/WebSphere/AppServer/profiles/AppSrv01

    INSTCONFSUCCESS: Success: Profile AppSrv01 now exists. Please consult /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/AboutThisProfile.txt for more information about this profile.
  • CGBT_SHIVANSH_RASTOGI
    5 Posts

    Re: How to install WAS 8 on 64 bit Solaris 10 after installing IIM 1.4.4

    ‏2011-07-27T06:38:50Z  
    Thanks a ton Scott, the entire confusion was cause I was expecting the GUI to give me the option to create the profile, since here there is no script I could not commence with profile management/creation.

    bash-3.00# ls -alrt
    total 14
    drwxr-xr-x 8 root root 144 Jul 18 17:14 ..
    drwxr-xr-x 2 root root 2 Jul 18 17:25 .
    bash-3.00# pwd
    /opt/IBM/WebSphere/AppServer/bin/ProfileManagement

    However i concentrated on the other option specified by you, and now I have my task done
    bash-3.00# ./manageprofiles.sh -create -templatePath /opt/IBM/WebSphere/AppServer/profileTemplates/default -AppSrv01 -profilePath /opt/IBM/WebSphere/AppServer/profiles/AppSrv01

    INSTCONFSUCCESS: Success: Profile AppSrv01 now exists. Please consult /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/AboutThisProfile.txt for more information about this profile.
    Hey Scott

    By any chance are you aware if we have any version of WAS which can be downloaded for free from the ibm site and maynot eventually expire? , in short full download version of WAS Development/Network Deployment mode, which is not trial/beta.

    Thanks
    Shivansh
  • Scott Johnston
    Scott Johnston
    101 Posts

    Re: How to install WAS 8 on 64 bit Solaris 10 after installing IIM 1.4.4

    ‏2011-07-27T13:55:14Z  
    Hey Scott

    By any chance are you aware if we have any version of WAS which can be downloaded for free from the ibm site and maynot eventually expire? , in short full download version of WAS Development/Network Deployment mode, which is not trial/beta.

    Thanks
    Shivansh
    I am glad to hear that you were able to get the trial version installed and successfully create profiles.

    The only full version of WAS that is available at no cost (free) and does not include a time out is WebSphere Application Server for Developers.

    Details are available here: http://www.ibm.com/developerworks/downloads/ws/wasdevelopers/

    Developers edition is essentially the same the base edition of WebSphere Application Server, but the term and conditions of the license agreement limit its use to development and testing purposes, and it only has limited free support. Using the developers edition to run an application server in a production environment is not supported. And, full IBM support for the Developers edition has to be purchased separately.

    Regards,
    Scott Johnston
    WebSphere Application Server
    Install & Configuration User Experience Lead