Several procedures require you to start or stop the instance
of WebLogic Server where you want to deploy AEM forms modules. Ensure
that WebLogic Server is stopped or running, depending on the task
you are performing.

Activity

Required WebLogic state

Creating a WebLogic domain

Stopped

Creating a WebLogic managed server

Running

Increasing the server thread count

Running

Deploying AEM forms products

Running

Note:

If you are running WebLogic Server on Red Hat® Enterprise Linux Advanced Server 4.0,
set the LD_ASSUME_KERNEL environment variable to
2.4.19 by using the export LD_ASSUME_KERNEL=2.4.19 command.
Then, run WebLogic Server from the same shell in which you set this
environment variable.

Start WebLogic Server

From a command prompt, go to [appserver root]/user_projects/domains/[appserverdomain].

Enter the following command:

(Windows) startWebLogic.cmd

(Linux, UNIX) ./startWebLogic.sh

Stop WebLogic Server

Start WebLogic Server administration console by
typing http://[host name]:7001/console in the URL
line of a web browser.

Log in by typing the user name and password that was used
when creating this WebLogic configuration, and then click Log In.

Under Change Center, click Lock & Edit.

Under Domain Structure, click Environment > Servers.

Click AdminServer and, on the Settings for AdminServer pane,
click the Control tab.

Ensure that AdminServer is selected in the Server Status
table and click Shutdown.

Select When Work Completes to gracefully shut down the server
or select Force Shutdown Now to stop the server immediately without
completing ongoing tasks.

On the Server Life Cycle Assistant pane, click Yes to complete
the shutdown.

The WebLogic Server administration console is no longer available,
and the command prompt that you ran the start command from is available.

Start WebLogic administration console

If WebLogic Admin Server is not already running,
from a command prompt, go to the [appserver root]\user_projects\domains\[domainname] directory,
and enter the following command:

(Windows) startWebLogic.cmd

(Linux, UNIX) ./startWebLogic.sh

Access WebLogic Server administration console by typing http://[host name]:[Port]/console in
the URL line of a web browser, where [Port] is the non-secure
listening port. By default, this port value is 7001.

On the login screen, type your administrator user name and
password, and click Log In.

Start Node Manager

Ensure that WebLogic Server is running.

From a new command prompt, go to [appserver root]/server/bin.

Enter the following command:

(Windows) startNodeManager.cmd

(Linux, UNIX) ./startNodeManager.sh

Stop Node Manager

After you shut down WebLogic Server, you can close the
command prompt from which you called Node Manager.

Start a WebLogic managed server

Note:

This task can be performed only after
you create a WebLogic domain and a managed server.

Ensure that the WebLogic Server and Node Manager are
running.

Start WebLogic Server administration console by typing http://[host name]:[port]/console in
the URL line of a web browser.

Under Domain Structure, click Environment > Servers.

In the right pane, click the Control tab.

Select the managed server that you want to start.

Click the Start button below the managed server you want
to start.

Stop a WebLogic managed server

Start WebLogic Server administration console by
typing http://[host name]:[port]/console in
the URL line of a web browser.

Under Domain Structure, click Environment > Servers.

In the right pane, click the Control tab.

Select the managed server that you want to stop.

Click the Shutdown button below the managed server you want
to stop.

Select When Work Completes to gracefully shut down the server
or select Force Shutdown Now to stop the server immediately without
completing ongoing tasks.

On the Server Life Cycle Assistant pane, click Yes to complete
the shutdown.

Twitter™ and Facebook posts are not covered under the terms of Creative Commons.