Oracle Forms and Reports 12c step by step installation

Oracle Forms12c step by step installation

Oracle Forms12c installation and configuration:

The following steps should be performed successfully:

·         Install database12c

·         Configure a pluggable database 

·         Install Oracle WebLogic Server (FMW Infrastructure) 

·         Install Oracle Forms12c 

·         Run Repository Creation Utility 

·         Configure Forms12c Using the Config Wizard 

·         Configure Reports12c 

·         Post installation test 

·         Reviewing System Requirements and Specifications

Before performing any installation you should read the system requirements documentation to ensure that your environment meets the minimum installation requirements for the products you are installing.

The system requirements document covers information such as hardware and software requirements, database schema requirements, minimum disk space and memory requirements, and required system libraries, packages, or patches. This document can be found on the Oracle Fusion Middleware System Requirements and Specifications page.

·         Reviewing Certification Information

Before performing any upgrade or installation you should read the Oracle Fusion Middleware certification document for your particular release. It is located on the Oracle Fusion Middleware Supported System Configurations

Download required softwares:

·         Oracle Forms: Oracle Forms and Reports 12c (12.2.1.2) Released October 2016

·         Oracle Database 12c Release 1

Step1: OracleDatabase12C -Installation

Step1: OracleDatabase12C -Installation

Change the characterSet for Forms Applications

Configure a pluggable database

Configure a pluggable database

After installing oracle database12c, we configure a pluggable database which is part of Forms12c installation

Run dbca.bat in a windows-shell command or run command interface as administrator

Or choose database configuration assistant menu option as shown in this screen OR 

Oracle WebLogic Server (FMW Infrastructure) installation

Oracle WebLogic Server (FMW Infrastructure) installation

Locate java.exe on your computer and run as administrator the following command in a dos-window

 

Forms12c and Reports12c-installation

Forms12c and Reports12c-installation

Run as administrator

This page prompts you to choose or not software updates for your components. Choose no and click Next.

Specify the Oracle home location to install the product

Choose Forms and Reports Deployment to install all of the products. Click Next.

The Prerequisites Checks page appears – We have a warning about VisualC++, click Next

Installation Summary

RCU – configuration

RCU – configuration

Start rcu.bat as administrator.

Forms12c-Configuration and Weblogic Domain creation

Configuring Forms Using the Config Wizard

In order to complete the configuration, open a Windows DOS shells as administrator and run the config wizard located in <ORACLE_HOME>/oracle_common/common/bin

The Templates screen appears, choose the selected components

Enter the WebLogic Domain administration username and password required to access WebLogic Server Control and Fusion Middleware Control.

Choose production and leave the default JDK. 

Enter the RCU DB connection information. Service for pluggable databse, hostname and password 

JDBC Component Schema Test screen. 

JDBC Component Schema Test: Results

Schéma de composant=LocalSvcTbl Schema
Pilote=oracle.jdbc.OracleDriver
URL=jdbc:oracle:thin:@//linecode:1521/ORAPLG1
Utilisateur=DEV_STB
Mot de passe=*********
Test SQL=SELECT 1 FROM DUAL

CFGFWK-64213: Le test a abouti.
CFGFWK-64213: Le test de la connexion JDBC a réussi.
CFGFWK-64213: Aucune action requise.

Schéma de composant=OPSS Audit Schema
Pilote=oracle.jdbc.OracleDriver
URL=jdbc:oracle:thin:@//linecode:1521/ORAPLG1
Utilisateur=DEV_IAU_APPEND
Mot de passe=*********
Test SQL=ISVALID

CFGFWK-64213: Le test a abouti.
CFGFWK-64213: Le test de la connexion JDBC a réussi.
CFGFWK-64213: Aucune action requise.

Schéma de composant=OPSS Audit Viewer Schema
Pilote=oracle.jdbc.OracleDriver
URL=jdbc:oracle:thin:@//linecode:1521/ORAPLG1
Utilisateur=DEV_IAU_VIEWER
Mot de passe=*********
Test SQL=select 1 from schema_version_registry where owner=(select user from dual) and mr_type=’IAU_VIEWER’ and version like ‘12.2.1%’

