sun java application server admin console - HomeworkEssaywritercsClub

sun java application server admin console

Configuring
Sun Java System Application Server 9 for ArcIMS

After installing ArcIMS, you must configure
your Web server for ArcIMS. If your Web server is not operational, contact
your system administrator before you proceed. See www.sun.com/software
for information on problems with Sun Java System Application Server 9.
Follow these steps to configure Sun Java System Application Server 9 for
ArcIMS:

 

  1. Verify that the following
    items are located in <Sun Java System Application Server 9 Installation
    Directory>\SDK\domains\domain1\server1\applications\j2ee-modules\servlet\WEB-INF\classes:

  • com directory

  • Esrimap_prop

  • ServletConnector_Res.properties

  • ServletConnector_Res_en_US.properties

 

If you can not verify the above:

      • Start the Sun
        Java System Application Server if it is not started already by going to
        Start > Programs > Sun Microsystems > Application Server PE 9>
        Start Default Server.

      • Go to Start
        > Programs > Sun Microsystems > Application Server PE 9> Admin
        Console to open the administrator console for Sun Java System Application
        Server 9 or type http://localhost:4848 in a Web browser. Log in.

      • In the left
        panel, navigate to Application Server> Applications > Web Applications
        (click on the little bullet to expand applications).

      • In the right
        panel, click Deploy, select Specify a package file to upload to the Application
        Server, then browse to the file <ArcIMS Installation Directory>\ArcIMS\Connectors\Servlet\arcimsservletconnector.war
         and click
        Next.

      • Edit the Application
        Name to say �servlet�.

      • Edit the Context
        Root to say �/servlet�.

      • Click OK.

 

  1. On the Website folder
    (ie. C:\arcims\website), create a WEB-INF folder and create web.xml and
    sun-web.xml text files within this folder.  In
    a text editor such as Notepad, edit these files.

  • Edit web.xml and paste
    the following:

<web-app>

<display-name>website</display-name>

</web-app>

 

  • Edit sun-web.xml and
    paste the following:

<?xml
version="1.0" encoding="UTF-8"?>

<sun-web-app>

<context-root>/website</context-root>

</sun-web-app>

 

  1. On the Output folder
    (ie. C:\arcims\output), create a WEB-INF folder and create web.xml and
    sun-web.xml text files within this folder.  In
    a text editor such as Notepad, edit these files.

  • Edit web.xml and paste
    the following:

<web-app>

<display-name>output</display-name>

</web-app>

 

  • Edit sun-web.xml and
    paste the following:

<?xml
version="1.0" encoding="UTF-8"?>

<sun-web-app>

<context-root>/output</context-root>

</sun-web-app>

 

  1. Go to Start > Programs
    > Sun Microsystems > Application Server PE > Admin Console to
    open the administrator console for Sun Java System Application Server
    9 or type http://localhost:4848 in a Web browser. Log in.

 

  1. In the left panel, navigate
    to Application Server> Applications > Web Applications (click on
    the little bullet to expand applications).

 

  1. In the right panel,
    click Deploy, select Specify a package file or a directory path that must
    be accessible from the server, then enter website path (ie. C:\arcims\website)
    and click Next.

 

  1. Edit the Application
    Name to say �website�.

 

  1. Edit the Context Root
    to say �/website�.

 

  1. Click OK.

 

  1. In the right panel,
    click Deploy, select Specify a package file or a directory path that must
    be accessible from the server, then enter output path (ie. C:\arcims\output)
    and click Next.

 

  1. Edit the Application
    Name to say �output�.

 

  1. Edit the Context Root
    to say �/output�.

 

  1. Click OK.

 

  1. Navigate to <Sun
    Java System Application Server 9 Installation Directory>\SDK\domains\domain1\applications\j2ee-modules\servlet\WEB-INF\classes.
    In a text editor (such as Notepad), open the Esrimap_prop file and edit
    �APPSMACHINE� to reflect the name of the ArcIMS host. Save and close the
    file.

 

  1. Navigate to <Sun
    Java System Application Server 9 Installation Directory>\SDK\domains\domain1\config
    and in a text editor (such as Notepad) open the server.policy file.  Copy
    and add the following text immediately above the line that begins �\\
    Following grant block is only required by connectors�:

