2-4 Oracle Fusion Middleware Installation Guide for Application Developer
2.1.3.3 Applying Java Required Files JRF
Java Required Files JRF consists of those components not included in the Oracle WebLogic Server installation and that provide common functionality for Oracle
business applications and application frameworks.
JRF consists of a number of independently developed libraries and applications that are deployed into a common location. The components that are considered part of Java
Required Files include: Oracle Application Development Framework, Oracle Fusion Middleware Audit Framework, Dynamic Monitoring Service, Infrastructure Security,
Java Object Cache, Oracle Platform Security Services, logging, MDS, Oracle Web Services, and Oracle Web Services Manager.
You must apply JRF to a Managed Server or cluster in certain circumstances.You can only apply JRF to Managed Servers that are in a domain in which JRF was configured.
That is, you must have selected Oracle JRF in the Configuration Wizard when you created or extended the domain.
For more information, see Applying Java Required Files to a Managed Server or Cluster in Oracle Fusion Middleware Administrators Guide.
2.1.3.4 Using Custom Port Numbers
By default, the servers that are created in each domain use the same set of port numbers for example, the Administration Server uses port 7001. If you want to use
custom port numbers, you can change the port number when you run the Configuration Wizard:
■
The Administration Server port number can be changed on the Configure Administration Server Screen.
■
The port number for all managed servers in your domain can be changed on the Configure Managed Servers Screen.
Fore more information about port numbers, refer to Port Numbers in Oracle Fusion Middleware Administrators Guide.
Configuring Application Developer 2-5
2.1.4 Extending an Existing Domain
While creating your WebLogic domain, if you chose not to configure all of the components on the Select Domain Source Screen, you can add these components at a
later date by extending your domain. If this is a first time installation or you do not want to add more components, you can skip this section and move to the next section.
Follow the instructions in Extending a WebLogic Domain inOracle Fusion Middleware Creating Domains Using the Configuration Wizard to extend an existing domain.
2.2 Starting the Administration Server
To get your deployments up and running, you must start the Administration Server by running the startWebLogic.sh on UNIX operating systems or
startWebLogic.cmd on Windows operating systems script in the directory where
you created your new domain. On UNIX systems:
DOMAIN_HOME
startWebLogic.sh
On Windows systems: DOMAIN_HOME
\startWebLogic.cmd
You entered the domain name and location on the Specify Domain Name and Location Screen in the Configuration Wizard.
2.3 Verifying the Installation
To verify the installation, start your browser and enter the following URLs:
■
To access the Administration Server console:
http:
administration_server_host
:
administration_server_port
console
■
If you configured your Administration Server to accept SSL connection, use the following URL to access the Administration Server console in secure mode:
https:
administration_server_host
:
secure_administration_server_port
console
■
To access Enterprise Manager:
http:
administration_server_host
:
administration_server_port
em
Note: Before proceeding, make sure that schemas exist in your
database for the components you are configuring when you extend the domain. For example, if you are planning to extend the domain
and configure Oracle WSM Policy Manager, then make sure the required schema for this component MDS exists in your Oracle
database before you continue.
2-6 Oracle Fusion Middleware Installation Guide for Application Developer
Deinstalling Application Developer 3-1
3
Deinstalling Application Developer
This chapter describes how to remove Application Developer and related products from your system.
You should always use the instructions provided in this chapter for removing the software. If you try to remove the software manually, you may experience problems
when you try to reinstall the software again at a later time. Following the procedures in this chapter will ensure that the software is properly removed. See Section 3.2,
Reinstallation for more information.
The following topics are covered:
■
Section 3.1, Deinstallation Instructions
■
Section 3.2, Reinstallation
3.1 Deinstallation Instructions
The deinstaller will attempt to remove the Oracle Home from which it was started; for Application Developer, this directory is the oracle_common directory. This
procedure will not remove any WebLogic domains that you have created - it only removes the software in oracle_common.
Before you choose to remove this directory, make sure that it is not in use by an existing domain, and also make sure you stop all running processes that use the
oracle_common directory. After you remove the software, you will no longer be able
to use your WebLogic domain. Deinstalling Application Developer properly involves the following tasks:
■
Stopping Oracle Fusion Middleware
■
Removing the Application Developer Schemas
■
Removing Application Developer
■
Manually Removing the Oracle Home Directory
■
Removing Oracle WebLogic Server
■
Removing Oracle JDeveloper
■
Removing Program Groups Windows Only
■
Rebooting Your System Windows Only
Kategori