CFGFWK-64213: Le test a abouti.
CFGFWK-64213: Le test de la connexion JDBC a réussi.
CFGFWK-64213: Aucune action requise.

Schéma de composant=OPSS Schema
Pilote=oracle.jdbc.OracleDriver
URL=jdbc:oracle:thin:@//linecode:1521/ORAPLG1
Utilisateur=DEV_OPSS
Mot de passe=*********
Test SQL=select 1 from schema_version_registry where owner=(select user from dual) and mr_type=’OPSS’ and version like ‘12.2.1%’

CFGFWK-64213: Le test a abouti.
CFGFWK-64213: Le test de la connexion JDBC a réussi.
CFGFWK-64213: Aucune action requise.

Reports12C – Configuration

Reports12C – Configuration

 

Before opening Reports builder you have to perform these additional steps:

·         Execute wlst.cmd from C:\app\oracle\product\12.2.1\oracle_common\common\bin

·         Connect to AdminServer. connect(weblogic,your_passwd,your_hostename:7001)
Run the following wlst command.
createReportsToolsInstance(instanceName=’reptools1′,machine=’AdminServerMachine’)

·         Restart WLS_REPORTS
After completing the previous steps, reports builder can be used.

·         run rwbuilder.bat from C:\app\oracle\config\domains\frs\reports\bin\rwbuilder.bat

Standalone Reports Server instance if required to print reports and change the rwservlet.properties file for in process reports set “NO”

createReportsServerInstance(instanceName='omnibus_test_rs1',machine='machine_gotsvol2018')

Forms&Reports12c – Post installation test

Forms12c and Reports12c:  Post installation and configuration test.

 

Modify your tnsnames.ora-file

<ORACLE_HOME>\user_projects\domains\base_domain\config\fmwconfig

#
#
# sample tnsnames.ora file
# sample entry
#<ALIAS> = (DESCRIPTION =(ADDRESS_LIST =
# (ADDRESS = (PROTOCOL = TCP)
# (HOST = <HOST>)(PORT = <PORT>)))
# (CONNECT_DATA = (SID = <SID>)))
#

# Connect to oracle12c database

ORACLE12C =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = linecode)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = oracle12c)
)
)

Start your servers

·         startNodeManager

·         startWeblogic

·         StartManagedWeblogic (your_web_ser_name)

Enabling Auto Login by Using the Boot Identity File

Enabling Auto Login by Using the Boot Identity File

During a startup or shutdown of a WebLogic instance (AdminServer, Forms or Reports), the server prompts you to enter a username and a password. You can use a boot identity file to enable auto-login without providing login information. A boot identity file is more secure than storing unencrypted information in a startup or shutdown script. The boot identity file can be different for each server instance in the domain.

First, locate your server’s instances on your operating systems:
<ORACLE_HOME>\user_projects\domains\base_domain\servers

·         AdminServer

·         WLS_FORMS

·         WLS_REPORTS

(.) Create a text-file with the following information:
username=weblogic_usrn    
password=weblogic_passwd
(.) Create a folder and name itsecurity.
(.) Save the text-file as boot.properties
(.) Restart your servers

Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server

Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server

If you want to start automatically  weblogic server instances when you boot a windows host computer, you can create specific windows services.
For each server instance for which a windows service is set, the weblogic server creates a key in  the Windows Registry under  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services.
After the windows host is started, the Microsoft Management Console (MMC) uses the information in this key to invoke the weblogic server intance.
InstallSvc.cmd is the script containing the variables used to install WebLogic Server as a Windows Service.
Some of variables need to be set before running the script. (For more details see, oracle doc)

WL_HOME                       - The root directory of your WebLogic installation

JAVA_HOME                    - Location of the version of Java used to start WebLogic 

WLS_USER                     - admin username for server startup

WLS_PW                         - cleartext password for server startup

ADMIN_URL                    - admin_url

PRODUCTION_MODE    - set to true for production mode servers, false for wait until the Weblogic Server is started.

HOST                               - IP address of the Weblogic Server  

PORT                               - Port number where the WebLogic Server is listening for requests 

Example of script to set up AdminServer as Windows Service.

---

SETLOCAL