// Permissions
for the ArcIMS Servlet Connector

grant
codeBase "file:/<Sun Java System Application Server 9 Installation
Directory>/SDK/domains/domain1/applications/j2ee-modules/servlet/WEB-INF/classes/-"

    permission
java.util.PropertyPermission "*", "read,write";

;

Save and close the file.

 

  1. Navigate to <Sun
    Java System Application Server 9 Installation Directory>\SDK\domains\domain1\config
    and in a text editor (such as Notepad) open the default-web.xml file.
     Copy and
    add the following text within the <welcome-file-list> block.

<welcome-file>default.html</welcome-file>

<welcome-file>default.htm</welcome-file>

Save and close the file.

 

  1. Navigate to <Sun
    Java System Application Server 9 Installation Directory>\SDK\domains\domain1\applications\j2ee-modules\servlet\WEB-INF
    and in a text editor (such as Notepad) open the web.xml file.  Copy
    and add the following text above the </welcome-file-list> line.

          <welcome-file>default.html</welcome-file>

          <welcome-file>default.htm</welcome-file>

Save and close the file.

 

  1. Restart Sun Java System
    Application Server 9.

 

Using the Diagnostics tool to test your ArcIMS installation

  1. Verify your ArcIMS installation
    was successful.

a. Choose Start > Programs > ArcGIS
> ArcIMS > Diagnostics. The ArcIMS Diagnostics tool displays.

b. Select your Web server protocol, type
your Web server name including domain, and type your port number. The
default is 80.

c. Click 1 to test the ArcIMS Servlet Connector
and 2 to test the ArcIMS Application Server.

 

If these tests are successful, your ArcIMS
Application Server and ArcIMS Servlet Connector are configured correctly.

 

If you receive an error message, select the
error number in the dropdown list and click View. The error number and
a description are displayed. Follow the instructions in the description
to fix the problem and try the Diagnostics tool again.

 

See Configuring
Sun Java System Application Server 9 for Service Administrator for
information on configuring ArcIMS Service Administrator.

 

See Step
5:Configure ArcIMS for the final step required to get ArcIMS running.

 

 

Sun Java System Application Server 9.1 Quick Start Guide
  • Previous: Application Server Administration Tools
  • Next: Where to Go Next

Starting the Server

This topic provides instructions for the following basic tasks:
starting the Domain Administration Server (DAS), logging into the
Admin Console, examining the log files, and starting the node agent.
The steps are presented in the order that you should complete them.

  • To Start the Domain on Solaris and Linux

  • To Start the Domain on Windows

  • To Log On to the Admin Console

  • To View the Domain Administration Server Log File

  • To Start the Node Agent

  • To Add Cluster Support to a Domain

  • To Start the Bundled Java DB Server

ProcedureTo Start the Domain on Solaris and Linux

To start the Domain Administration Server, start the default
domain, domain1.

  1. Add the as-install/bin/ directory
    to the PATH environment variable.

  2. Start the server by entering this command:

    asadmin start-domain domain1

    When you are prompted
    for the user, admin password, and the master password, enter your
    user name and the passwords that you provided during installation.

    When the start up process is complete, the following message
    appears:

    Domain domain1 started

    On the Ubuntu Linux operating system, if you do
    not have root access, you can use the asadmin convenience
    wrapper script located in /usr/bin to create a
    domain in your home directory. Running asadmin start-domain from
    the convenience script creates and starts the domain. For more information
    on the convenience script, type asadmin man at
    the command prompt. If you have root access, you can also create and
    start domains using the asadmin commands create-domain and start-domain from the as-install/bin directory. These domains are created by default in domain-root-dir.

    Each domain has a corresponding profile: enterprise,
    cluster, or developer. domain1 is created with
    the default profile, which is defined in the AS_ADMIN_PROFILE variable
    defined in the asadminenv.conf file. For more
    information on the three profiles see the Usage Profiles in Sun Java System Application Server 9.1 Administration Guide . If domain1 was created
    with developer profile, when you log in to the Admin Console, you
    cannot use features such as clustering and node agents. To use clusters
    and server instances, use the create-domain command
    to create a domain with cluster profile.

    For information
    on creating domains, type asadmin create-domain --help or see create-domain(1) in the Sun Java System Application Server 9.1 Reference Manual .

