Establishing production environment is the final, but probably the most important step in the application’s life cycle. Production environment for ADF application implies application server, but also various settings and resources. As each version of ADF becomes more demanding, it is necessary to follow certain procedures in establishing ADF production environment. This blog will describe the procedure of installation of ADF 188.8.131.52.0 on WebLogic 10.3.5.
ADF technology requires establishment of the environment within which applications can be executed. The “environment” is used to refer to a group of jar files that must be available as a library on WebLogic server. The number of jar files has grown over time and “environment” has begun to refer to the startup and shutdown classes and configuration of server instances. In other words, “environment” is increasingly complex and without well-defined procedures it is impossible to make ADF application work properly.
New ADF version, Oracle ADF 184.108.40.206.0, made things even more complicated. For the first time ADF version and WebLogic server version (version 10.3.5) are not synchronized, so in process of ADF installation, it is necessary to patch WebLogic Server in order to successfully install environment.
For starters, I would like to show you how it once was. The reason is simple. It is still possible to do it old fashion way and everything will seem fine. But that’s all.
The old fashion way is to start the installing JDeveloper. Selecting an existing domain directory and the ADF Runtime as a component for installation is all you have to do to pass the installation procedure. Upon completion of the installation, you will extend your WebLogic domain with new components and the ADF runtime is installed. This is still possible, but it will not be enough. Deploying the application mistakes will appear to suggest that something went wrong.
So what is the proper way to do it? A series of steps will have to be taken:
- Install WebLogic
- Configure Managed Servers
- Install the ADF Runtime
- Extend domain
- Apply the JRF template
- Install the WebLogic patches
It will be assumed that WebLogic has already been installed and that the managed server which will run ADF applications has been created. In this case it is necessary to shut down all servers on the domain, install and run ADF Runtime installer for version 220.127.116.11, available on http://www.oracle.com/technetwork/developer-tools/adf/downloads/index.html.
The installation process will ask for Middleware home, and its completion will do the following:
- In the middleware directory it will create oracle_common directory
- WebLogic will have everything necessary to be able to extend domains with new functionalities
Installing ADF Runtime
So you should extend the domain. Domain is extended with three components (as shown in the picture) that will:
- Install the EM console on the server admin
- Install all the necessary library, shutdown / startup class, and other configuration to the WebLogic domain
The extending domain will not allow for the specific managed server to use ADF Runtime. To enable specific managed server to use ADF Runtime, the EM console should be used. Log onto EM console (available at http://WLS_SERVER:ADMIN_SERVER_PORT/em) using the same credential you used for AdminServer console and select the specific managed server in a tree structure on the left. Action JRF APPLY TEMPLATE will become available. Use it to complete the ADF Runtime installation.
Applying JRF template
However, due to disconnection of the new ADF and Weblogic versions, this is not enough. The next step is to patch WebLogic. Patches 12611176 and 12556632 (available from OTN) must be applied in order specified by “opatch apply” command (opatch tools comes with the ADF runtime installation and are located in the folder oracle_common!!).
After that, it is necessary to shutdown the target domain servers. Execute “wlst.sh” or “wls.cmd” (depending on your OS), that you find in your <Middleware_HOME>/oracle_common/common/bin/ directory. Then run the “upgradeADF(‘<your Domain Path>’)” command in offline mode. Restart the servers and it is all done!
And in the end you could check that everything (ADF libraries) is properly targeted. In case of using node manager, it is necessary to adjust it to using a startup / shutdown script. Of course, the successful test would be deploying of ADF applications.