set DOMAIN_NAME=base_domain

set USERDOMAIN_HOME=<ORACLE_HOME>\user_projects\domains\base_domain

set DOMAIN_HOME=<ORACLE_HOME>\user_projects\domains\base_domain

set SERVICE_DESCRIPTION=setting_Up_AdminServer_as_windows_service

set SERVER_NAME=AdminServer

set host=host_name

set port=port_number

set PRODUCTION_MODE=false

set MW_HOME=<ORACLE_HOME>\wlserver

set WLS_USER=wls_user

set WLS_PW=wls_pwd

set JAVA_HOME=<java_home>

set MEM_ARGS=your_mem_arg

set ADMIN_URL=your_admin_url

rem call %USERDOMAIN_HOME%\bin\setDomainEnv.cmd

call "%<ORACLE_HOME>%\wlserver\server\bin\installSvc.cmd"

ENDLOCAL

---

Start the AdminServer Microsoft Management Console

Description set in the script 

-- set SERVICE_DESCRIPTION=setting_Up_AdminServer_as_windows_service

Just modify your script if you want to create weblogic - reports & Forms instances as windows services.

Using graphs and Charts in Forms12C

Using graphs in Forms12C

 

This demo shows the integration of the Oracle BI Bean Graph in Forms.
Graphs are populated using the PJC.
Type of Graphs in this demo are: Simple Graph, interactive Graph and Separate Frame.

·         First, download the demo Download demo from Oracle

·         Sign the FormsGraph.jar – file

·         Copy it into <Oracle_Home>/forms/java

·         Modify your formsweb.cfg – file by adding FormsGraph.jar to archive tag

# Forms applet archive setting for other clients (Sun Java Plugin, Appletviewer, etc)
archive=frmall.jar,jacob.jar,FormsGraph.jar,frmwebutil.jar

·         Open your graph module in FormsBuilder (Forms [64 Bit] Version 12.2.1.2.0 (Production))

·         Compile and save the graph.fmb module.

Use Webutil to manipulate blob columns

Use Webutil to manipulate blob columns

This demo shows how to manipulate information stored in database tables as blob type using webutil.
We have database table named PDM with the following structure:

ID                  NUMBER        

DNAME               VARCHAR2(100) 

FNAME               VARCHAR2(50)  

IBLOB               BLOB          

FTYPE               VARCHAR2(5)

PDM – data

Oracle Forms 12c Client Deployment Configuration Options

Oracle Forms 12c Client Deployment Configuration Options

There are four supported client deployment configuration options in Oracle Forms 12c. The available options are as follows. (Ref. Oracle – PDF doc )

·         Java Applet embedded in HTML

·         JNLP embedded in HTML

·         Java Web Start (JWS)

·         Forms Standalone Launcher (aka Standalone or FSAL)

Any of these options can be enabled and configured using Fusion Middleware Control, the formsweb.cfg should be modified to setup any of the previous configurations.

---

·         Java Applet Embedded in HTML:

This configuration is the default one for any oracle Forms installation. This option was the first offered when browsers began supporting the Java Plug-in. This configuration is the default for any Oracle Forms installation, 12.2.1 and older. JavaScript integration feature. Single sign-on and single sign-off are also fully supported in this configuration. Disadvantages of using this option include the requirement of a Java Plug-in and the need for a certified browser that supports the Java Plug-in.

In our example:

The section of BLOB-configuration contains the following values base.htm and basejpi.htm  for  respectively baseHTML and baseHTMLjpi variables.

[BLOB]

# System parameter: file setting environment variables for the Forms runtime processes

# System parameter: default base HTML file

baseHTML=base.htm

# System parameter: base HTML file for use with Sun's Java Plug-In

baseHTMLjpi=basejpi.htm

the BLOB forms application is launched simply by entering the following url:

http://linecode:9001/forms/frmservlet?config=BLOB

Java Applet Embedded in HTML

·         JNLP Embedded in HTML

Embedded JNLP, like an embedded Applet, fully supports JavaScript integration, single sign-on, and single sign-off Embedded JNLP has the added advantage of base-64 encoding the JNLP content. The base-64 encoded text is not human readable.