ProcedureTo Start the Domain on Windows

To start the Domain Administration Server, start the default
domain, domain 1.

  1. From the Explorer window or desktop, right click My Computer.

  2. Choose Properties to display the System Properties dialog.

  3. Click the Advanced tab.

  4. Click Environment Variables.

  5. In the User variables section:

    • If a PATH variable exists, verify that as-install\bin exists in the path: as-install\bin;other_entries. If as-install\bin does
      not exist in the PATH variable, add it.

    • If a PATH variable is not present,
      click New. In Variable Name, type PATH. In Variable
      Value, type the path to the server’s bin directory: as-install\bin. Click OK to commit the change.

  6. Add a new environment variable AS_ADMIN_USER and
    set it to the Administrative User Name that you assigned during installation.

  7. Click OK to commit the change and close the remaining
    open windows.

  8. Start the Application Server by clicking the Start Admin Server
    option within the Programs menu.

  9. When a command prompt window opens to prompt you for the
    admin password and the master password, enter the passwords that you
    provided during installation.

    A window appears with a
    message telling that you the server is starting:

    Starting
    Domain domain1, please wait. Log redirected to
    domain_dir\domain1\logs\server.log...

    When the
    startup process has completed, you see an additional message:

    Domain domain1 started.Press any
    key to continue ...

    Each domain has a corresponding
    profile: enterprise, cluster, or developer. domain1 is
    created with the default profile, which is defined in the AS_ADMIN_PROFILE variable defined in the asadminenv.conf file.
    For more information on profiles see the Usage Profiles in Sun Java System Application Server 9.1 Administration Guide . If domain1 was created
    with developer profile, when you log in to the Admin Console, you
    cannot use features such as clustering and node agents. To use clusters
    and server instances, use the create-domain command
    to create a domain with cluster profile. For information on creating
    domains, type asadmin create-domain --help or see create-domain(1) in the Sun Java System Application Server 9.1 Reference Manual .

  10. Press a key to close the message window.

ProcedureTo Log On to the Admin Console

The Admin Console is a browser interface that simplifies a variety
of administration and configuration tasks. It is commonly used to:

  • Deploy and undeploy applications

  • Enable, disable, and manage applications

  • Configure resources and other server settings

  • Select and view log files

For further information about using the Admin Console, consult
the online help or the Sun Java System Application Server 9.1 Administration Guide .

  1. Type this URL in your browser:

    http:// localhost:4848

    If the
    browser is on a different system than the server, replace the localhost variable with the name of the system that
    the Domain Admin Server is running on.

    4848 is
    the Admin Console’s default port number. If you changed the
    port number during the installation or if you have created a domain
    with another port number, use that number instead.


    Note –

    If a popup window appears with a message such as Website
    Certified by an Unknown Authority
    , click OK.

    This
    message appears because your browser does not recognize the self-signed
    certificate that the Domain Administration Server uses to service
    the Admin Console over the secure transmission protocol.


  2. When the Log in window appears, enter the admin user name
    and password.

  3. Click Login.

    Admin Console has a banner pane, a left pane
with common tasks tree, and a right pane with links for Common Tasks
and documentation

    In the left pane, select what you want to manage from the tree
    provided. In the right pane, various administrative tasks are listed
    under the Common Tasks heading.

ProcedureTo View the Domain Administration Server Log
File

Application Server instances and the Domain Administration Server
produce annotated logs on the file system. By default, all errors,
warnings or useful informative messages are logged.

  1. From the Common Tasks list in the right pane, click Search
    Log Files to launch a new browser window for Log Viewer.

    The Log Viewer provides view, search, and filter
