install apps to weblogic
Install a Web application
Installing a Web application refers to making its physical file or directory known to WebLogic Server. A Web application can be installed as WAR archive or exploded WAR directory. After you have installed the Web application, you can start it so that users can begin using it.
To install a Web application:
1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see 1. Use the Change Center).
2. In the left pane of the Administration Console, click Deployments.
3. In the right pane, click Install.
4. Using the Install Application Assistant, locate the WAR file or exploded WAR directory that corresponds to the Web application you want to install. If you specify an exploded directory, WebLogic Server installs all components in and below the specified directory.
5. When you have located the file or directory to install, click Next.
6. Specify whether you want to target the installation as an application or a shared library.
7. Click Next.
8. Select the servers and/or clusters to which you want to deploy the Web application.
Note: If you have not created additional Managed Servers or clusters, you will not see this assistant page
9. Click Next.
10. Optionally update settings about the deployment. These settings include:
⦁ The deployed name of the Web application.
⦁ The security model that is applied to the application.
⦁ How the source files (WAR or exploded directory contents) are made available to targeted Managed Servers and clusters.
Typically, the default values are adequate.
11. Click Next.
12. Review the configuration settings you specified, and click Finish to complete the installation.
Note: If you install an application that follows the below directory structure and there is no deployment plan in the /plan directory, WebLogic server automatically creates a deployment plan for you.
⦁ app-root
⦁ /app
⦁ /plan
1. If you chose to immediately go to the deployment's configuration screen, click the tabs to set additional configuration settings for the Web application. If you chose to change this information later, the Administration Console returns you to the Deployments table, which should now include your newly-installed Web application.
2. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
Not all changes take effect immediately—some require a restart
===================================================================
Install an Enterprise application
Installing an Enterprise application refers to making its physical file or directory known to WebLogic Server. An Enterprise application can be installed as an archived EAR file or as an exploded directory. After you have installed the Enterprise application, you can start it so that users can begin using it.
To install an Enterprise application:
1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
2. In the left pane of the Console, select Deployments.
3. In the right pane, click Install.
4. Using the Install Application Assistant, locate the EAR file or exploded directory that corresponds to the Enterprise application you want to install. If you specify an exploded directory, WebLogic Server installs all components it finds in and below the specified directory. Click the circle to the left of the application.
5. Click Next.
6. Select Install this deployment as an application.
If you have created additional Managed Servers or clusters, you can also select Install this deployment as an application, but target the modules individually. Select this option if, for example, you want to target all Web applications in the Enterprise application to one Managed Server and all EJBs to a different Managed Server. If you have not created additional Managed Servers or clusters, you will not see this option.
7. Click Next.
If you previously selected the option to target the entire Enterprise application to the same server or cluster, the Select Deployment Targets window appears.
Note: If you have not created Managed Servers or clusters, other than the current Administration Server, you will not see this assistant page.
8. Follow these steps:
a. Select the Managed Servers or clusters to which you want to deploy the entire Enterprise application.
b. Click Next.
If you previously selected the option to target individual modules of the Enterprise Application to their own server or cluster, then the Select Modules to Target window appears with a table that contains a list of all the modules, the type of module (such as EJB or Web Application), and the Managed Server, cluster, or JMS server (for application-scoped JMS modules) to which it is currently targeted, if any. Follow these steps:
c. Select the modules which you want to target to a particular Managed Server, cluster or JMS server.
d. Click Next.
e. Select the Managed Server, cluster, virtual host, and/or JMS server to which you want to target the modules.
f. Click Next. The install assistant takes you back to the table of modules, but now the Selected Targets column for the modules you just targeted shows the current target.
g. Repeat the preceding steps until you have targeted all the modules as you wish.
h. Click Next with no modules selected to proceed to the next assistant page.
9. Optionally update settings about the deployment. These settings include:
· The deployed name of the Enterprise application. The default deployment name is the name of the Enterprise Application EAR file or exploded directory.
· For any Web application or EJB modules, the security model that is applied. See Manage security for Web applications and EJBs for detailed information about the models.
· How the source files (EAR or exploded directory contents) are made available to all targeted Managed Servers and clusters. See Controlling Deployment File Copying with Staging Modes for detailed information about the deployment staging modes.
Typically, the default values are adequate.
10. Click Next.
11. Review the configuration settings you have chosen, specify whether you want to immediately update the application's configuration after you install it, then click Finish to complete the installation.
Note: If you install an application that follows the below directory structure and there is no deployment plan in the /plan directory, WebLogic server automatically creates a deployment plan for you.
· app-root
· /app
· /plan
12. If you chose to immediately go to the deployment's configuration screen, click on the tabs to set additional configuration settings for the Enterprise application. If you chose to change this information later, the Console returns you to the Deployments table, which should now include your newly-installed Enterprise application.
13. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
Not all changes take effect immediately—some require a restart (see Use the Change Center).
============================================================
Start and stop a deployed Enterprise application
====================================
Before you begin
You must install an Enterprise application before you can start it. See Install an Enterprise application.
Starting an Enterprise Application makes the application available to WebLogic Server clients; stopping it makes it unavailable.
When you start an application, you can make it immediately available to clients, or you can start it in Administartion Mode to first ensure that it is working as you expect. Starting in Administration mode allows you to perform final ("sanity") checking of the distributed application directly in the production environment without disrupting clients.
Similarly, you can stop an application so that no clients can use it, or you can stop it in Administration Mode so that only administrative tasks can be performed.
Stopping an application does not remove its source files from the server; you can later redeploy (also called update) a stopped application to make it available to WebLogic Server clients once again.
To start or stop an installed Enterprise Application, follow these steps:
1. In the left pane of the Console, select Deployments.
A table in the right pane displays all deployed Enterprise Applications and Application Modules.
2. In the table, locate the Enterprise application you want to start or stop.
3. Select the check box to the far left of the Enterprise application.
4. Click the Start button at the top or bottom of the Deployments table to start a stopped application. Similarly, click the Stop button to stop an application.
When you start an application, you must pick one of the following options:
⦁ Servicing all requests: Specifies that WebLogic Server make the application immediately available to all clients.
⦁ Servicing only administrative requests: Specifies that WebLogic Server make the application available in Administration Mode only.
When you stop an application, you must pick one of the following options:
⦁ When work completes: Specifies that WebLogic Server wait for the application to finish its work and for all currently connected users to disconnect.
⦁ Force stop now: Specifies that WebLogic Server stop the application immediately, regardless of the work that is being performed and the users that are connected.
⦁ Stop, but continue servicing administrative requests: Specifies that WebLogic Server stop the application once all its work has finished, but to then put the application in Administration Mode so it can be accessed for administrative purposes.
1. Click Yes to confirm your decision.
Start and stop a deployed Enterprise application
Before you begin
You must install an Enterprise application before you can start it. See Install an Enterprise application.
Starting an Enterprise Application makes the application available to WebLogic Server clients; stopping it makes it unavailable.
When you start an application, you can make it immediately available to clients, or you can start it in Administartion Mode to first ensure that it is working as you expect. Starting in Administration mode allows you to perform final ("sanity") checking of the distributed application directly in the production environment without disrupting clients.
Similarly, you can stop an application so that no clients can use it, or you can stop it in Administration Mode so that only administrative tasks can be performed.
Stopping an application does not remove its source files from the server; you can later redeploy (also called update) a stopped application to make it available to WebLogic Server clients once again.
To start or stop an installed Enterprise Application, follow these steps:
1. In the left pane of the Console, select Deployments.
A table in the right pane displays all deployed Enterprise Applications and Application Modules.
2. In the table, locate the Enterprise application you want to start or stop.
3. Select the check box to the far left of the Enterprise application.
4. Click the Start button at the top or bottom of the Deployments table to start a stopped application. Similarly, click the Stop button to stop an application.
When you start an application, you must pick one of the following options:
⦁ Servicing all requests: Specifies that WebLogic Server make the application immediately available to all clients.
⦁ Servicing only administrative requests: Specifies that WebLogic Server make the application available in Administration Mode only.
When you stop an application, you must pick one of the following options:
⦁ When work completes: Specifies that WebLogic Server wait for the application to finish its work and for all currently connected users to disconnect.
⦁ Force stop now: Specifies that WebLogic Server stop the application immediately, regardless of the work that is being performed and the users that are connected.
⦁ Stop, but continue servicing administrative requests: Specifies that WebLogic Server stop the application once all its work has finished, but to then put the application in Administration Mode so it can be accessed for administrative purposes.
1. Click Yes to confirm your decision.
Installing a Web application refers to making its physical file or directory known to WebLogic Server. A Web application can be installed as WAR archive or exploded WAR directory. After you have installed the Web application, you can start it so that users can begin using it.
To install a Web application:
1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see 1. Use the Change Center).
2. In the left pane of the Administration Console, click Deployments.
3. In the right pane, click Install.
4. Using the Install Application Assistant, locate the WAR file or exploded WAR directory that corresponds to the Web application you want to install. If you specify an exploded directory, WebLogic Server installs all components in and below the specified directory.
5. When you have located the file or directory to install, click Next.
6. Specify whether you want to target the installation as an application or a shared library.
7. Click Next.
8. Select the servers and/or clusters to which you want to deploy the Web application.
Note: If you have not created additional Managed Servers or clusters, you will not see this assistant page
9. Click Next.
10. Optionally update settings about the deployment. These settings include:
⦁ The deployed name of the Web application.
⦁ The security model that is applied to the application.
⦁ How the source files (WAR or exploded directory contents) are made available to targeted Managed Servers and clusters.
Typically, the default values are adequate.
11. Click Next.
12. Review the configuration settings you specified, and click Finish to complete the installation.
Note: If you install an application that follows the below directory structure and there is no deployment plan in the /plan directory, WebLogic server automatically creates a deployment plan for you.
⦁ app-root
⦁ /app
⦁ /plan
1. If you chose to immediately go to the deployment's configuration screen, click the tabs to set additional configuration settings for the Web application. If you chose to change this information later, the Administration Console returns you to the Deployments table, which should now include your newly-installed Web application.
2. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
Not all changes take effect immediately—some require a restart
===================================================================
Install an Enterprise application
Installing an Enterprise application refers to making its physical file or directory known to WebLogic Server. An Enterprise application can be installed as an archived EAR file or as an exploded directory. After you have installed the Enterprise application, you can start it so that users can begin using it.
To install an Enterprise application:
1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
2. In the left pane of the Console, select Deployments.
3. In the right pane, click Install.
4. Using the Install Application Assistant, locate the EAR file or exploded directory that corresponds to the Enterprise application you want to install. If you specify an exploded directory, WebLogic Server installs all components it finds in and below the specified directory. Click the circle to the left of the application.
5. Click Next.
6. Select Install this deployment as an application.
If you have created additional Managed Servers or clusters, you can also select Install this deployment as an application, but target the modules individually. Select this option if, for example, you want to target all Web applications in the Enterprise application to one Managed Server and all EJBs to a different Managed Server. If you have not created additional Managed Servers or clusters, you will not see this option.
7. Click Next.
If you previously selected the option to target the entire Enterprise application to the same server or cluster, the Select Deployment Targets window appears.
Note: If you have not created Managed Servers or clusters, other than the current Administration Server, you will not see this assistant page.
8. Follow these steps:
a. Select the Managed Servers or clusters to which you want to deploy the entire Enterprise application.
b. Click Next.
If you previously selected the option to target individual modules of the Enterprise Application to their own server or cluster, then the Select Modules to Target window appears with a table that contains a list of all the modules, the type of module (such as EJB or Web Application), and the Managed Server, cluster, or JMS server (for application-scoped JMS modules) to which it is currently targeted, if any. Follow these steps:
c. Select the modules which you want to target to a particular Managed Server, cluster or JMS server.
d. Click Next.
e. Select the Managed Server, cluster, virtual host, and/or JMS server to which you want to target the modules.
f. Click Next. The install assistant takes you back to the table of modules, but now the Selected Targets column for the modules you just targeted shows the current target.
g. Repeat the preceding steps until you have targeted all the modules as you wish.
h. Click Next with no modules selected to proceed to the next assistant page.
9. Optionally update settings about the deployment. These settings include:
· The deployed name of the Enterprise application. The default deployment name is the name of the Enterprise Application EAR file or exploded directory.
· For any Web application or EJB modules, the security model that is applied. See Manage security for Web applications and EJBs for detailed information about the models.
· How the source files (EAR or exploded directory contents) are made available to all targeted Managed Servers and clusters. See Controlling Deployment File Copying with Staging Modes for detailed information about the deployment staging modes.
Typically, the default values are adequate.
10. Click Next.
11. Review the configuration settings you have chosen, specify whether you want to immediately update the application's configuration after you install it, then click Finish to complete the installation.
Note: If you install an application that follows the below directory structure and there is no deployment plan in the /plan directory, WebLogic server automatically creates a deployment plan for you.
· app-root
· /app
· /plan
12. If you chose to immediately go to the deployment's configuration screen, click on the tabs to set additional configuration settings for the Enterprise application. If you chose to change this information later, the Console returns you to the Deployments table, which should now include your newly-installed Enterprise application.
13. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
Not all changes take effect immediately—some require a restart (see Use the Change Center).
============================================================
Start and stop a deployed Enterprise application
====================================
Before you begin
You must install an Enterprise application before you can start it. See Install an Enterprise application.
Starting an Enterprise Application makes the application available to WebLogic Server clients; stopping it makes it unavailable.
When you start an application, you can make it immediately available to clients, or you can start it in Administartion Mode to first ensure that it is working as you expect. Starting in Administration mode allows you to perform final ("sanity") checking of the distributed application directly in the production environment without disrupting clients.
Similarly, you can stop an application so that no clients can use it, or you can stop it in Administration Mode so that only administrative tasks can be performed.
Stopping an application does not remove its source files from the server; you can later redeploy (also called update) a stopped application to make it available to WebLogic Server clients once again.
To start or stop an installed Enterprise Application, follow these steps:
1. In the left pane of the Console, select Deployments.
A table in the right pane displays all deployed Enterprise Applications and Application Modules.
2. In the table, locate the Enterprise application you want to start or stop.
3. Select the check box to the far left of the Enterprise application.
4. Click the Start button at the top or bottom of the Deployments table to start a stopped application. Similarly, click the Stop button to stop an application.
When you start an application, you must pick one of the following options:
⦁ Servicing all requests: Specifies that WebLogic Server make the application immediately available to all clients.
⦁ Servicing only administrative requests: Specifies that WebLogic Server make the application available in Administration Mode only.
When you stop an application, you must pick one of the following options:
⦁ When work completes: Specifies that WebLogic Server wait for the application to finish its work and for all currently connected users to disconnect.
⦁ Force stop now: Specifies that WebLogic Server stop the application immediately, regardless of the work that is being performed and the users that are connected.
⦁ Stop, but continue servicing administrative requests: Specifies that WebLogic Server stop the application once all its work has finished, but to then put the application in Administration Mode so it can be accessed for administrative purposes.
1. Click Yes to confirm your decision.
Start and stop a deployed Enterprise application
Before you begin
You must install an Enterprise application before you can start it. See Install an Enterprise application.
Starting an Enterprise Application makes the application available to WebLogic Server clients; stopping it makes it unavailable.
When you start an application, you can make it immediately available to clients, or you can start it in Administartion Mode to first ensure that it is working as you expect. Starting in Administration mode allows you to perform final ("sanity") checking of the distributed application directly in the production environment without disrupting clients.
Similarly, you can stop an application so that no clients can use it, or you can stop it in Administration Mode so that only administrative tasks can be performed.
Stopping an application does not remove its source files from the server; you can later redeploy (also called update) a stopped application to make it available to WebLogic Server clients once again.
To start or stop an installed Enterprise Application, follow these steps:
1. In the left pane of the Console, select Deployments.
A table in the right pane displays all deployed Enterprise Applications and Application Modules.
2. In the table, locate the Enterprise application you want to start or stop.
3. Select the check box to the far left of the Enterprise application.
4. Click the Start button at the top or bottom of the Deployments table to start a stopped application. Similarly, click the Stop button to stop an application.
When you start an application, you must pick one of the following options:
⦁ Servicing all requests: Specifies that WebLogic Server make the application immediately available to all clients.
⦁ Servicing only administrative requests: Specifies that WebLogic Server make the application available in Administration Mode only.
When you stop an application, you must pick one of the following options:
⦁ When work completes: Specifies that WebLogic Server wait for the application to finish its work and for all currently connected users to disconnect.
⦁ Force stop now: Specifies that WebLogic Server stop the application immediately, regardless of the work that is being performed and the users that are connected.
⦁ Stop, but continue servicing administrative requests: Specifies that WebLogic Server stop the application once all its work has finished, but to then put the application in Administration Mode so it can be accessed for administrative purposes.
1. Click Yes to confirm your decision.
Comments
Post a Comment