This configuration requires the Java Plug-in and a certified browser that supports the Java Plug-in.

Let’s define a jnlp configuration for our BLOB forms application.

# JNLP conf. for BLOB Forms application

[JNLPBLOB]

# System parameter: default base HTML file

basejnlp=base.jnlp

# System parameter: base HTML file for use with Sun's Java Plug-In

baseHTMLjpi=basejpi_jnlp.htm

JNLP conf. for BLOB

In this configuration, our icons do not appear. We have to do some other modifications to extensions-file.

<!-- <jar href="ADD YOUR JARS HERE - ONLY ONE PER ENTRY"/> -->

 <!-- <jar href="jacob.jar"/> -->

 <jar href="iconsapp.jar"/>

Now, all icons appear in our form

Unable to Start the Admin Server in Forms 12c, due to ORA-28000

How to fix the ORA-28000 : Unable to Start the Admin Server in Forms 12c

During Forms12c installation and configuration, we have to configure a repository. (Fore more details, see the procedure for RCU Configuration document above)

During the repository installation and depending on the choice you made, some of the following schemas are created: DEVPLG, DEV_WLS, DEV_IAU_VIEWER, DEV_STB, DEV_IAU, DEV_OPSS, DEV_IAU_APPEND, DEV_WLS_RUNTIME.

---

·         So, for the puspose of the current post, i will simulate the ORA-28000

·         Let’s begin by locking the DEV_OPSS user created in our pluggable database.

alter user DEV_OPSS account lock;
SELECT username, account_status, authentication_type
  FROM dba_users
WHERE username LIKE ‘DEV_%’;

DEV_WLS_RUNTIME OPEN      PASSWORD
DEV_IAU_APPEND     OPEN     PASSWORD
DEVPLG                    OPEN     PASSWORD
DEV_OPSS                LOCKED PASSWORD
DEV_IAU                  OPEN     PASSWORD
DEV_STB                  OPEN    PASSWORD
DEV_IAU_VIEWER     OPEN    PASSWORD

·         Now, we start our weblogic server in order to see the error
startWeblogic.cmd

Caused by: java.sql.SQLException: ORA-28000: the account is locked

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:466)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:391)
at oracle.jdbc.driver.T4CTTIfun.processError(T4CTTIfun.java:1126)
at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthenticate.java:507)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:546)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:269)
at oracle.jdbc.driver.T4CTTIoauthenticate.doOAUTH(T4CTTIoauthenticate.java:440)
at oracle.jdbc.driver.T4CTTIoauthenticate.doOAUTH(T4CTTIoauthenticate.java:1025)
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:682)
at oracle.jdbc.driver.PhysicalConnection.connect(PhysicalConnection.java:793)
at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:33)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:614)
at java.sql.DriverManager.getConnection(DriverManager.java:664)
at java.sql.DriverManager.getConnection(DriverManager.java:208)
at org.eclipse.persistence.sessions.DefaultConnector.connect(DefaultConnector.java:98)
… 94 more

<2017-09-07, 10:28:19,303 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED.>
<2017-09-07, 10:28:19,303 AM EDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself
<2017-09-07, 10:28:19,305 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN.>
Stopping Derby server…
Derby server stopped.

---

·         To fix the previous error, we just need to unlock the DEV_OPSS user
alter user DEV_OPSS account unlock;
startWeblogic.cmd

……………………………………………………………….
<2017-09-07, 10:31:28,994 AM EDT> <Notice> <Server> <BEA-002613> <Channel “Default[2]” is now listening on 0:0:0:0:0:0:0:1:7003
mp, http.>
<2017-09-07, 10:31:28,994 AM EDT> <Notice> <Server> <BEA-002613> <Channel “Default” is now listening on 10.12.37.17:7003 for pro
p.>
<2017-09-07, 10:31:28,995 AM EDT> <Notice> <WebLogicServer> <BEA-000329> <Started the WebLogic Server Administration Server “Adm
n” running in production mode.>
<2017-09-07, 10:31:28,995 AM EDT> <Notice> <Server> <BEA-002613> <Channel “Default[1]” is now listening on 127.0.0.1:7003 for pr
tp.>
<2017-09-07, 10:31:28,995 AM EDT> <Notice> <Server> <BEA-002613> <Channel “Default[2]” is now listening on 0:0:0:0:0:0:0:1:7003
mp, http.>
<2017-09-07, 10:31:28,997 AM EDT> <Notice> <Server> <BEA-002613> <Channel “Default” is now listening on 10.12.37.17:7003 for pro
p.>
<2017-09-07, 10:31:28,999 AM EDT> <Notice> <WebLogicServer> <BEA-000360> <The server started in RUNNING mode.>
<2017-09-07, 10:31:29,5 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING.>

 