options.

  2. In the Log Viewer window, select “server”
    from the Instance Name drop-down list and click Search.

    The
    Domain Administration Server’s recent log file entries are displayed.

  3. Scan the messages and look for any WARNING or SEVERE messages indicating that problems were encountered
    during server startup.

    You can close Log Viewer at any
    time. After you create clusters and deploy applications, examine log
    files if any of the operations failed. Use Log Viewer to view the
    log files of any running Application Server instance in the domain.

ProcedureTo Start the Node Agent

A node agent is a lightweight process running
on each machine that participates in an Application Server administrative
domain. The node agent is responsible for starting and stopping server
instances on the host. It also communicates with the Domain Administration
Server to create new Application Server instances.


Note –

You can use node agents only on domains with the cluster
or enterprise profile. If you are running only a developer domain,
you need to create a domain with cluster profile before you can create
and use node agents. For information on creating domains, type asadmin
create-domain
--help or see create-domain(1) in the Sun Java System Application Server 9.1 Reference Manual


One node agent is needed on a machine for each Application Server
administrative domain that the machine belongs to. If you are using
Sun Java System Application Server 9.1 (Enterprise bundle), choose the
Node Agent Component during installation and a default node agent
called hostname is created. If you have
installed Glassfish, the node agent is not automatically created.
To create a node agent, follow the instructions in To Create a Node Agent in Sun Java System Application Server 9.1 High Availability Administration Guide .

  1. In a terminal window, type this command:

    asadmin start-node-agent nodeagentname

    Replace the variable nodeagentname with
    the name of the node agent you created. If you want to use the default
    node agent, which is created by Sun Java System Application Server 9.1,
    replace the nodeagentname with the name
    of the host on which Application Server is running. If your default domain
    on port 4848 (domain1) is not running on cluster
    or enterprise profile, use the --port option
    to specify the port of the cluster or enterprise domain.

  2. When you are prompted, provide the master password.

    The node agent starts and connects with the Domain Administration
    Server.


    Note –

    Ensure that the Domain Administration Server is running
    before you start the node agent. Check the server.log file
    of a cluster instance to identify problems related to starting node
    agents or cluster instances.

    If you have problems while
    starting a node agent or a cluster on Windows, see the Sun Java System Application Server 9.1 Release Notes for possible solutions
    to the problem.


    After the node agent has been started once, you can view it
    in the Admin Console.

Next Steps

In this section you started the Domain Administration Server
and confirmed that it is running. You also logged in to the Admin
Console and used the Log Viewer. You started the node agent. You can
stop the Quick Start trail here if you do not wish to continue, or
you can go on to the next section.

ProcedureTo Add Cluster Support to a Domain

You can use the Admin Console add cluster support to a developer
domain.

  1. Log on to the Admin Console. For instructions, see To Log On to the Admin Console .

  2. From the left pane, click Application Server.

  3. Click the Add Cluster Support button in the General tab.

  4. The Add Cluster Support page appears. Review the information
    on this page and click OK.

  5. In the Restart Required Page, click the Stop Instance
    button to stop the domain.

  6. Log in to the machine where the domain is installed and
    run the following command: as-install/bin/asadmin list-domains. Verify that the domain was stopped.

  7. Run the following command: as-install/bin/asadmin start-domain <domain-name>

    The restarted domain supports clustering.

Troubleshooting

If the restarted domain does not show clustering capabilities,
stop the domain, reboot the machine on which the domain is installed,
and restart the domain as shown in step 7.

ProcedureTo Start the Bundled Java DB Server

The Application Server includes a bundled Java DB server. To start
it, use the following procedure:

  1. Make sure that you are logged in as the user that installed
    the database.

  2. Run asadmin start-database.

    For more information on the start-database command,
    see the command’s help or the start-database(1) information in Sun Java System Application Server 9.1 Reference Manual .

  • Previous: Application Server Administration Tools
  • Next: Where to Go Next