Administration Servers

The WebLogic Remote Console can connect directly to a WebLogic Administration Server to view and edit its domain, much like the WebLogic Server Administration Console, though there are some differences.

You can save the connection details for multiple WebLogic Administration Servers, making it easy to switch between domains with a click.

Connect to a WebLogic Administration Server

1. Start the WebLogic Administration Server.

2. Open the Providers drawer and beside the project name, click ⋮. Select Add Admin Server Connection Provider.

3. Enter a name for the Administration Server connection. This is the name that will appear in the Project list of providers so you can identify which provider you’re working on.

4. Enter a username and password for a user account with editing privileges in the selected Administration Server. As with the Administration Console, your management capabilities will be limited depending on the level of access granted to your user account. See Understand access discrepancies for more information. You can choose to have multiple connections to the same Administration Server with different users.

5. Enter the URL for the Administration Server.

   Note: Make sure that the management/* endpoint of your administration server is accessible by the WebLogic Remote Console. If your administration server’s endpoints are behind a load balancer or otherwise externally unavailable, you will need to expose that endpoint manually.

6. Optional:

   • If you want to force WebLogic Remote Console to connect to an Administration Server regardless of warnings about expired, untrusted, or missing certificates, enable the Insecure Connection checkbox. We strongly recommend that you only enable this setting for development or demonstration environments.
   • If you want to facilitate communication between a WebLogic Server domain that resides in a different network and the WebLogic Remote Console, enter a proxy server address in the Proxy Override field. You can also set a proxy address globally that applies to all administration server connections.

7. Click OK to connect the WebLogic Remote Console to the WebLogic Administration Server.

The WebLogic Remote Console is now connected to a WebLogic Administration Server. You can make changes to the domain as desired.

Edit a WebLogic Administration Server

Editing a domain in the WebLogic Remote Console is similar in process to the Administration Console. When you start editing a domain, a configuration lock is created that blocks other users from making simultaneous changes. Once you’re satisfied with your changes, you can activate these changes and perpetuate them to the Administration and Management Servers.

1. Open the Providers drawer and select the Administration Server you want to edit.
2. Click the Edit Tree perspective and make your changes to the domain configuration. Fields marked with require a server restart.
3. Click Save on every page after making your changes.
4. If you have the extension installed, open the Providers drawer and select Shopping Cart to view your changes.
5. Commit your changes. In the upper right corner of the content pane, click and then Commit Changes.
6. Restart your server if necessary.
   1. Check if any servers require a restart on the Monitoring Tree perspective > Environment > Servers page.

Shopping cart

The Shopping Cart (equivalent to the Change List in the WebLogic Server Administration Console) holds all the pending changes for the current session in the WebLogic Remote Console. In the shopping cart, you can see if any changes are pending, commit those changes or discard them entirely.

If you installed the console extension, console-rest-ext-6.0.war, then you can also see the specific changes you’ve made and the status of the lock in the Change Manager.

Open the Shopping Cart menu and click View Changes to see your pending changes.

Some changes can be activated immediately (dynamic) while other changes require a server restart to activate (non-dynamic). When you need to activate non-dynamic changes, navigate to the Environment > Servers node in the Monitoring perspective to see which servers need a restart.

If you need to undo a change, you must discard all Shopping Cart contents or manually revert the change in the Edit Tree perspective.

Edit the connection details of a WebLogic Administration Server

1. Open the Providers drawer and beside the WebLogic Administration Server connection that you want to edit, click the icon.
2. Edit the details of the WebLogic Administration Server. You can change its name in WebLogic Remote Console, switch user accounts or update the URL.
3. Click OK to save your changes.

View the connection details of a WebLogic Administration Server

It’s easy to view the details of a WebLogic Server Connection.

1. Open the Providers drawer and beside the WebLogic Administration Server, click the icon.

A list of connection details will appear, including:

• Provider ID
• Domain Name
• Domain URL
• Domain Version
• Username
• Role

Delete a connection to a WebLogic Administration Server

This will only delete the WebLogic Remote Console access to the WebLogic Administration Server. The domain itself will be unaffected.

1. Open the Providers drawer and beside the WebLogic Administration Server, click the icon.

Create a managed server

1. In the Edit Tree perspective, expand the Environment > Servers node.
2. Click New.
3. Enter a name for the new server.
4. Optional: If you want to copy the settings from an existing server onto your new server, select a server from the Copy settings from another server dropdown. Only the server’s settings will be copied; children, such as channels, are not copied. Any settings that are not supported by the WebLogic Server REST API are also not copied.
5. Click Create.

Control Operations

The WebLogic Remote Console provides control operations for the Administration Server in the Monitoring perspective.

Change server state

Server state indicates the specific condition of a server in the life cycle management.

1. Open the Providers drawer and select a WebLogic Administration Server connection.
2. Choose the Monitoring perspective from the home page.
3. Go to Environment > Servers
4. Choose the action for the server(s):
   • Start
   • Resume
   • Suspend
   • Shutdown
   • Restart SSL
5. Choose when to initiate the action:
   • When work completes
   • Force shutdown now
6. In the dialog box, move the servers whose state you want to change from Available to Chosen.
7. Initiate the action.

Create MBeans

The WebLogic Remote Console includes simplified wizards for deploying applications and creating JDBC system resources.

In most other cases, when you create a new MBean on a page, you are prompted to fill in a few key properties, such as Name, then click Create. Unlike the WebLogic Server Administration Console, the WebLogic Remote Console does not guide you through configuring other properties that you typically need to complete the configuration. Instead, it displays the new bean’s pages where you can click through the tabs to finish configuring the bean.

Application Deployment

You can use the WebLogic Remote Console to manage the deployment process for applications to WebLogic Server.

For more information on the general process for application deployment, see Deploying Applications to Oracle WebLogic Server.

Install an application

When you install an application, you make its physical file or directory known to WebLogic Server. An application can be installed as an archived EAR file or as an exploded directory.

1. In the Edit Tree, navigate to Deployments > App Deployments.
2. Select New.
3. Fill in the required fields.
4. Click Create.
5. Commit your changes.

Your new application appears under the App Deployment node. You can make additional changes to the application on this page.

You must start an application before it can process client requests.

Start an application

You need to start an application to make it available to WebLogic Server clients.

When you start an application, you can make it immediately available to clients, or you can start it in Administration 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.

1. In the Monitoring Tree, navigate to Deployments > Application Management.
2. Select the application that you want to start.
3. Click Start and choose either:
   • Servicing all requests: to make the application immediately available to all clients.
   • Servicing only administration request: to make the application available in Administration Mode only.

Stop an application

When you stop an application, you can choose whether no clients can use it, or 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 a stopped application to make it available to WebLogic Server clients again.

1. In the Monitoring Tree, navigate to Deployments > Application Management.
2. Select the application that you want to stop.
3. Click Stop and choose either:
   • When work completes: to allow the application to finish its work and for all currently connected users to disconnect.
   • Force stop now: to stop the application immediately, regardless of the work that is being performed and the users that are connected.
   • Servicing non-administration requests: to stop the application once all its work has finished, but to then put the application in Administration Mode so it remains accessible for administrative purposes.

View an application’s current state

1. In the Monitoring Tree, navigate to Deployments > Application Management and choose the application whose state you want to view.

Review an application’s runtime statistics

1. In the Monitoring Tree, navigate to Deployments > Application Runtime Data and choose the application for which you want to view runtime information.
2. Explore the child nodes of the selected application to see its various runtime data.

Deployment Plans

You can use a deployment plan to specify deployment property values for an application. A deployment plan is an optional document that works with or overrides your application’s deployment descriptors to configure an application for deployment to a specific WebLogic Server environment. Deployment plans are written in XML.

For more information, see Understanding WebLogic Server Deployment Plans in Deploying Applications to Oracle WebLogic Server.

Create a Deployment Plan

1. In the Monitoring Tree, navigate to Deployments > Application Management and select your application.
2. Click Create Plan.
3. Copy the file path to the deployment plan into the Plan Path field. Deployment plans must be in XML format and should be called plan.xml. It’s recommended that you store a deployment plan for a single application in its own plan/ subdirectory of the application’s root directory.
4. Click Done.

Update a Deployment Plan

You can update a deployment plan with new deployment instructions for an application.

For more information, see Manually Customizing the Deployment Plan in Deploying Applications to Oracle WebLogic Server.

1. In the Monitoring Tree, navigate to Deployments > Application Management > yourApplication > Deployment Plan.
2. You can edit the individual variable assignments within a deployment plan or the deployment plan as a whole:
   • To edit individual variable assignments:
     1. Select the variable assignment module that you want to edit and click Edit.
     2. Enter a value and, if updating an array, choose an operation.
     3. Click Done.
   • To edit a deployment plan document:
     1. Select the Deployment Plan tab.
     2. Edit the deployment plan directly within the text box field or copy and paste the plan into a text editor. Make your edits and then copy and paste it back into the WebLogic Remote Console.
     3. Click Save.
3. Navigate back up to Deployments > Application Management.
4. Select your application and click Update.
5. Optional: Redeploy your application.

Redeploy an application

To redeploy an application with an updated deployment plan.

1. If necessary, follow the instructions at Update a deployment plan to modify an application’s deployment plan.
2. In the Monitoring Tree, navigate to Deployments > Application Management and select your application.
3. Click Redeploy.