Unable to Start the Admin Server in Forms 12c, due to ORA-28001

Unable to Start the Admin Server in Forms 12c, due to ORA-28001

In the previous post, we have seen how to fix the issue : 
Unable to Start the Admin Server in Forms 12c, due to ORA-28000 in case of DEV_OPSS schema is locked.
We will now look at ORA-28001 error caused by password expired.
For the purpose of the current post, i will set the DEV_OPSS password expired in our pluggable database.

---

Reset the password to expired
ALTER USER DEV_OPSS PASSWORD EXPIRE;
Let’s display the user :
SELECT username, account_status, authentication_type 
FROM dba_users 
WHERE username LIKE ‘DEV_%’;

DEV_WLS_RUNTIME             OPEN     PASSWORD
DEV_IAU_APPEND              OPEN     PASSWORD
DEVPLG                      OPEN     PASSWORD
DEV_OPSS                                         EXPIRED   PASSWORD
DEV_IAU                     OPEN     PASSWORD
DEV_STB                     OPEN     PASSWORD
DEV_IAU_VIEWER              OPEN     PASSWORD
DEV_WLS                     OPEN     PASSWORD

After starting the weblogic server, using the startWeblogic.cmd command on windows, we will get the following error:

Error Code: 28001
…………………………………………….
at oracle.security.jps.internal.policystore.rdbms.JpsDBDataManager.existsTable

(JpsDBDataManager.java:1669)
… 84 more
Caused by: java.sql.SQLException: ORA-28001: the password has expired

---

♦ Solution:

·         We have to reset the expired password for the DEV_OPSS user.

·         alter user DEV_OPSS identified by xxx_n_pass;

·         We need to start weblogic server, however, before that, we have to do the following:

·         Run the wlst.cmd in $ORACLE_HOME/oracle_common/common/bin

·         Search for jps-config.xml – file in : ORACLE_HOME>\user_projects\domains\base_domain\config\fmwconfig

·         Run the following command in wlst-window

modifyBootStrapCredential(jpsConfigFile='<Oracle_Home>/user_projects/domains/base_domain/config/fmwconfig/jps-config.xml’,username=’DEV_OPSS’,password=’xxx_n_pass’)

·         In WLST, run the following (you must use forward slashes ‘/’ even for Windows): 

·         Exit WLST: exit() — Exit the wlst scripting window.

·         Restart the Admin Server. The Admin Server will start up even if there are some errors about the data source

weblogic.application.ModuleException: weblogic.common.resourcepool.ResourceSystemException:
Could not create connection for datasource ‘opss-data-source’.

·         The returned message is: ORA-01017: invalid username/password; logon denied

·         Log into the Admin Console.

·         In the Admin Console, click “Lock & Edit“.

·         Go to the Configuration Pool, change and confirm the new password

·         Click on Activate changes

·         If all is done correctly, you will see Setting updated successfully.

·         Click on view changes and restart.

Finally, restart your weblogic server. Source: Oracle Support Document ID 1682942.1

Client-Idle System Event in Forms12c

The new System Events include the following Client-Idle (SYSTEM_CLIENT_IDLE)

This event will be raised when the end-user has not performed any actions in the associated application session for the amount of time configured.
The maximum idle time will be configurable using either a new applet parameter idleTimeout or using a newSET_APPLICATION_PROPERTY argument CLIENT_IDLE_TIME.
Setting the value to 0 will disable idle time monitoring.
The values set for this event may not exactly represent the time specified. For example, an idle time setting of n seconds may not immediately raise the event until n+1 seconds have elapsed.

---