The WebLogic 8 plug-in provides several specific component types and provides easy access to functions that are useful for working with BEA WebLogic 8 applications. This chapter describes the following information:
Installing and Using the WebLogic 8 Environment with the Sun N1 Service Provisioning System
Solaris: Running the WebLogic 8 Demonstration Application: Avitek Medical Records
The provisioning system enables you to provision and manage applications.
The WebLogic 8 plug-in provides both plans and component procedures as tools for you to perform tasks. By using plans, you link directly to the functionality you desire. Using component procedures, you have a greater number of tasks that you can perform.
The WebLogic 8 plug-in organizes tasks in four categories: application tasks, infrastructure tasks, configuration tasks, and advanced tasks. These task categories follow the same convention for describing the task that you need to perform.
Table 4–1 Common Task Names
Task Name |
Description |
---|---|
View Installations, View Configurations, View Clusters, View Cluster Members |
View a list of where all components of a particular type are installed. |
View All |
View all components of a particular type within a specified folder. |
Create |
Links to the component Details page where you can add a new component of this type to the provisioning system. You can create new components by importing them from an existing WebLogic Admin Server or by browsing the file system. |
Start or Stop |
Links to the component Details page to run the Start or Stop component procedure. |
Install, Uninstall, Remove, Join, Leave |
Represents a plan that produces the described functionality. |
Two prerequisites exist for each task documented in this book.
The WebLogic Administration Server is used to perform or verify many operations. Therefore, to perform any task that alters the WebLogic 8 environment, the Administration Server must be configured within the provisioning system with the correct connection information and running.
The Administration Server does not need to be online when installing the WebLogic software, creating the WebLogic Domain, or when creating the enterprise application (EAR), web application (WAR), and Java archive (JAR) files.
All tasks within the provisioning system require that you have specific permissions. To perform tasks with the WebLogic plug-in, you must belong to a user group that has the Run Component Procedures permission on the folder that contains the component. You must also have the Allow on Host Set permission for the host set on which you plan to deploy the component.
For more information about permissions, see Chapter 3, Controlling Access Using Permissions, in Sun N1 Service Provisioning System 5.2 System Administration Guide.
For information about how to update your group membership, see How to Change a User’s Group Membership in Sun N1 Service Provisioning System 5.2 System Administration Guide.
Creating a WebLogic 8 environment within the provisioning system is similar to the process of creating the environment without the provisioning system.
(Optional) Install WebLogic 8 application on a reference server.
By installing and configuring a reference server, you can verify that the configuration works as desired and then replicate the configuration across multiple hosts.
Import the WebLogic 8 plug-in.
See Importing Plug-Ins in Sun N1 Service Provisioning System 5.2 System Administration Guide.
Set the WebLogic session variables: WL_DEFAULT_PASSWORD and WL_DEFAULT_USER.
Prepare all hosts.
The WebLogic 8 plug-in contains a new system service that must be distributed to all hosts in the provisioning system. See Preparing a Physical Host in Sun N1 Service Provisioning System 5.2 System Administration Guide.
Install the WebLogic software.
Create a WebLogic domain by installing an Administrative Server.
See How to Create a WebLogic 8 Domain and Administration Server.
Create a Managed Server in the new WebLogic domain.
Create and Install the WebLogic license component.
See How to Create a License Component and How to Install a License Component.
(Optional) Create a WebLogic 8 cluster.
(Optional) Add a cluster member by assigning existing Managed Servers to the cluster.
If necessary, configure the application's connection to the database.
Configure a connection pool.
(Optional) Configure a Multi Pool.
Configure a data source or transactional data source.
See Data Source and Transaction Data Source Component Types.
If the application uses Java Messaging Service, configure the JMS server.
Capture application files (EARs, JARs, and WARs).
Deploy applications to targets hosts, host sets, or clusters.
An application can target either a cluster or a Managed Server.
See Installing an Enterprise Application, Installing a Web Application, or Installing a JAR or EJB File.
Use the WebLogic 8 Common Tasks page as a starting point to create and manage WebLogic servers and clusters.
You need to create a domain and Administration Server before you can set up Managed Servers to host your applications. A domain is a set of WebLogic servers that is managed by an Administration Server. All information about the domain is contained in a configuration file that is stored on the Administration Server.
When you create a new domain by installing the AdminServer component, you also:
Configure the domain
Create the Admin Server virtual host
You can use this procedure to create a new domain or you can use this procedure to register an existing domain within the provisioning system by selecting the markOnly option.
In this document, two similar terms are used: AdminServer and Administration Server. The prepackaged Sun N1 Service Provisioning System WebLogic 8 component is called the AdminServer component. AdminServer represents the provisioning system component and Administration Server represents the installed application running in the WebLogic 8 environment.
To create a WebLogic 8 domain, you must belong to a user group that has the Run Component Procedures permission on the folder that contains the component. You must also have the Allow on Host Set permission for the host set on which you plan to deploy the component.
Verify that your WebLogic session variables, WL_DEFAULT_USER and WL_DEFAULT_PASSWORD, are set.
WebLogic session variables must be seven characters long and include a number.
For more information about session variables, see Chapter 5, Session Variables, in Sun N1 Service Provisioning System 5.2 Plan and Component Developer’s Guide.
In the Common Tasks section in the browser interface, click WebLogic 8.
Click the Domain Management: Create link.
The plan's Details page displays.
Click Run.
The Run page displays.
In the Plan Parameters area, select the variable settings for the AdminServer component that you plan to deploy.
If the variable settings have been established for this component, select the appropriate settings from the menu.
If the settings are not available from the menu, click Select From List.
The Select Variable Settings From List window displays.
To create a new set of variable settings, select Create Set.
The following list provides commonly updated variables for the AdminServer component.
Required. The WebLogic domain name.
Required. The default TCP port for the AdminServer virtual host to use.
Before the domain is created, a check is performed to verify that this port is available. To fix this error, free the port and run the startAdminServer component procedure found on the AdminServer component Details page.
Optional. True specifies that the SSL port can be used to connect the Administration Server.
Required for Windows systems. This variable specifies the name of the domain start script for Windows Systems. The value of this variable must be a .cmd file.
Required. This variable determines whether the managed server is run in production mode. The default value of production is false. This variable can be set to true or false.
Variables that are updated less often include configuration variables such as the following:
Required. The name of the managed server that hosts the domain administration console. The default value is myserver. If performing a markOnly install, set the variable to the server name used during the WebLogic install.
Required. The hostname or IP address that managed servers use to connect to the Admin Server. The default value is the hostname of the Remote Agent on which the Admin Server resides.
Required. This variable becomes the name of the domain's virtual host. The substitution variable is based on the values for the host name and for the domain name. This variable follows the format :[target:sys.hostName]_weblogic_admin_ :[domainName]. For example, sqa-420_weblogic_admin_wls.
The Select Variable Settings From List window displays.
In the text field at the top of the table, type the name of the new variable settings set.
To change the WebLogic Domain name, select the domainName row and type the new domain name.
To change the port number for the Administration Server from the default value of 7001, select the adminPort row and type the new port number.
To specify that secure HTTP be used to connect to the Administration Server, select the secureConnect row and type True in the text field.
To change the path to where WebLogic is installed, select the beaHome row and type the correct path.
The installPath variable, beaHome variable, and the WebLogic BEAHome of installation plan variable must contain the same value .
The default value for these three variables is /usr/local/bea.
The value for the installPath variable is treated as a relative path to the default Remote Agent directory, unless you specify an absolute path, such as /opt or c:\mydir. For example, for a Windows Remote Agent, if you set the installPath variable to c\mydir and deploy the file to an Agent with a default home directory of c:\Program Files\N1 Service Provisioning System\agent, the file is deployed to c:\Program Files\N1 Service Provisioning System\agent\c\mydir.
If necessary, modify the value of the remaining predefined variable.
The targetRefName is pre-defined for you, although you can modify it if necessary. The targetRefName is created based on the values for the host name and for the domain name. This variable follows the format :[target:sys.hostName]_admin_:[domainName]
To use variable components from another component, click Import Set.
For more information about importing variable sets, see How to Run a Plan in Sun N1 Service Provisioning System 5.2 Operation and Provisioning Guide.
The Import Variable Settings window displays.
Select the target host.
Target the virtual host that was created when you installed the WebLogic software. See How to Install the WebLogic Software procedure.
The target host must be a member of the com.sun.weblogic#InstallHS host set.
If you are capturing an existing WebLogic domain within the provisioning system, select the markOnly option.
Click Run Plan (Includes Preflight).
You can create multiple domains using the same user and password. However, if you prefer to have separate passwords for each of your domains, you need to update your WebLogic user and password session variables after each domain installation.
The plan that creates new domains always uses the default session variable names, WL_DEFAULT_USER and WL_DEFAULT_PASSWORD.
Install the new domain and AdminServer using the default WebLogic session variables, WL_DEFAULT_USER and WL_DEFAULT_PASSWORD.
See How to Create a WebLogic 8 Domain and Administration Server.
Go to the Session Variables page by clicking Session Variables at the top of the browser interface.
Create new session variables for the newly installed AdminServer.
These new session variables have the same value as the default variables with which you installed the AdminServer.
Attribute Name |
Default Session Variable Names |
New Session Variable Names |
---|---|---|
adminUser |
WL_DEFAULT_USER |
WL_TEST_USR |
adminPassword |
WL_DEFAULT_PASSWORD |
WL_TEST_PWD |
Go to the host Details page for the AdminServer you created in step 1 and click Edit.
Update the AdminServer's host type attributes.
For example, replace the adminUser value with :[session:WL_TEST_USR].
If you have another domain to install, return to the Session Variables page and update the default WebLogic session variables with the new values to be used for the next domain you plan to install.
You can run multiple Managed Servers in each domain to host your applications. WebLogic Managed Servers are captured and represented in the provisioning system by Server components. Throughout this book, Server refers to the provisioning system component, while Managed Server refers to the installed instance of the Managed Server running in the WebLogic 8 environment.
You can use this procedure to create a new Managed Server or you can use this procedure to register an existing Managed Server within the provisioning system by selecting the markOnly option.
If you plan to create a cluster, you need to create the Managed Servers that belong to that cluster before you create the cluster.
Before you can create a WebLogic Managed Server, the following criteria must be met.
A domain to contain the Managed Server must exist.
For more information, see How to Create a WebLogic 8 Domain and Administration Server.
The domain's AdminServer must be running.
To manually start an AdminServer, run the startAdminServer component procedure from the AdminServer component Details page.
The WebLogic software must be installed on the host on which you plan to install a Managed Server.
You must belong to a user group that has the Run Component Procedures permission on the folder that contains the component. You must also have the Allow on Host Set permission for the host set on which you plan to deploy the component.
In the Common Tasks section in the browser interface, click WebLogic 8.
Click the Application Server Management: Create link.
The plan's Details page displays.
Click Run.
The Run page displays.
In the Plan Parameters area, select the variable settings for the ManagedServer component that you plan to deploy.
The Server component represents the Managed Server instance within the WebLogic 8 environment.
If the variable settings have been established for this component, select the appropriate settings from the menu.
If the settings are not available from the menu, click Select From List.
The Select Variable Settings From List window displays.
To create a new set of variable settings, select Create Set.
The following list provides commonly updated variables for the ManagedServer component.
Required. A name for the new variable set you create
Required. Name of the AdminServer virtual host that hosts the new Managed Server. This value will be in the format remoteAgentName_weblogic_admin_domainName.
You can find the virtual host on the Hosts page. The virtual host will be of type com.sun.weblogic8#AdminServerHS.
Required. The new Managed Server's name. This name is used in the targetRefName variable to create the Managed Server virtual host.
Required. The name of the Managed Server's startup script.
The default location of the startup script is /usr/local/bea/user_projects/servers/ domainName/targetName. This location can be changed by setting the altServerRoot component variable.
Required for Windows systems. This variable specifies the name of the domain start script for Windows Systems. The value of this variable must be a .cmd file.
Required if not using SSL. The default value for this variable is 7010. If this port is not available, the Managed Server does not start and an error message displays. After you free the port, you can start the Managed Server by running the Start component procedure on the Managed Server's component Details page.
Required if using SSL. The default value for this variable is 7020. This port must be available, otherwise the Managed Server does not start and an error message displays. After you free the port, you can start the Managed Server by running the Start component procedure on the Managed Server's component Details page.
Required. This variable determines whether the managed server is run in production mode. The default value of production is false. This variable can be set to true or false.
Required. The UNIX user to run the WebLogic installation. This user must exist on the host to be installed and must have write permission on the beaHome directory. The default value for this variable is taken from the WebLogic software installation component.
Required. The IP address the Managed Server uses to listen.
Required. The directory used for the Managed Server.
To use variable components from another component, click Import Set.
For more information about importing variable sets, see How to Run a Plan in Sun N1 Service Provisioning System 5.2 Operation and Provisioning Guide.
Select the target host or target host set.
The Managed Server resides on the Remote Agent that you target.
The target host must be a member of the com.sun.weblogic#AdminServer host set.
Target the virtual host that was created when you installed the WebLogic software. See How to Install the WebLogic Software procedure.
The target host must be a member of the com.sun.weblogic#InstallHS host set.
If you are capturing an existing WebLogic Managed Server within the provisioning system, select the markOnly option.
Click Run Plan (Includes Preflight).
This procedure provides the steps on how to create a license component. After the license component is created, see How to Install a License Component to install the license.
In the Common Tasks section in the browser interface, click WebLogic 8.
Click the License Management: Create link.
The component's Edit page displays.
Type the name of the new license component.
(Optional) Type the components label and description.
Select a host that has a copy of the BEA license on its file system.
Navigate through the host's file system and select the license file.
Click Check In Selected Item.
The component's Check In page displays.
Choose a folder on which you have edit permissions.
Click Continue to Check In.
Before you can install a license component, one must exist within the provisioning system. See How to Create a License Component.
In the Common Tasks section in the browser interface, click WebLogic 8.
Click the License Management: View All link.
The Components page displays.
In the row of the license component that you plan to install, click Details.
The component's Details page displays.
In the Component Procedures table, select the Default: Install procedure and click Run.
The plan's Run page displays.
Select the target host.
You target the AdminServer virtual host.
You do not need to modify the component variables for license installation.
(Optional) If you want to replace an existing license, in the Plan Variables section, select the Replace Rather Than Merge With Existing License option.
If you choose to replace an existing license, you need to restart the WebLogic domain for the new license to take effect.
Click Run Plan (Includes Preflight).
You might need to create a cluster for the following reasons:
To increase application availability with the server's failover capabilities
To increase throughput by scaling applications across multiple servers
A cluster appears to clients as a single WebLogic Managed Server instance. The server instances that constitute a cluster can run on the same machine, or can be located on different machines. Each cluster member in a cluster must run the same version of WebLogic.
You can use this procedure to create a new cluster or you can use this procedure to register an existing cluster within the provisioning system by selecting the markOnly option.
Before you create a WebLogic cluster, you must create a WebLogic domain, an Administration Server, and the Managed Servers that you plan to use in the cluster.
To create a WebLogic cluster, you must belong to a user group that has the Run Component Procedures permission on the folder that contains the component. You must also have the Allow on Host Set permission for the host set on which you plan to deploy the component.
In the Common Tasks section in the browser interface, click WebLogic 8.
Click the Cluster Management: Create link.
The plan's Details page displays.
Click Run.
The Run page displays.
In the Plan Parameters area, select the variable settings for the Cluster component that you plan to deploy.
If the variable settings have been established for this component, select the appropriate settings from the menu.
If the settings are not available from the menu, click Select From List.
The Select Variable Settings From List window displays.
To create a new set of variable settings, select Create Set.
The following list provides commonly updated variables for the ManagedServer component.
Required. A name for the new variable set you create
Required. The name of the new cluster.
Optional. This variable can be a DNS host name that maps to multiple IP addresses or a comma-separated list of single address host names or IP addresses. No value is necessary for this variable.
This variable provides the address that cluster members can use to communicate with each other.
This variable provides the port number that cluster members can use to communicate with each other.
The Select Variable Settings From List window displays.
In the text field at the top of the table, type the name of the new variable settings set.
To change the name of the new cluster, select the targetName row and type the new name.
To specify the address for the cluster instance, select the clusterAddress row and type the address.
This variable can be a DNS host name that maps to multiple IP addresses or a comma-separated list of single address host names or IP addresses. No value is necessary for this variable.
To change the cluster's multicast port, select the multicastAddress row and type the new address.
This variable provides the address that cluster members can use to communicate with each other. The default value is 237.0.0.1.
To change the cluster's multicast address, select the multicastPort row and type the new port number.
This variable provides the aport number that cluster members can use to communicate with each other. The default value is 7001.
If necessary, modify the value of the remaining predefined variables.
The installPath is created based on the value for the AdminServer virtual host name, the domain name, and the cluster name.
The targetRefName is created based on the values for the host name and for the domain name. This variable follows the format :[target:sys.hostName]_admin_:[domainName]
Click Save.
The new variable settings display in the table.
Click Select.
To use variable components from another component, click Import Set.
For more information about importing variable sets, see How to Run a Plan in Sun N1 Service Provisioning System 5.2 Operation and Provisioning Guide.
Select the target host.
Because you can only install a cluster on an Administrative Server, the target host is the AdminServer virtual host.
If you are capturing an existing WebLogic cluster within the provisioning system, select the markOnly option.
Click Run Plan (Includes Preflight).
Cluster nodes are Managed Servers assigned to a cluster. You will want to create cluster members to make your applications highly available and scalable.
When a Managed Server joins the cluster, the applications that are currently targeted to the Managed Server continue to target that server, the application deployment state is preserved. The plan that creates the cluster members automatically stops the Managed Server to add it to the cluster. After the Managed Server is added, the plan restarts the Managed Server.
You can use this procedure to create a new cluster member or you can use this procedure to register an existing cluster member within the provisioning system by selecting the markOnly option.
Before you can create cluster members, the following requirements must be met.
Managed Servers that you plan to convert to cluster members must exist.
For more information, see How to Create a WebLogic Managed Server.
The cluster that you plan to add nodes to must exist.
For more information, see How to Create a WebLogic Cluster.
To create a cluster member, you must belong to a user group that has the Run Component Procedures permission on the folder that contains the component. You must also have the Allow on Host Set permission for the host set on which you plan to deploy the component.
In the Common Tasks section in the browser interface, click WebLogic 8.
Click the Cluster Member Management: Join link.
The plan's Details page displays.
Click Run.
The plan's Run page displays.
Choose the Managed Server that you want to add to the cluster.
Verify that the plan variable WebLogic Cluster Name contains the correct cluster name.
To specify how long the provisioning system waits before verifying that the server was restarted, type the number of seconds in the Seconds to Wait Before Failing Verify Step field.
If you are capturing an existing WebLogic cluster member within the provisioning system, select the markOnly option.
Click Run Plan (Includes Preflight).
This section describes the tasks that are commonly performed with WebLogic servers and clusters after they have been installed.
Domains and Administrative Servers
Clusters
Managed Servers
This section contains procedures for managing WebLogic Domains and Administration Servers.
By removing a WebLogic domain through the provisioning system, you automatically perform the following tasks.
Uninstall the WebLogic AdminServer component and virtual host.
This task removes the Administration Server. If you select the markOnly option, only AdminServer virtual host is removed.
Uninstall all Managed Servers components and virtual hosts that belonged in the domain.
This action also removes the Managed Server within the WebLogic environment unless you select the markOnly option.
Uninstall all cluster components and virtual hosts that belonged in the domain.
This action also removes clusters within the WebLogic environment unless you select the markOnly option.
Remove application components, license configurations, and applications.
The WebLogic virtual hosts cannot contain components that do not belong to the plug-in. To successfully remove the WebLogic domain, all components that do not belong to the plug-in must be removed before running the domain uninstall plan.
To remove a WebLogic domain, you must belong to a user group that has the Run Component Procedures permission on the folder that contains the component. You must also have the Allow on Host Set permission for the host set on which you plan to deploy the component.
In the Common Tasks section in the browser interface, click WebLogic 8.
Click the Domain Management: Remove link.
The plan's Details page displays.
Click Run.
The plan's Run page displays.
Select the target host.
Target the virtual host that was created when you installed the WebLogic software. See How to Install the WebLogic Software procedure.
The target host must be a member of the com.sun.weblogic#InstallHS host set.
Type the name of the WebLogic domain, in the WebLogic Domain Name field.
If you want to remove the WebLogic domain, Administration Server, clusters, and Managed Server from the provisioning system and plan to keep the domain running in the WebLogic environment, select the markOnly option.
Click Run Plan (Includes Preflight).
In the Common Tasks section in the browser interface, click WebLogic 8.
Click the Domain Management: Start link.
The component Details page displays.
In the Component Procedures list, select the row containing the StartAdminServer procedure and click Run.
The plan's Run page displays.
Select the Admin Server that you need to start.
Managed Servers follow the format host (install-path), where host represents the name of the physical host and domain name and install-path represents the name of the . The Admin server name displays as server_wls_managedServerName, for example, server_weblogic (admin_wls)
Click Run Selected Installations.
The plan's Run page displays.
Set the Plan Variables.
(Optional) To override the standard memory arguments passed to Java, type the name in the VmArgs field.
The format used for the vmArgs field is —virtualMachineName. For example, -Xms32m -Xmx200m.
To specify how long the provisioning system waits before verifying that the server started, type the number of seconds in the Seconds to Wait Before Failing Verify Step field.
Click Run Plan (Includes Preflight).
The following section describes how to start, stop, and remove clusters.
When you start or stop a cluster, you start or stop all cluster members within the cluster.
In the Common Tasks section in the browser interface, click WebLogic 8.
Click the Cluster Management: Start or Stop link.
The component Details page displays.
In the Component Procedures list, select the row containing the Start or Stop procedure and click Run.
The plan's Run page displays.
Select the cluster that you plan to start or stop.
The cluster name is a part of the installPath.
Click Run Selected Installations.
The plan's Run page displays.
Click Run Plan (Includes Preflight).
When you remove a cluster, all cluster members associated with that cluster are also removed. .
For more information about the behavior of cluster members returning to the role of Managed Servers, see How to Remove a WebLogic Cluster Member.
When the Managed Servers are removed from the cluster, they are stopped. If you plan to continue using the Managed Server, you must restart it. See How to Start a Managed Server
To remove a cluster, you must belong to a user group that has the Run Component Procedures permission on the folder that contains the component. You must also have the Allow on Host Set permission for the host set on which you plan to deploy the component.
In the Common Tasks section in the browser interface, click WebLogic 8.
Click the Cluster Management: Remove link.
The plan's Details page displays.
Click Run.
The plan's Run page displays.
In the Target Host field, select the domain that hosts the cluster.
In the WebLogic Cluster Name field of the Plan Variables section, type the cluster name that would display in the WebLogic interface.
Select the markOnly option if you want to remove the WebLogic Cluster from the provisioning system but plan to keep the cluster running in the WebLogic environment.
Click Run Plan (Includes Preflight).
When you remove a cluster member, the cluster member component is removed from the Managed Server and the Managed Server that acted as the cluster member returns to its original state. Applications that were targeted to the cluster, and therefore cluster members, are no longer hosted by the Managed Server after it is restarted. Applications targeted directly to the Managed Server continue to target the Managed Server.
When a Managed Server is removed from a cluster, the Managed Server is left in a stopped state. If you plan to continue using the Managed Server, you must restart it. See How to Start a Managed Server.
To remove a cluster member, you must belong to a user group that has the Run Component Procedures permission on the folder that contains the component. You must also have the Allow on Host Set permission for the host set on which you plan to deploy the component.
In the Common Tasks section in the browser interface, click WebLogic 8.
Click the Clusters Member Management: Leave link.
The plan's Details page displays.
Click Run.
The plan's Run page displays.
Choose the Managed Server that you plan to remove.
If you want to remove the WebLogic cluster member from the provisioning system but plan to keep the cluster member running in the WebLogic environment, select the markOnly option.
Click Run Plan (Includes Preflight).
To start a Managed Server, you must belong to a user group that has the Run Component Procedures permission on the folder that contains the component. You must also have the Allow on Host Set permission for the host set on which you plan to deploy the component.
In the Common Tasks section in the browser interface, click WebLogic 8.
Click the Application Server Management: Start link.
The component Details page displays.
In the Component Procedures list, select the row containing the Start procedure and click Run.
The plan's Run page displays.
Select the Managed Server that you need to start.
Managed Servers follow the format host (install-path), where host represents the name of the physical host and install-path represents the name of the managed server. The managed server name displays as server_wls_managedServerName, for example, server_wls_Server-One
Click Run Selected Installations.
The plan's Run page displays.
Set the Plan Variables.
(Optional) To override the standard memory arguments passed to Java, type the name in the VmArgs field.
The format used for the vmArgs field is —virtualMachineName. For example, -Xms32m -Xmx200m.
To specify how long the provisioning system waits before verifying that the server started, type the number of seconds in the Seconds to Wait Before Failing Verify Step field.
Click Run Plan (Includes Preflight).
To stop a Managed Server, you must belong to a user group that has the Run Component Procedures permission on the folder that contains the component. You must also have the Allow on Host Set permission for the host set on which you plan to deploy the component.
In the Common Tasks section in the browser interface, click WebLogic 8.
Click the Application Server Management: Stop link.
The component Details page displays.
In the Component Procedures list, select row containing the Stop procedure and click Run.
The plan's Run page displays.
Select the Managed Server that you need to start.
Managed Servers follow the format host (install path), where host represents the name of the physical host and install path represents the name of the managed server. The managed server name displays as server_domainName_managedServerName. For example, server_wls_Server-One.
Click Run Selected Installations.
The plan's Run page displays.
Click Run Plan (Includes Preflight).
In the Common Tasks section in the browser interface, click WebLogic 8.
Click the Application Server Management: Remove link.
The plan's Details page displays.
Click Run.
The plan's Run page displays.
Select the Managed Server that you plan to remove.
Modify the plan variables if necessary.
Type the name of the WebLogic Managed Server.
Type the name of the WebLogic domain that the Managed Server is registered with.
If you want to remove the WebLogic Managed Server from the provisioning system but want to keep the Managed Server running in the WebLogic environment, select the markOnly option.
Click Run Plan (Includes Preflight).
In the Common Tasks section in the browser interface, click WebLogic 8.
Click the Application Server Management: Start link.
The component Details page displays.
In the Component Procedures list, select the row containing the setAdditionalClasspath procedure and click Run.
The plan's Run page displays.
Select the Managed Server that you plan to update.
Managed Servers follow the format host (install path), where host represents the name of the physical host and install path represents the name of the managed server. The managed server name displays as server_domainName_managedServerName. For example, server_wls_Server-One.
Click Run Selected Installations.
The plan's Run page displays.
Type the additional CLASSPATH elements.
The additional CLASSPATH elements will be added to the default CLASSPATH, which is defined in the WebLogic Managed Server startup script. This startup script was defined when the Managed Server was created. See How to Create a WebLogic Managed Server.
For Windows systems, use a semicolon (;) to separate additional CLASSPATH elements, and use the backslash character (/) as a file separator. For example, c:/files/a1.jar;c:/files/a2.jar;c:/files/b1.jar
(Optional) If you want the new classpath elements to take effect immediately, select Restart Server.
Click Run Plan (Includes Preflight).
The WebLogic Common Tasks page enables you to capture, configure, and deploy WebLogic Enterprise, EJB technology, and Web Applications.
You can perform several specific tasks, as described in the following sections:
Do not deploy or manage your WebLogic applications outside of the Sun N1 Service Provisioning System. If you use the provisioning software, you must manage your WebLogic applications exclusively with the provisioning software.
In the Common Tasks section in the browser interface, click WebLogic.
Click the Enterprise Applications (EAR): Create link.
(Optional) Type a label for this component.
(Optional) Type a description for this component.
Choose how you plan to import the application.
For more information, see Browsing for an Enterprise Application.
Navigate through the hierarchy to find the enterprise application to capture.
Click Check-in Selected Item.
Confirm the information on the check-in page, then click Continue to Check-in.
In the Common Tasks section in the browser interface, click WebLogic.
Click Create in the Web Applications (WAR) section of the WebLogic Common Tasks page.
(Optional) Type a label for this component.
(Optional) Type a description for this component.
Choose how you plan to import the application.
For more information, see Browsing for a Web Application.
Navigate through the hierarchy to find the web application to capture.
Click Check-in Selected Item.
Confirm the information on the check-in page, then click Continue to Check-in.
In the Common Tasks section in the browser interface, click WebLogic.
Click Create in the Java Archives Containing EJBs (JAR) section of the WebLogic Common Tasks page.
Type a label for this component.
Type a description for this component.
Choose how you plan to import the JAR file.
For more information, see Browsing for a JAR or EJB File.
Navigate through the hierarchy to find the JAR file to capture.
Click Check-in Selected Item.
Confirm the information on the check-in page, then click Continue to Check-in.
The WebLogic 8 Plug-In includes several WebLogic-specific component types. These component types enable you to quickly model many of the most common WebLogic application components and to automatically associate install, uninstall, export, and snapshot behavior with a particular resource. Many of the component types are used by the software when you create and manage servers and clusters. As a result, you will only work with a few component types on a regular basis.
However, based on the needs of your application, you might need to configure the WebLogic services before you can deploy the application components. To configure the services, you might need to rely on the component types that are described in the following sections:
These configuration component types are only necessary if your application requires them. For example, if your web application uses a database to retrieve and store information, you will need to configure a connection pool and data source or transactional data source.
To use these configuration component types, select the task that you want to perform and run the associated component procedure. If you need to create and check-in a new component based on an existing component elsewhere on your file system, click Create. After checking in the new component, you can run the appropriate component procedure to configure the WebLogic environment according to your application's needs.
You usually configure and deploy these configuration component types before deploying your application. However, you can configure the WebLogic environment after the application components have been deployed by restarting the application after configuration is complete. Redeploy the application to restart it.
For more information about configuring these configuration objects, see BEA's Administration Console Online Help.
A component of this type models an enterprise application. The component can contain either an enterprise application archive (EAR) or the expanded version of an EAR as a package.
You can use one of the following browsers to select your enterprise application for this component type:
A WebLogic Administration Server browser from which you can select one of the installed applications and its relevant settings. The Administration Server browser provides an alphabetical list of enterprise applications on the Administration Server. You can choose one enterprise application for a component.
A file system browser from which you can select the EAR file to create a component that does not include settings. The file system browser provides a list of files and directories from which you can choose. You can choose to see only those files or type *.ear in the browser.
To install an enterprise application component, you must use a WebLogic Managed Server or cluster as the target host. The installation process performs three main tasks:
Installs the EAR file on the target.
Registers the EAR with the WebLogic Administration Server.
Applies any properties previously captured during domain browse.
You can install the enterprise application by navigating to the application's component Details page and running the Install component procedure.
When you uninstall an enterprise application component, the enterprise application no longer targets the virtual host. If the enterprise application is not targeted elsewhere, the registration component is removed from the Administration Server.
You can uninstall the enterprise application by navigating to the application's component Details page and running the Uninstall component procedure.
Action |
Condition |
Result |
---|---|---|
Install |
The topology is incorrectly configured (target host does not point at correct domain host) |
Targeting fails |
Install |
The target host is not a valid WebLogic target |
Installation prohibited |
Browsing/Install/Uninstall |
Credentials are not properly configured |
Operation fails |
Browsing |
Path not correctly configured in domain host |
Browsing fails |
A component of this type includes a web application. The component can contain either a web application and its relevant settings or the web application without its settings.
You can use one of the following browsers to select your web application for this component type:
A WebLogic Administration Server browser from which you can select one of the installed applications and its relevant settings. The Administration Server browser provides an alphabetical list of web applications on the Administration Server. You can choose one web application for a component.
A file system browser from which you can select the WAR file to create a component that does not include settings. The file system browser provides a list of files and directories from which you can choose. You can choose to see only those files or type *.war in the browser.
To install a web application component, you must use a WebLogic Managed Server or cluster as the target host. The installation process will install the component on that target, and install the contained registration component on the Administration Server of the target.
You can install the web application by navigating to the application's component Details page and running the Install component procedure.
When you uninstall a web application component, the web application no longer targets the virtual host. If the web application is not targeted elsewhere, the registration component is removed from the Administration Server.
You can uninstall the web application by navigating to the application's component Details page and running the Uninstall component procedure.
Action |
Condition |
Result |
---|---|---|
Install |
The topology is incorrectly configured (target host doesn't point at correct domain host) |
Targeting fails. |
Install |
The target host is not a valid WL target. |
Installation prohibited. |
Browsing/Install/Uninstall |
Credentials aren't properly configured. |
Operation fails. |
Browsing |
Path not correctly configured in domain host. |
Browsing fails. |
You can use one of the following browsers to select your EJB or JAR files for this component type:
A WebLogic Administration Server browser from which you can select one of the installed applications and its relevant settings. The Administration Server browser provides an alphabetical list of applications on the Administration Server. You can choose one EJB for a component.
A file system browser from which you can select the JAR file to create a component that does not include settings. The file system browser provides a list of files and directories from which you can choose. You can choose to see only those files or type *.jar in the browser.
When you install a component of this type, the file or directory is copied to the file system based on the install path. Once that copy finishes, the file or directory is registered with the WebLogic Administration Server.
You can install the JAR or EJB file by navigating to the application's component Details page and running the Install component procedure.
When you uninstall a component of this type, the file or directory is removed from the master server.
You can uninstall the JAR or EJB file by navigating to the component Details page and running the Uninstall component procedure.
Action |
Condition |
Result |
Uninstall |
A dependant WebLogic EJB is still installed. |
Uninstall fails indicating the dependency. |
You can use a WebLogic Administration Server browser from which you can select a connection pool and its relevant settings. The Administration Server browser provides an alphabetical list of applications on the Administration Server.
The WebLogic plug-in also includes a default connection pool component called WLJDBCConnectionPoolConfig. This default component eliminates the need for browsing. You can find the default component in the /com/sun/webLogic8 folder or by selecting View All from the Common Tasks page. The default component can then be installed through the component Details page using the Default: Install component procedure.
When you install a component of this type, the file or directory is copied to the file system based on the install path. Once that copy finishes, the file or directory is registered with the WebLogic Administration Server.
You can install the connection pool by navigating to the component Details page and running the Install component procedure.
You must set the following required variables before installing the connection pool:
Pool name
URL
Driver
Database name
User
Password
When you uninstall a component of this type, the file or directory is removed from the Master Server.
You can uninstall the connection pool by navigating to the component Details page and running the Uninstall component procedure.
You can use a WebLogic Administration Server browser from which you can select the data source or transaction data source and its relevant settings. The Administration Server browser provides an alphabetical list of applications on the Administration Server.
The WebLogic plug-in also includes a default data source and transaction data source, which eliminates the need for browsing. You can find the default components in the /com/sun/webLogic8 folder or by selecting View All from the Common Tasks page. The default components can then be installed through the component Details page using the Default: Install component procedure. The default components are named as follows:
WLDataSourceConfig – the data source component
WLTxDataSourceConfig – the transactional data source component
When you install a component of this type, the file or directory is copied to the file system based on the install path. Once that copy finishes, the file or directory is registered with the WebLogic Administration Server.
You can install the data source or transaction data source by navigating to the component Details page and running the Install component procedure.
Before you install a data source or transaction data source component, a connection pool component must already be installed.
You must set the following required variables before installing the data source or transaction data source:
Data Source or Transaction Data Source name
Java Naming and Directory Interface™ (JNDI™) name
Pool name
When you uninstall a component of this type, the file or directory is removed from the master server.
You can uninstall the data source or transaction data source by navigating to the component Details page and running the Uninstall component procedure.
You can use a WebLogic Administration Server browser from which you can select a Multi Pool and its relevant settings. The Administration Server browser provides an alphabetical list of applications on the Administration Server.
The WebLogic plug-in also includes a default multi pool component called WLJDBCMultiPoolConfig. This default component eliminates the need for browsing. You can find the default component in the /com/sun/webLogic8 folder or by selecting View All from the Common Tasks page. The default component can then be installed through the component Details page using the Default: Install component procedure.
When you install a component of this type, the file or directory is copied to the file system based on the install path. Once that copy finishes, the file or directory is registered with the WebLogic Administration Server.
You can install the multi pool by navigating to the component Details page and running the Install component procedure.
You must set the following required variables before installing the multi pool:
Multi Pool name
Algorithm type
Pool List – A pipe-separated (|) list of connection pools.
When you uninstall a component of this type, the file or directory is removed from the Master Server.
You can uninstall the Multi Pool by navigating to the component Details page and running the Uninstall component procedure.
When you install a component of this type, the file or directory is copied to the file system based on the install path. Once that copy finishes, the file or directory is registered with the WebLogic Administration Server.
You can install the thread pool by navigating to the component Details page and running the Install component procedure.
You can edit the plan parameter variable settings.
When you uninstall a component of this type, the file or directory is removed from the Master Server.
You can uninstall the thread pool by navigating to the component Details page and running the Uninstall component procedure.
When you install a component of this type, the file or directory is copied to the file system based on the install path. Once that copy finishes, the file or directory is registered with the WebLogic Administration Server.
You can install the transaction service by navigating to the component Details page and running the Install component procedure.
You can edit the plan parameter variable settings.
When you uninstall a component of this type, the file or directory is removed from the Master Server.
You can uninstall the transaction service by navigating to the component Details page and running the Uninstall component procedure.
You can use a WebLogic Administration Server browser from which you can select a JMS Server and its relevant settings. The Administration Server browser provides an alphabetical list of applications on the Administration Server.
The WebLogic plug-in also includes a default JMS server component called WLJMSServerConfig. This default component eliminates the need for browsing. You can find the default component in the /com/sun/webLogic8 folder or by selecting View All from the Common Tasks page. The default component can then be installed through the component Details page using the Default: Install component procedure.
When you install a component of this type, the file or directory is copied to the file system based on the install path. Once that copy finishes, the file or directory is registered with the WebLogic Administration Server.
You can install the JMS Server by navigating to the component Details page and running the Install component procedure.
You must set the required JMS Server name variable before installing the JMS Server.
When you uninstall a component of this type, the file or directory is removed from the Master Server.
You can uninstall the JMS Server by navigating to the component Details page and running the Uninstall component procedure.
You can use a WebLogic Administration Server browser from which you can select a JMS queue and its relevant settings. The Administration Server browser provides an alphabetical list of applications on the Administration Server.
The WebLogic plug-in also includes a default JMS Queue component called WLJMSQueueConfig. This default component eliminates the need for browsing. You can find the default component in the /com/sun/webLogic8 folder or by selecting View All from the Common Tasks page. The default component can then be installed through the component Details page using the Default: Install component procedure.
When you install a component of this type, the file or directory is copied to the file system based on the install path. Once that copy finishes, the file or directory is registered with the WebLogic Administration Server.
You can install the JMS Queue by navigating to the component Details page and running the Install component procedure.
Before you install a JMS Queue component, a JMS Server component must already be installed.
You must set the following required variables before installing the component:
jmsDestName
jmsserverName
jndiName
When you uninstall a component of this type, the file or directory is removed from the Master Server.
You can uninstall the JMS Queue by navigating to the component Details page and running the Uninstall component procedure.
You can use a WebLogic Administration Server browser from which you can select a JMS topic and its relevant settings. The Administration Server browser provides an alphabetical list of applications on the Administration Server.
The WebLogic plug-in also includes a default JMS Topic component called WLJMSTopicConfig. This default component eliminates the need for browsing. You can find the default component in the /com/sun/webLogic8 folder or by selecting View All from the Common Tasks page. The default component can then be installed through the component Details page using the Default: Install component procedure.
When you install a component of this type, the file or directory is copied to the file system based on the install path. Once that copy finishes, the file or directory is registered with the WebLogic Administration Server.
You can install the connection pool by navigating to the component Details page and running the Install component procedure.
Before you install a JMS Topic component, a JMS Server component must already be installed.
You must set the following required variables before installing the component:
jmsDestName
jmsserverName
jndiName
When you uninstall a component of this type, the file or directory is removed from the Master Server.
You can uninstall the JMS topic by navigating to the component Details page and running the Uninstall component procedure.
You can use a WebLogic Administration Server browser from which you can select a JMS File Store and its relevant settings. The Administration Server browser provides an alphabetical list of applications on the Administration Server.
The WebLogic plug-in also includes a default JMS File Store component called WLJMSFileStoreConfig. This default component eliminates the need for browsing. You can find the default component in the /com/sun/webLogic8 folder or by selecting View All from the Common Tasks page. The default component can then be installed through the component Details page using the Default: Install component procedure.
When you install a component of this type, the file or directory is copied to the file system based on the install path. Once that copy finishes, the file or directory is registered with the WebLogic Administration Server.
You can install the JMS File Store by navigating to the component Details page and running the Install component procedure.
You must set the following required variables before installing the component:
jmsFileStoreName
When you uninstall a component of this type, the file or directory is removed from the Master Server.
You can uninstall the JMS File Store by navigating to the component Details page and running the Uninstall component procedure.
You can use a WebLogic Administration Server browser from which you can select a JMS JDBC Store and its relevant settings. The Administration Server browser provides an alphabetical list of applications on the Administration Server.
The WebLogic plug-in also includes a default JMS JDBC Store component called WLJMSJDBCStoreConfig. This default component eliminates the need for browsing. You can find the default component in the /com/sun/webLogic8 folder or by selecting View All from the Common Tasks page. The default component can then be installed through the component Details page using the Default: Install component procedure.
When you install a component of this type, the file or directory is copied to the file system based on the install path. Once that copy finishes, the file or directory is registered with the WebLogic Administration Server.
You can install the JMS JDBC Store by navigating to the component Details page and running the Install component procedure.
You must set the following required variables before installing the component:
jmsJDBCStoreName
When you uninstall a component of this type, the file or directory is removed from the Master Server.
You can uninstall the JMS JDBC Store by navigating to the component Details page and running the Uninstall component procedure.
A JMS connection factory encapsulates connection configuration information and enables JMS applications to communicate with the messaging system.
You can use a WebLogic Administration Server browser from which you can select a JMS connection factory and its relevant settings. The Administration Server browser provides an alphabetical list of applications on the Administration Server.
The WebLogic plug-in also includes a default JMS Connection Factory component called WLJMSConnectionFactoryConfig. This default component eliminates the need for browsing. You can find the default component in the /com/sun/webLogic8 folder or by selecting View All from the Common Tasks page. The default component can then be installed through the component Details page using the Default: Install component procedure.
When you install a component of this type, the file or directory is copied to the file system based on the install path. Once that copy finishes, the file or directory is registered with the WebLogic Administration Server.
You can install the JMS Connection Factory by navigating to the component Details page and running the Install component procedure.
You must set the following required variables before installing the component:
jmsConnectionFactoryName
jndiName
When you uninstall a component of this type, the file or directory is removed from the Master Server.
You can uninstall the JMS Connection Factory by navigating to the component Details page and running the Uninstall component procedure.
You can use a WebLogic Administration Server browser from which you can select a JMS destination key and its relevant settings. The Administration Server browser provides an alphabetical list of applications on the Administration Server.
The WebLogic plug-in also includes a default JMS Destination Key component called WLJMSDestinationKeyConfig. This default component eliminates the need for browsing. You can find the default component in the /com/sun/webLogic8 folder or by selecting View All from the Common Tasks page. The default component can then be installed through the component Details page using the Default: Install component procedure.
When you install a component of this type, the file or directory is copied to the file system based on the install path. Once that copy finishes, the file or directory is registered with the WebLogic Administration Server.
You can install the JMS Destination Key by navigating to the component Details page and running the Install component procedure.
You must set the following required variables before installing the component:
jmsDestinationKeyName
When you uninstall a component of this type, the file or directory is removed from the Master Server.
You can uninstall the JMS Destination Key by navigating to the component Details page and running the Uninstall component procedure.
You can use a WebLogic Administration Server browser from which you can select a mail session and its relevant settings. The Administration Server browser provides an alphabetical list of applications on the Administration Server.
When you install a component of this type, the file or directory is copied to the file system based on the install path. Once that copy finishes, the file or directory is registered with the WebLogic Administration Server.
You can install the mail session by navigating to the component Details page and running the Install component procedure.
You must set the following required variables before installing the mail session:
msName
jndiName
Mail session property – This variable is generated by the WebLogic 8 plug-in, and is set to the value you set for the property of the mail session in the WebLogic console. For example, mail.user.
When you uninstall a component of this type, the file or directory is removed from the Master Server.
You can uninstall the mail session by navigating to the component Details page and running the Uninstall component procedure.
You can use a WebLogic Administration Server browser to select application server configuration objects and their relevant settings. The Administration Server browser provides an alphabetical list of applications on the Administration Server.
The WebLogic plug-in also includes default components, which eliminate the need for browsing. You can find the default component in the /com/sun/webLogic8 folder or by selecting View All from the Configuration Tasks section of the Common Tasks page. The default component can then be installed through the component Details page using the Default: Install component procedure.
The following list contains each WebLogic configuration object that has been modeled as a component type. The list also provides the default component name and the component variables that require custom values.
The default component for this component type is WLDataSourceConfig. Required component variables: Data source name (dataSourceName), JNDI name (jndiName), Pool name (poolName).
The default component for this component type is WLTxDataSourceConfig. Required component variables: Transaction data source name (dataSourceName), JNDI name (jndiName), Pool name (poolName).
The default component for this component type is WLJDBCConnectionPoolConfig. Required component variables: Pool name (name), URL (url), Driver (driverName), Database name (databaseName), User (user), Password (password).
The default component for this component type is WLJDBCMultiPoolConfig. Required component variables: Multi Pool name(multiPoolName), Algorithm type(algorithmType), Pool list – A pipe-separated (|) list of connection pools (poolList).
You cannot browse for an existing thread pool.
You cannot browse for an existing thread pool.
The default component for this component type is WLJMSServerConfig. Required component variables: JMS Server name (jmsServerName).
The default component for this component type is WLJMSQueueConfig. Required component variables: JMS destination name (jmsDestName), JMS Server name (jmsserverName), JNDI name of the JMS destination (jndiName).
The default component for this component type is WLJMSTopicConfig. Required component variables: JMS destination name (jmsDestName), JMS Server name (jmsserverName), JNDI name of the JMS destination (jndiName).
The default component for this component type is WLJMSFileStoreConfig. Required component variables: Name of the JMS file store (jmsFileStoreName).
The default component for this component type is WLJMSJDBCStoreConfig. Required component variables: Name of the JMS JDBC store (jmsJDBCStoreName).
The default component for this component type is WLJMSConnectionFactoryConfig. Required component variables:Name of the JMS connection factory (jmsConnectionFactoryName), JNDI name (jndiName).
The default component for this component type is WLJMSDestinationKeyConfig. Required component variables: Name of the JMS destination key (jmsDestinationKeyName).
No default component exists for this component type.
Required component variables: Mail session name (msName), JNDI name (jndiName), and the variable generated from the WebLogic value of the mail session property.
When you install a component of this type, the file or directory is copied to the file system based on the install path. Once that copy finishes, the file or directory is registered with the WebLogic Administration Server.
You can install the component by navigating to the component Details page and running the Install component procedure. Many components require that you edit certain component variables. See the list of WebLogic configuration component types for variables that require custom values.
When you uninstall a component of this type, the file or directory is removed from the Master Server.
You can uninstall the configuration component by navigating to the component Details page and running the Uninstall component procedure.
You can use a WebLogic Administration Server browser from which you can select a mail session and its relevant settings. The Administration Server browser provides an alphabetical list of applications on the Administration Server.
You can use a file system browser from which you can select the license. The file system browser provides a list of files and directories from which you can choose.
When you install a component of this type, the file or directory is copied to the file system based on the install path. Once that copy finishes, the file or directory is registered with the WebLogic Administration Server.
You can install the license by navigating to the component Details page and running the Install component procedure.
When you uninstall a component of this type, the file or directory is removed from the Master Server.
You can uninstall the license by navigating to the component Details page and running the Uninstall component procedure.
The Avitek Medical Records demonstration is included in the WebLogic 8 Plug-In to illustrate how to provision BEA WebLogic 8 and a custom application. This demonstration runs on the Solaris OS only. All demo-related plans and components exist in the /com/sun/weblogic8/demo/ folder.
To install the demo application, run the installDemoAppPlan plan. This plan sets up the database and configures the JMS and JDBC resources for the managed server. The JMS and JDBC components are created from existing component types.
The InstallDemoAppPlan performs the following tasks.
Starts the PointBase database
Installs the sample JDBC connection pools
Installs the sample JDBC DataSource
Installs the sample JMS JDBC store
Installs the sample JMS server
Installs the sample JMS queues
Installs the sample JMS connection factory
Adds email capabilities to the sample application
Configures the authenticators that are required to log in to the demo application
Before you install the Avitek Medical Records sample application, you must compile the application. Follow these steps.
If you created a domain for the sample application, source the environment script in the sample application domain directory.
# BEA-InstallDirectory/user_projects/domains/medrec/setMedRecEnv.sh |
In the previous example, BEA-InstallDirectory specifies the BEA WebLogic home directory, for example, /export/home/bea.
Change directories to the src directory of the sample application.
# BEA-InstallDirectory/weblogic81/samples/server/medrec/src |
Use the ant build utility to build the sample application source.
# ant |
Create an XML file named package.xml with content that is similar to the following example.
<project name="tutorial" default="package"> <target name="package"> <wlpackage srcdir="/export/home/bea/weblogic81/samples/server/medrec/src/medrecEar" destdir="/export/home/bea/weblogic81/samples/server/medrec/build/medrecEar" toFile="/export/home/bea/weblogic81/samples/server/medrec/dist/medrecEar.ear" /> </target> </project>
In the wlpackage element, change the paths for srcdir, destdir, and toFile to point to the appropriate directories on your system.
Save this file to the BEA-InstallDirectory/weblogic81/samples/server/medrec/src/medrecEar directory.
Repeat Step 4 and Step 5 to create package.xml files for the physicianEar and startupEar directories.
Change the paths for srcdir, destdir, and toFile to point to the appropriate physicianEar and startupEar directories. Save each package.xml file to the appropriate subdirectory of the BEA-InstallDirectory/weblogic81/samples/server/medrec/src directory.
Use the ant build utility in each EAR directory to update the build with the contents of the package.xml file.
# cd BEA-InstallDirectory/weblogic81/samples/server/medrec/src/EAR-dir # ant -f package.xml |
In the previous example, EAR-dir specifies either the medrecEar, the physicianEar or the startupEar directory.
The medrecEar.ear, the physicianEar.ear, and the startupEar.ear files are created in the BEA-InstallDirectory/weblogic81/samples/server/medrec/dist directory.
Before you can run the Avitek Medical Records demonstration, the following procedures must be performed.
You must perform the previous procedures after you install or upgrade to the 3.0 version of the WebLogic 8 Plug-In version 3.0.
Convert the WebLogic demonstration expanded EAR directories to .ear files.
The WebLogic demonstration files are located at BEA-InstallDirectory/weblogic81/samples/server/medrec/dist/. You need to convert the medrecEar, physicialEar, and startupEar directories.
Create components out of the demonstration .ear files.
For more information, see How to Capture a WebLogic Enterprise Application or EAR File.
You need to save your components in a folder that is not owned by the WebLogic 8 plug-in.
Create session variables for the WebLogic application.
Create the following session variable.
Specifies the port to use for the WebLogic application. The value for WL_POINTBASE_PORT can be any open port number. The default value is 9092.
From the Common Tasks page, click Demo Application Configuration: Configure.
The plan Details page displays.
Click Run.
Leave the plan parameter component variables set at the default value.
Select a managed server as the target host.
Install the demo application EAR components.
On the WebLogic plug-in Common Tasks page, click Create in the Enterprise Application (EAR) section.
Navigate to the folder in which you installed the medrecEar.ear component.
Run the component's Default:Install component procedure.
Repeat steps Step b through Step c for the physicianEar.ear and the startupEar.ear components.
View the Avitek Medical Records demonstration applications.
You can see the three demonstration applications at the following urls.
http://RA-hostname:7010/patient
http://RA-hostname:7010/admin
http://RA-hostname:7010/physician
When you work with WebLogic through the provisioning system, you can use two command lines: the Sun N1 Service Provisioning System command line and the WebLogic command line.
By default, the provisioning system's command-line interface is located in the following directory: /opt/SUNWn1sps/N1_Service_Provisioning_system_5.1/cli/bin/cr_cli.
BEA WebLogic 8 plug-in objects are located in the /com/sun/weblogic8 folder.
You can interact with plug-in components and plans much like any other custom component or plan. However, if you want to make changes to the components or plans, you need to save the component or plan to a new folder and make your changes there. For more information about using the provisioning system's command-line interface, see Chapter 1, Using the Command-Line Interface, in Sun N1 Service Provisioning System 5.2 Command-Line Interface Reference Manual
The WebLogic command line is accessible through the WebLogic 8 Common Task page. For more information about the WebLogic 8 command-line interface, see the WebLogic Server Command Reference on BEA's web site.
You can run WebLogic commands on any Administration Server or Managed Server.
In the Common Tasks section in the browser interface, click WebLogic 8.
Select whether you plan to run the command on an Administration Server or a Managed Server.
If you plan to run commands on an Administration Server, click Domain Management: Start.
If you plan to run commands on a Managed Server, click Application Server Management: Start.
The component Details page displays
Select the Run-cli component procedure and click Run.
The plan's Run page displays.
Select the AdminServer virtual host or Managed Server virtual host on which to run the CLI and click Run Selected Installations.
Type the needed information in the plan variable fields.
Many of the plan variables do not require information and can be left blank. The following list describes the optional variables.
This variable can be safely ignored if you do not connect to the server using SSL.
This is the user name variable. The user name and password variables are mutually exclusive with the user-configuration file and key file variables. Supply either the user name and password or the user-configuration file and key file locations.
This is the password variable. The user name and password variables are mutually exclusive with the user-configuration file and key file variables. Supply either the user name and password or the user-configuration file and key file locations.
This is the user-configuration file variable. The user name and password variables are mutually exclusive with the user-configuration file and key file variables. Supply either the user name and password or the user-configuration file and key file locations.
This is the key file variable. The user name and password variables are mutually exclusive with the user-configuration file and key file variables. Supply either the user name and password or the user-configuration file and key file locations.
Click Run Plan (Includes Preflight).
This example uses the WebLogic FORCESHUTDOWN command to illustrate input for each Run-cli plan variable.
Weblogic CLI to run (weblogic.Admin or weblogic.Deployer): |
weblogic.Admin |
The SSL arguments for the command: | |
The listen address of the server instance that runs the command: |
sun03 This is the name of the AdminServer. |
The listen port of the server instance that runs the command: |
7001 |
The name of the user who must have appropriate permission to view or modify the target of the command: |
admin |
The password that is associated with the username: |
xxxxx |
The name and location of a user-configuration file, which contains an encrypted username and password: | |
the name and location of the key file: | |
The name of the command to run: |
FORCESHUTDOWN |
Arguments of the command: |
Server-one |
You can use the WebLogic Server Scripting Tool (WLST) from the provisioning system's browser interface. For information on how to perform administrative tasks and configuration changes using the WLST, see BEA's WebLogic Server Using the WebLogic Server Scripting Tool document.
You must first create the WebLogic script component, then install it.
In the Common Tasks section in the browser interface, click WebLogic 8.
Click the Command Line Interface: Create link.
The component's Edit page displays.
Type the name of the new WebLogic Script component.
(Optional) Type the components label and description.
Select a host that has a copy of the WebLogic script file on its file system.
Navigate through the host's file system and select the file.
Click Check In Selected Item.
The component's Check In page displays.
Select a folder on which you have edit permissions.
Click Continue to Check In.
Before you can install a WebLogic script component, one must exist within the provisioning system. See How to Create a WebLogic Script Component.
In the Common Tasks section in the browser interface, click WebLogic 8.
Click the Command Line Interface: View All link.
The Components page displays.
In the row of the WLScript component that you plan to install, click Details.
The component's Details page displays.
In the Component Procedures table, select the Default: Install procedure and click Run.
The plan's Run page displays.
Select the target host.
You target the AdminServer virtual host.
You do not need to modify the component variables for license installation.
(Optional) Type the name of the WebLogic user who installed the software in the RunAs field.
This user represented by the webLogicUser variable used in the software installation plan.
Click Run Plan (Includes Preflight).
The WebLogic 8 Plug-In relies on plans to perform many of the tasks associated with installing and removing Administration Servers, Managed Servers, and clusters.
BEA WebLogic 8 plug-in plans are located in the /com/sun/weblogic8 folder and linked to from the Common Tasks page.
If you are experiencing problems managing WebLogic through the provisioning software, messages will likely appear on the screen to tell you that a problem exists.
Problems encountered during plan run or preflight The plan (or preflight) "/com/sun/weblogic8/InstallAdminServerPlan" finished with 1 failed host(s). (017034) Unable to find session variable "WL_DEFAULT_PASSWORD" (Unresolved session variable WL_DEFAULT_PASSWORD. This session variable was automatically created when the system was unable to find it.). Add this session variable and try the operation again. (040111) |
Although the message in this example is easily understood, not all messages are this straightforward.
The following message means that the JMX interface on the Administration Server was not available or the login information is wrong.
Admin Server adminHost JMX interface running on port portNumber is not available; Admin Server must be running for this operation. |
To find out more information about the specific problem, follow the Run History Details links until you reach the final error block. View the output of stderr and stdout for details on the error condition.
This section includes examples of error messages that you might encounter during the installation of WebLogic.
The user specified is not a valid system users: weblogic (017056) |
You must create the system user “weblogic” or change the Install variable weblogicUser to an existing user.
Specified target(s) "sol01" were not in the required host set "com.sun.weblogic8#SupportedHS". (017087) |
This error message could result for two reasons:
The host does not support an operating system that is compatible with the plug-in.
If true, select a host that uses an operating system that is supported by the plug-in.
The host has not been prepared.
If true, go to the Hosts page and prepare the host.
Error: Installation could not be preformed check the deployment details for more information. |
You must check the deployment details of the final execNative control to find information from the WebLogic installer.
The following messages are examples of what could be contained in the stdout output.
SilentBEAHomeTask – Access to the directory is denied: [/usr/local/bea]
If this message is displayed, the WebLogic user specified in the installation plan does not have permission to create or write to the beaHome directory. You can change the permissions on the directory or create the beaHome directory using the provisioning system's directory component.
SilentBEAHomeTask – At least one item must be selected.
If this message is displayed, an installation of WebLogic already exists in this path. You must change the path or uninstall the existing WebLogic installation.