The post Oracle Forms 11gR2 Extended Support Expiration Notice appeared first on PITSS US - Oracle Forms Upgrade, Forms to ADF, Forms to APEX, Migration.

Top 5 Java Frameworks

Be it the Tiobe index, the analysis of RedMonks or even the results of PYPL – all evaluation systems of the current programming languages see Java in first place or second only understandable if so for its own software development, especially the various Java frameworks under the magnifying glass are taken.

Handing Oracle’s announcement to Java EE to the Eclipse Foundation’s open source community to allow more agility in the development of the programming language is encouraging a lot of movement in the area of frameworks. In addition, the increasingly popular use of JavaScript in the UI and the architectural pattern of the microservices lead to a further change in the Java frameworks.

The question arises: Which Java frameworks may we assume at the top of the charts next year?

Spring MVC

Spring MVC is now one of the established classics in Java-based application development for web applications. Therefore, it can be assumed that this framework will also take one of the first places in the coming year. With the version 5.0 expected in September, not only the Java JDK version 9 supported, but also important innovations will be released. WebFlux incorporates a promising framework that is fundamentally based on a reactive, non-blocking stack, making it ideal for asynchronous and streaming scenarios.

Also, the Java Framework opens in many places in the programming language Kotlin, which may be much trusted in the future.

Advantages

R

Fine granular modularity: Only the components of the framework that are really used need to be integrated.

R

Dependency Injection: A method with which the dependency between different classes is ideal, i. H. modular, without overhead and very easy to test, can be solved.

R

Easy Portability: The created application runs on a very wide selection of different WebContainer (eg TomCat, Glassfish etc.).

R

Broad community support: Support in various forums, platforms and sponsors is easy to find.

Disadvantages

Q

Not complete: May be considered a disadvantage or strength, but for a complete application development for other areas of data connectivity, transaction control, security, etc., other frameworks must be used.

Q

No RAD tool: Relatively much coding is required, which requires more manual effort in large projects.

Spring Boot

A second framework from the product range of Spring should also find the place among the top candidates here. Spring Boot follows the concept of “conventions before configurations” and should simplify the quick start into application development. The starter package already includes an AppServer and the most important configurations, so that you can start the development without a complex set-up. It consistently uses Java Configuration Services, which allows dependencies on other tools and frameworks to be managed by Spring Boot.

In principle, Spring Boot can use all the features of the other Spring projects and include them. The approach is currently targeting projects that rely on microservice architectures, as Spring Boot can pull everything together, from the first class for database access to WebContainer.

Advantages

R

Very easy set-up: The initial project can be created and downloaded on the website via Wizzards.

R

Simple deployment: Spring Boot takes over the dependencies, a simple call and the container incl. Application are provided.

R

Simple debugging: Since it is a simple Java application, it can also be used as such for debugging.

Disadvantages

Q

Focus: Like most frameworks, Spring Boot only covers a specific area of application development. Without further frameworks the project will not succeed.

Q

Coding: Even though the annotations are already doing a lot of work, at the end of the day it still remains with an extensive amount of lines of code that need to be written.

Q

Enterprise Applications: Focus is on stand-alone application in a microservice ecosystem. If an enterprise application is needed, the approach is not helpful.

Oracle ADF

Oracle’s full Java framework covers the entire application development stack, from data connectivity to a variety of data sources, from visual declaration of task flows to the design of the UI based on Java Server Faces technology. The combination of wizards and the degree of freedom in the concept of the JEE platform anywhere to integrate their own components, provide unprecedented productivity for the developer. Particularly noteworthy are the preconfigured possibilities to provide the created application on all levels with a comprehensive security concept and without further implementation to give the user the opportunity to customize the application after deployment to their own ideas. In addition to the framework linked to the Weblogic server, Oracle also provides a free version with ADF Essential that is certified with the Glassfish server. B. on TomCat servers can be used.

Advantages

R

Productivity: The approach to edit XML files either via wizards or in the editor, which are then interpreted by the framework, saves unnecessary coding.

R

Full: There is no other framework, tools or classes necessary to create a complete enterprise application.

R

Technology Encapsulation: The framework encapsulates basic technologies, such as: As HTML5 and facelets and thus ensures the releases that each current and established implementations are used.

Disadvantages

Q

IDE Binding: Use of the framework is tied to the IDE JDeveloper (recommended by Oracle) or Eclipse. Other IDEs are not supported.

Q

Limits of generation: If requirements are to be implemented that are outside the mainstream of the framework, the complexity increases disproportionately.

Q

Binding to Weblogic Server: The Weblogic Server is required for full functionality. ADF Essential solves the problem, but requires its own implementation for security and customization.

Java Server Faces (JSF) – PrimeFaces

Java ServerFaces describes a web framework for creating applications based on Java as well as servlets and JSP (Java ServerPages) technologies and belongs to the technology stack Java EE. The approach of the Model-View-Controller concept is strictly followed, modularization and reuse allow an efficient design of the user interfaces. JSF is implemented by a number of web frameworks. These include ICEFaces from IceSoft, RichFaces from JBoss and – most prominently – PrimeFaces from PrimeTek.

Only last year, PrimeFaces was awarded the Java Community in the Enterprise Java Duke’s Choice Award.

PrimeFaces is a lightweight library that tries to make the complexity of UI design as easy as possible. Especially with Spring applications in the backend appealing enterprise applications can be created.

Advantages

R

Easy to use: The concept of getting along with a JAR without further dependencies makes it easier to integrate into your own development infrastructure.

R

Community support: Literature, blogs and support in various forums are widespread and provide rich and valuable content.

R

Standard: It follows the JSF and JEE standard, allowing integration into and from other frameworks that follow this pattern. For the area JSF PrimeFaces can be accepted as quasi-standard.

Disadvantages

Q

Scope: PrimeFaces focuses exclusively on the design of the UI. Other frameworks are therefore imperative for the data connection and the controller.

Q

Data Binding: The integration of data binding is time consuming and quickly becomes extensive.

Q

Technically demanding: There are many options available for the UI, which can quickly lead to a complex implementation and require a high level of technical know-how.

Vaadin

Vaadin is a web framework that allows the developer to write the complete application on the server side exclusively in Java. The framework uses Google’s Java-to-Java Script Compiler “Goolge Web Toolkit” (GWT) to represent the UI in the browser. In this combination, Vaadin gives the user the feeling of a true rich client interface with standard features such as: For example, column sorting and the abandonment of complete page refreshing.

The abstraction of the actual web development with HTML5, CSS and Javascript makes it easier for the newcomers to take the first step into web development, but at the same time provides the framework for possible degrees of freedom in designing the user interfaces.

Support for the development environment is particularly evident in the Eclipse area, where Netbeans and IntelliJ are also supported. In addition, Vaadin also offers a Visual Designer, which allows a WYSIWYG development of the web front end.

Advantages

R

Helpful plug-ins from the manufacturer: These include a spreadsheet component, native smartphone and tablet support, UI Testing Tools and more. v. m.

R

Easy integration with Spring: Full API integration, ideal access to Spring Data deployment.

R

Use: Efficient implementation focused on server-side Java programming.

Disadvantages

Q

Costs: If Vaadin is to be used in its entirety, with all plug-ins and maintenance, the service starts at 800 € per month.

Q

Generated Code: Relatively large, as the client-side generated Java Script components are getting quite large.

Q

No client-side processing possible: Each request goes first to the server and this can be time-consuming.

Conclusion to the Top 5 Java Frameworks

Currently, more than 60 web frameworks are listed on Wikipedia. The selection in this article is our perception and refers to the frameworks that become visible to us in conversation with our customers.

Application development on the Web shows that at least two Java frameworks from different vendors often have to be used to develop a complete enterprise application. The exception here is Oracle’s Application Development Framework, which offers everything from data connection to UI from a single source.

Since a large number of applications rely on Oracle databases in the backend, this framework offers itself all the more.

However, to end with a quote from Steve Jobs: “Technology is nothing. What’s important is that you have faith in people, that they’re basically good and smart, and you’re giving them tools, they’ll do wonderful things with them.”

The post Top 5 Java Frameworks appeared first on PITSS US - Oracle Forms Upgrade, Forms to ADF, Forms to APEX, Migration.

The post Jasper Reports – Javascript & PL/SQL Integration appeared first on PITSS US - Oracle Forms Upgrade, Forms to ADF, Forms to APEX, Migration.

The post Unable to Access Oracle Forms Application with SSL Using JRE 8 Update 171 appeared first on PITSS US - Oracle Forms Upgrade, Forms to ADF, Forms to APEX, Migration.

How to Prevent Oracle WebLogic Server Vulnerability

by Stephen la Rocca

Business Development, PITSS GmbH

The US IT security company Greynoise is currently reporting heavily increased scanning activity for vulnerable WebLogic servers.

Although there are already updates available for these which apparently can already be bypassed by the attackers, the updates do not solve the crux of the problem. Particularly critical seems to be the vulnerability with the identifier CVE-2018-2628.

GreyNoise has observed a large spike in devices scanning the Internet for TCP port 7001 beginning last week on 4/16/18. This activity corresponds directly with the disclosure (4/18/2018) and weaponization (4/18/18) of Oracle WebLogic CVE-2018-2628. Ref: https://t.co/3qdeQSF59T

— GreyNoise Intelligence (@GreyNoiseIO) April 24, 2018

Close the vulnerability and block TCP port 7001

If you use Oracle WebLogic Server, you should definitely take action. On one hand, the latest version must be installed as soon as possible. That alone does not seem to be enough.

Security researcher Kevin Beaumant warns that the most recent patch did not close the actual vulnerability, but merely blacklisted certain commands. Therefore, it is important to additionally block TCP port 7001 in order to avoid external access.

Oh dear. There’s a zero day in Oracle WebLogic because the April patch didn’t fix the issue properly. Mitigation: make sure port 7001 TCP is blocked inbound to your Fusion stack boxes. https://t.co/EqjqMwzXNp

— Kevin Beaumont (@GossiTheDog) April 29, 2018

If you’re looking for help updating, modernizing, and securing your vulnerable WebLogic server, contact PITSS today.

The post Preventing Oracle WebLogic Server Vulnerability appeared first on PITSS US - Oracle Forms Upgrade, Forms to ADF, Forms to APEX, Migration.

The latest critical patch update from Oracle for July 2018 brings a lot of security updates. These updates affect the WebLogic Server, the Enterprise Manager, and databases (among other things). Oracle recommends that all users download the patches immediately to guarantee that your applications will operate securely.

All affected software components, as well as the critical patch update notices, can be found at the following link: http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html

If you need assistance while importing the latest Oracle critical patch update, we’re here to help.

The post Oracle Releases Critical Patch Update for July 2018 appeared first on PITSS US - Oracle Forms Upgrade, Forms to ADF, Forms to APEX, Migration.

The post Oracle Critical Patch Update for April 2019 appeared first on PITSS US - Oracle Forms Upgrade, Forms to ADF, Forms to APEX, Migration.

There is a known PITSS.CON issue when you run a Search and Replace. The issue is that after running either a search or a search and replace in PITSS.CON, the following error is produced:

40505 – ORACLE error: unable to perform query

After a few moments, the Search and Replace results will come up. However, the results are blank even though there is a count of objects which should have been returned.

The reason for this is because there is an Oracle bug in the Oracle database hosting PITSS.CON. The solution is to run the following SQL command as a SYSDBA user such as SYS:

alter system set optimizer_features_enable=’11.2.0.4′;

Once this is run, the problem should disappear.

The post Unable to Perform Query When Running Search and Replace in PITSS.CON appeared first on PITSS US - Oracle Forms Upgrade, Forms to ADF, Forms to APEX, Migration.

When moving PITSS.CON from one database to another, if you encounter the error where it fails to insert into MIG_PITSSCON_USERS or PITSSCON_USERS, check the MIG install log located in C:\pitsscon\log or C:\pitsscon\mig\log. If you see the following error at the end of the log file:

ORA-04063: package body “MIG.PAC_IN” has errors

The MIG user being installed does not have the proper permissions to set up the PITSS.CON administrator in the database. To fix this problem, the following grants will need to be granted to PUBLIC in the database as a SYSDBA user:

• grant execute on DBMS_OBFUSCATION_TOOLKIT to PUBLIC;
• grant execute on DBMS_OUTPUT to PUBLIC;
• grant execute on DBMS_STATS to PUBLIC;
• grant execute on DBMS_JAVA to PUBLIC;
• grant execute on DBMS_SQL to PUBLIC;
• grant execute on DBMS_LOB to PUBLIC;

Once these grants are set up in the database, re-try the PITSS.CON database move, and it should work successfully.

The post PITSS.CON Database Move Error – Error When Inserting into MIG_PITSSCON_USERS appeared first on PITSS US - Oracle Forms Upgrade, Forms to ADF, Forms to APEX, Migration.

By default, Oracle Forms is not configured to have sessions timeout after a session has been idle for a specific period of time. However, it can be possible to either configure timeouts in Oracle Forms or to have Forms sessions time out due to outside factors.

In Forms 12c, Oracle Forms has three different parameters available for configuring timeouts:

• heartBeat – Indicates the frequency which the client sends a packet to the server to indicate that it is still up and running
  • Defined in: $DOMAIN_HOME/config/fmwconfig/servers/WLS_FORMS/applications/formsapp_12.2.1/config/formsweb.cfg
  • Default value (if not set): 2 (minutes)
  • Minimum allowed value: None
  • Maximum allowed value: None
• FORMS_TIMEOUT – Indicates the amount of time (in minutes) before a Forms session is terminated when there is no client communication with the server. Such communication occurs when either the user is doing something in the app or from the heartbeat when the user is not using the form (the session is idle).
  • Defined in: $DOMAIN_HOME/config/fmwconfig/servers/WLS_FORMS/applications/formsapp_12.2.1/config/<ENV_FILE>.env
  • Default value (if not set): 15 (minutes)
  • Minimum allowed value: 3 (minutes)
  • Maximum allowed value: 1440 (minutes)
    • NOTE: Oracle does not recommend setting FORMS_TIMEOUT greater than 15 minutes.
• Session-Timeout – Indicates the number of minutes elapsed for timing out a Forms session.
  • Defined in: $DOMAIN_HOME/config/fmwconfig/deployment-plans/formsapp/12.2.1
  • Default value (if not set): 60 (minutes)

For no timeout to occur, the heartBeat must be set to a value less than both FORMS_TIMEOUT and Session-Timeout. The reason is that when a Forms session is idle, a heartbeat is sent from the client to send a signal to the server to keep the session alive and not timeout. A timeout from the Forms side will only occur if the time between when the session became idle and either FORMS_TIMEOUT or Session-Timeout is reached before either a session becomes active again by user interaction or by a heartbeat. With the default settings indicated above, the heartbeat is set to a value less than both FORMS_TIMEOUT and Session-Timeout. As a result, no timeout will occur unless timeout settings are manually configured.

Configuring Timeout in Oracle Forms

If you wish to configure a timeout feature in Oracle Forms, the recommended option is to either create a Forms Timeout JavaBean or (new to 12c) is to create a system event, SYSTEM_CLIENT_IDLE. Unlike the Timeout Bean, there are less limitations with the system event. The full solution may be found in https://support.oracle.com/epmos/faces/DocumentDisplay?id=2114912.1, but the solution involves creating an alert, CLIENT_IDLE_ALERT, then creating a number type called event_value, a button trigger, an event called CLIENT_IDLE with the “Event Type” property of “System Client-Idle”, and a WHEN-EVENT-RAISED trigger. Last, run the form, set a valid timeout entry value into the EVENT_VALUE, press the button to start the timeout, and then the CLIENT_IDLE event will take place as soon as the timeout set in the EVENT_VALUE is reached. Once it has, the alert will then pop up.

NOTE: If any model/blocking window is displayed, idle code will not fire until after the blocking condition is released. If you need it to behave differently, a custom JavaBean will need to be developed.

Although it is not recommended by Oracle, you may also configure timeout by setting the heartBeat parameter to be greater than FORMS_TIMEOUT. For example, if FORMS_TIMEOUT is set to 15 (minutes) in your ENV file and you set the heartBeat to 16 (minutes) in formsweb.cfg, a heartbeat will not be sent to the server from the idle client until the heartBeat limit (16 minutes in this example) is reached. Thus, the FORMS_TIMEOUT limit will be reached, and idle sessions will then see a FRM-93652 error after 15 minutes or however long the FORMS_TIMEOUT variable is set.

Another option which is not recommended by Oracle is to set the heartBeat greater than Session-Timeout (in plan.xml) but not necessarily greater than FORMS_TIMEOUT. The same timeout situation will happen, but an FRM-92102 error will appear instead.

FRM-91230 – Fatal Error in Runtime Process: Timeout on Connection to Java Client

Sometimes Forms sessions may be kicked out or timed out due to outside factors such as database timeouts, network issues, server issues (on the OS level), or load balancers. In the front end, users may either see a Forms session or JNLP window exit out or crash with an error such as FRM-93652. One of the first places to look for any Forms-related errors is in formsapp-diagnostic.log located in $DOMAIN_HOME/servers/WLS_FORMS/logs. In the logs, you may notice periodic errors such as FRM-91230. This usually indicates that the user lost connection to the Forms runtime process due to a termination. For Oracle Forms 12c, this may be seen due to the following reasons:

1. Users closed the browser without exiting the Oracle Forms application gracefully

a. This can be quite common. The only way to prevent this is to either educate the users to gracefully exit the application before closing the browser whenever possible (it may be unavoidable if the browser itself crashes for any reason) or to program the forms to alert the user to gracefully close the form first. If you are using Java Web Start or FSAL, users will also be left apt to close the application improperly.

2. Heartbeat is greater than FORMS_TIMEOUT

a. Oracle does not recommend this approach for configuring timeouts. See the Configuring Timeout in Oracle Forms section for details on recommended approaches. If you do not configure timeouts manually in Oracle Forms, the heartBeat parameter will be less than FORMS_TIMEOUT.

3. Inappropriate timers in forms

a. Timers (if configured) should have as short duration and low frequency as possible. If you need to utilize timers, Oracle recommends configuring JavaBeans for this.

4. Network issues

Sources:

• Session-Timeout: https://support.oracle.com/epmos/faces/DocumentDisplay?id=1073239.1
• FRM-91230: https://support.oracle.com/epmos/faces/DocumentDisplay?id=1357555.1
• Timeout in Webforms: https://support.oracle.com/epmos/faces/DocumentDisplay?id=549735.1
• Configuring Client Idle Session Timeout: https://support.oracle.com/epmos/faces/DocumentDisplay?id=2114912.1

The post Timeouts in Oracle Forms appeared first on PITSS US - Oracle Forms Upgrade, Forms to ADF, Forms to APEX, Migration.

Similar to how timeouts can be configured for Oracle Forms, similar timeout features may be implemented for Oracle Reports. Configuring timeouts in Oracle Reports is done in rwserver.conf which is the main configuration file for the reports server. The following configurations may be done in rwserver.conf for configuring timeout:

• Engine Response Timeout
  • Default: null (no timeout)
  • The Engine Response Timeout is how long (in minutes) a report job can run before the reports server engine cancels the job.
  • This is good if a query or report engine is hanging and holding up the queue for other report jobs.
  • Example (15 minutes):
    • <engine class=”oracle.reports.engine.EngineImpl” engLife=”25″ id=”rwEng” maxEngine=”12″ minEngine=”0″ maxIdle=”30″ jvmOptions=”-Xms512m -Xmx512m” initEngine=”2″ engineResponseTimeOut=”15”>
• callbackTimeout
  • Default: 90000
  • The callbackTimeOut is the amount of time (in milliseconds) which the reports server will wait from when the reports server engine is started to when it is called back.
  • Example (100000 ms)
    • <engine class=”oracle.reports.engine.EngineImpl” engLife=”25″ id=”rwEng” maxEngine=”12″ minEngine=”0″ maxIdle=”30″ jvmOptions=”-Xms512m -Xmx512m” initEngine=”2″ callbackTimeout=”100000”>
• maxIdle
  • Default: 30
  • The maxIdle parameter is how long a reports server engine can remain idle before it is terminated. However, this will only work if the value of minEngine is set to 0. If minEngine is set to a value greater than 0, the engine will remain up because the server will be configured to always have an engine running.
  • Example ( 60 min):
    • <engine class=”oracle.reports.engine.EngineImpl” engLife=”25″ id=”rwEng” maxEngine=”12″ minEngine=”0″ maxIdle=”30″ jvmOptions=”-Xms512m -Xmx512m” initEngine=”2″ maxIdle=”60”>

The post Timeouts in Oracle Reports appeared first on PITSS US - Oracle Forms Upgrade, Forms to ADF, Forms to APEX, Migration.

WebLogic is a very stable application server platform used for deploying Java applications. However, there may come a time when your WebLogic server may encounter memory issues. When troubleshooting OutOfMemoryErrors in WebLogic, there are some important key points to keep in mind. One part of JVM memory is heap where the other part consists of permanent space. As we do not recall seeing OutOfMemoryErrors pertaining to PermGen, we would not change anything with this unless directed otherwise. We would also ignore -XX:NewRatio (this is another version of –Xmn as it is the ratio between the young generation and the old generation heap except in a ratio format) as well as –XX:PermSize and –XX:MaxPermSize (these parameters are for managing the permanent space in JVM memory) initially.

Troubleshooting Tips:

We are in favor of trying out -XX:+UseG1GC (the Garbage-First or G1 garbage collector) as documented in these articles:

• https://docs.oracle.com/javase/8/docs/technotes/guides/vm/gctuning/g1_gc.html#garbage_first_garbage_collection
• http://docs.oracle.com/javase/7/docs/technotes/guides/vm/G1.html.

The G1 garbage collector is supposed to achieve high performance and pause time goals. It has been supported since JDK 7. Oracle recommends using G1 when:

1. Applications are using very large heaps to avoid running out of memory (especially 6 GB of heap or larger)
2. More than 50% of the Java heap is being filled with live data
3. The rate of object allocation rate varies significantly
4. There is a very long garbage collection or compaction pauses longer than a second

Also, Oracle is currently planning to replace the existing garbage collector, Concurrent Mark-Sweep Collector (CMS), with G1.

If you use the G1 garbage collector, it will be important to set the parameter, -XX:InitiatingHeapOccupancyPercent=##, which also controls when garbage collection takes place as noted in Oracle Support note 1677981.1. We would test with having the value set to 55. Additionally, we would also use the –XX:MaxGCPauseMillis argument which is the pause time goal. This parameter, in milliseconds, is the pause time. We have seen this set to 200 milliseconds, so you could try configuring this and adjust as accordingly. You may also use -XX:MaxTenuringThreshold if you like which is another garbage collector tuning parameter specifying how many minor GC cycles an object will stay in “survivor spaces”. We recommend to only set this between 0 and 15 (one of PITSS’ customers used 10). It is advised to not set it greater than 15. If you go ahead with the G1 garbage collector, you can ignore the arguments “-XX:ParallelGCThreads” and “-XX:ConcGCThreads”.

In general, other reasons why the OutOfMemoryError messages are occurring even with the message “GC overhead limit exceeded” can be due to (as documented in http://www.jvmhost.com/articles/what-is-java-lang-outofmemoryerror-gc-overhead-limit-exceeded):

1. Optimize the application to use less memory and/or reuse objects instead of creating new ones. This will reduce how often the garbage collector runs. Try reusing objects if a lot of temporary objects are created.
2. Increase the JVM heap.
3. Do not use -XX:-UseGCOverheadLimit. Although the “GC overhead limit exceeded” errors will disappear, they will be replaced by heap-related OutOfMemoryError messages.

When troubleshooting OutOfMemoryErrors in WebLogic, you can also test the JVM by debugging the garbage collector and the JVM. If you set these logging JVM parameters, -verbose:gc, -XX:+PrintGCDetails, and -XX:+PrintGCTimeStamps, you can check to see if a full garbage collection is done before the OutOfMemoryError appears. If the GC fails to complete before the error happens, it may be a JVM bug. Also, make sure the JVM does proper compaction work and the memory is not fragmented. If the JVM does its work properly, the error may be application-related. Oracle Support note 877172.1 in the “For Java OOM” section contains more information on this.

The post Troubleshooting OutOfMemoryErrors in WebLogic appeared first on PITSS US - Oracle Forms Upgrade, Forms to ADF, Forms to APEX, Migration.

Starting in Forms 12c, end users have been able to launch their Oracle Forms applications without needing the insecure NPAPI plugin which has since been removed from all browsers except for Internet Explorer. With this, Forms 12c allows users to configure either Java Web Start (JWS) or Forms Standalone Launcher (FSAL) to launch their applications. However, when launching Oracle Forms in Firefox using Java Web Start, there is a known issue where the downloaded JNLP file cannot be run.

These steps will allow you to set up Firefox so that you may run the JNLP from Firefox:

1. Launch Mozilla Firefox if it is not already open.

2. Click the “Open menu” icon in the top-right corner and select “Options”.

Once you click the Open menu icons highlighted here, click on Options in the menu which appears.

3. While in the General tab, scroll down until you see Applications. Once there, locate the JNLP File entry.

The default setting is to “Always ask”. However, this causes a problem with trying to run a JNLP from Firefox.

4. Under the Action column, select the down arrow in the JNLP File entry and choose “Java Web Start Launcher”.

5. Exit out of Firefox completely and restart Firefox.

After completing the steps above, you should be able to download a JNLP file from Firefox to run your Oracle Forms application. You will now be able to run Oracle Forms in Firefox using Java Web Start.

Once you click OK in this pop-up, a JNLP window will be launched to run Forms.

Oracle has some additional information regarding both Java Web Start and Forms Standalone Launcher in its white paper. You may click on this link here to read the white paper. Contact PITSS today if you would like any assistance setting up your Oracle Forms environment to run with Java Web Start or Forms Standalone Launcher.

The post How to Run Oracle Forms in Firefox Using Java Web Start appeared first on PITSS US - Oracle Forms Upgrade, Forms to ADF, Forms to APEX, Migration.

Oracle Forms 12c has introduced new ways to launch Oracle Forms applications: Java Web Start (JWS) and Forms Standalone Launcher (FSAL). FSAL is a way which you can launch an Oracle Forms application without using a web browser. It is absolutely possible to run PITSS.CON using Forms Standalone Launcher. Before you can run PITSS.CON using Forms Standalone Launcher, these prerequisites need to be met:

Prerequisites

1. You must be running Oracle Forms 12c
2. Each end user must be provided a jar file, frmsal.jar, from the application server in which PITSS.CON is installed
3. Each end user must either have a JDK or JRE installed
4. The JDK or JRE must be in the end user’s PATH environment variable
5. PITSS.CON must be installed in your application server environment

Setup

Once all prerequisites have been met, you may proceed with configuring the PITSS.CON environment to use FSAL:

1. Open up formsweb.cfg in %DOMAIN_HOME%\config\fmwconfig\servers\WLS_FORMS\applications\formsapp_12.2.1\config

2. Locate your configuration section for pitsscon. Example: [pitsscon]

3. Add the following parameters to the end of your pitsscon configuration section:

• baseSAAfile=webutilsaa.txt
• fsalcheck=true

4. Save and close the file

5. If you have not already done so, locate your frmsal.jar file in %ORACLE_HOME%\forms\java and provide this to all end users whom will run PITSS.CON.

Launching PITSS.CON With FSAL

Now that the PITSS.CON environment has been configured, your end users may now run PITSS.CON using Forms Standalone Launcher:

1. Make sure all end users have either a JDK or JRE in their PATH environment variable.

• Example: PATH=C:\Program Files\Java\jre1.8.0_261\bin;…

2. Open up Command Prompt or cmd.exe.

3. Run the following command to call PITSS.CON:

• java -jar <PATH_TO_frmsal.jar>\frmsal.jar -url “http://<app_server_url>:<forms_port>/forms/frmservlet?config=pitsscon”
• Example: java -jar C:\Users\Scott\Downloads\frmsal.jar -url “http://pitss-server:9001/forms/frmservlet?config=pitsscon”

After launching the java command, the PITSS.CON login screen will now appear. You may now log into PITSS.CON normally. This will allow you to run PITSS.CON independently from the web browser. Please note that if you need to run a tree report from PITSS.CON, a report will be launched from the default web browser.

The post How to Run PITSS.CON Using Forms Standalone Launcher appeared first on PITSS US - Oracle Forms Upgrade, Forms to ADF, Forms to APEX, Migration.

Aliases allow you to use Oracle HTTP Server to access files stored on the server. These steps below can be run for configuring aliases in OHS 12c:

1. Log into EM using your WebLogic username and password.

2. Once logged into EM, expand the Target Navigation pane in the top-left corner. Expand HTTP Server and right-click on ohs1. Go to Administration → Server Configuration

3. Click the lock button in the top-right corner and select “Lock & Edit”.

4. Under Aliases, click “+ Add Row” to create a new alias.

5. In the newly-created row, enter the URL path (the alias itself) and the file path of the alias. For the file path, make sure to surround it with double quotes and to use ‘/’ instead of ‘\’ even for Windows environments.

6. Repeat steps 4 and 5 for any additional aliases you may need to create. Once you are done creating the alias(es) you need, click “Apply”.

7. Expand the Oracle HTTP Server drop-down menu and go to Administration → Advanced Configuration.

8. Select “httpd.conf” and click “Go”.

9. Scroll down to the very bottom. You will see the alias there.

10. In the line underneath it, add the following lines:

• <Directory “<ALIAS_FILE_PATH>”>
• Options Indexes MultiViews
• AllowOverride None
• Require all granted
• </Directory>

NOTE: The directory should use ‘/’ instead of ‘\’ and be surrounded by double quotes.

11. Click “Apply”.

12. Go to the lock button and click “Activate Changes”.

13. Restart OHS.

14. Once OHS has been restarted, test the alias in the URL to make sure your files are accessible.

Source: Oracle Support Doc ID 2124492.1

The post Configuring Aliases in OHS 12c appeared first on PITSS US - Oracle Forms Upgrade, Forms to ADF, Forms to APEX, Migration.

Built on PL/SQL, Oracle Forms has been used by many companies and organizations over the years for performing day-to-day operations. Oracle Forms has transitioned from a client/server platform to a web-based platform deployed in Oracle WebLogic Server. With only requiring a download of a JRE (Java Runtime Environment), end users are able to access Oracle Forms applications from any web browser using new technologies such as Java Web Start (JWS) and Forms Standalone Launcher (FSAL). However, due to challenges of organizations maintaining software on PCs and risking potential security breaches through Java, more companies have considered a move away from Oracle Forms or any Java-based platform. Oracle has a solution to this problem, and Oracle Application Express (APEX) is a solution to take into consideration.

Built within Oracle Database, APEX is a low-code development platform which allows you to build and maintain applications which can be accessed worldwide from any device. APEX also has advanced features which allow your application to be more appealing and user friendly without the need of a Java plugin or runtime. APEX is similar to Oracle Forms which it is also built on PL/SQL; thus, APEX greatly reduces a learning curve for developers. Here are some reasons to consider moving from Oracle Forms to APEX:

Similarities Between Forms and APEX

1. With APEX also being built on PL/SQL, developers will not need to learn new programming languages such as Java or C# to develop and maintain applications. Training will be minimized due to that APEX is built in the same language as Oracle Forms and that APEX uses a low amount of code.
2. APEX allows you to utilize Oracle Database features fully.
3. The same database objects may be used in both Oracle Forms and APEX.

Advantages of APEX Over Oracle Forms

1. Java is NOT required to be installed on a PC. This means that end users will not need to have a Java Development Kit (JDK) or a Java Runtime Environment (JRE) installed to run an application migrated or built in APEX.
2. In addition to applications being able to run from any web browser on a PC or Mac, they can also be run on mobile devices such as phones and tablets.
3. Developers will not need to have software installed on their PCs such as Oracle Forms Builder, JDeveloper, or other IDEs to develop APEX applications. Development can be done within a web browser.
4. APEX is metadata-based, and source files no longer need to be stored on the server. For example with Oracle Forms, it is required to store executables (FMXs, MMXs, PLXs, etc.) at the operating system level. This is no longer required with APEX. Thus, developers will no longer need any access to the application server.
5. Designing the user interface of the applications is much easier with different themes and styles pre-packaged within APEX.
6. APEX comes FREE with a license of Oracle Database. If you are migrating from Forms to APEX, you are already using Oracle Database; thus, you will already be licensed with Oracle Database. Best of all, all Oracle Database editions from Express Edition (XE) to Enterprise Edition (EE) support APEX.
7. APEX is also compatible with Oracle Database in the cloud including Autonomous Database. Autonomous Database involves running a full Oracle Database in the cloud without needing to manage the infrastructure. With Autonomous Database, common DBA tasks such as patching, backup, and recovery are fully automated. Click here to learn more about Autonomous Database from Oracle.
8. Accessing APEX applications requires Oracle REST Data Services (ORDS) which must be deployed to an application server. Unlike Oracle Forms, you are not limited to only using Oracle WebLogic Server to deploy ORDS for accessing APEX. You may also use open source application servers such as Apache Tomcat and Eclipse Jetty. As a result, WebLogic licenses are no longer required for running APEX unless you choose to use WebLogic for deploying ORDS.

Next Steps

If you are not quite ready to migrate your entire application to APEX, it is also possible to migrate a subset of your application to APEX and have it work in tandem with your existing Oracle Forms application. PITSS has seen use cases where APEX and Oracle Forms work together to satisfy customer needs. It is absolutely possible to call an APEX application from Forms and an Oracle Form from APEX.

If you are considering moving from Oracle Forms to APEX, please contact PITSS today for how we can help support you with your digital transformation of your legacy application.

Oracle has some additional information regarding APEX on Oracle’s website as well as how you can get started with APEX for FREE. Click here to get started with APEX today.

The post Advantages of Moving from Oracle Forms to APEX appeared first on PITSS US - Oracle Forms Upgrade, Forms to ADF, Forms to APEX, Migration.

All modern releases of Oracle Database have Oracle Application Express (APEX) already installed. However, none of them have the latest version of APEX installed. Before considering a setup of APEX in an Oracle Database environment, certain prerequisites will need to be met. In addition to APEX, it is also necessary to install Oracle REST Data Services (ORDS) in order to access APEX from an application server such as WebLogic or Tomcat. The following information in this article will explain further about the Oracle APEX prerequisites.

Hardware Prerequisites

As APEX already comes bundled with Oracle Database, not much consideration needs to be taken with regards to the hardware prerequisites beyond what is already required by Oracle Database. As you will be upgrading the bundled APEX to the latest APEX release (APEX 20.1 as of August 2020), the supported operating system is the main hardware requirement which will need to be heeded.

Supported Operating Systems

Additional Hardware Prerequisites

Although no other hardware prerequisites are required for APEX (beyond what is already required for Oracle Database), the following prerequisites are needed for running an application server such as Oracle WebLogic Server for hosting ORDS:

• RAM: 4 GB (8 GB or more is preferred for production environments)
• Disk space: 10 GB or more
• SWAP or Virtual Memory: 8 GB or more (16 GB or more is recommended for production environments)
• Network requirements: Either a static IP address or a loopback adapter with a static IP address
• OS User: If installing Oracle WebLogic Server to deploy ORDS, the OS account used to install the Oracle software must be used to run the WebLogic server.

Database Requirements

APEX is supported in the following releases of Oracle Database:

• Oracle Database 11.2.0.4.0+
• Oracle Database 12.1.0.2.0+
• Oracle Database 12.2.0.1.0+
• Oracle Database 18.0.0.0.0+
• Oracle Database 19.0.0.0.0+

During the setup of APEX and ORDS, a SYSDBA account will be required. This is necessary to run a few SQL scripts for setting up APEX (the SQL scripts come bundled with every Oracle Database install). Please consult with your DBA before setting up APEX in your environment.

Software Requirements

Oracle Application Express (APEX)

The latest release Oracle APEX may be downloaded from Oracle’s website.from https://www.oracle.com/tools/downloads/apex-downloads.html. Once you are there, you may click on the link for either all languages or for the English only version.

NOTE: You must have an Oracle account to download software from Oracle. In addition, you must agree to the Oracle License Agreement before you are permitted to download the software. Keep in mind that if you are licensed for Oracle Database, no additional licenses are required for setting up and using APEX.

Oracle REST Data Services (ORDS)

In order to access your APEX environment, Oracle REST Data Services is also one of the Oracle APEX prerequisites. As of August 2020, ORDS 20.2 is the most current release of ORDS. ORDS 20.2 may be downloaded from Oracle at https://www.oracle.com/database/technologies/appdev/rest-data-services-downloads.html.

NOTE: You must have an Oracle account to download software from Oracle. In addition, you must agree to the Oracle License Agreement before you are permitted to download the software.

Supported Application Servers for ORDS

ORDS must be deployed into an application server. The following application servers may be used for deploying ORDS:

• Oracle WebLogic Server
• Apache Tomcat
• Standalone Mode (embedded Eclipse Jetty server)

If you decide to use Oracle WebLogic Server as your application server, you must keep these points in mind:

• You must have a license to run Oracle WebLogic Server.
• It is highly recommended to use at least Oracle WebLogic Server 12c for deploying ORDS. The latest version of Oracle WebLogic Server may be downloaded here if you do not have it already installed (we recommend the Fusion Middleware Infrastructure Installer): https://www.oracle.com/technetwork/middleware/weblogic/downloads/index.html
• Oracle WebLogic Server requires an Oracle JDK (OpenJDK is not supported) to be installed. WebLogic requires JDK 8 (later releases are not currently supported with WebLogic at this time) which the latest update may be downloaded here: http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
• NOTE: If you are using a JDK solely for the purpose of running WebLogic, you should not need a separate Java SE license or subscription. However, it is strongly recommended to verify this with your Oracle representative with regards to your Oracle licensing. Additional information may also be found here (a subscription to My Oracle Support is required to view this information): https://www.oracle.com/java/technologies/javase/jdk-faqs.html

If you decide to use Apache Tomcat instead, you may download it from the main Apache Tomcat site.

Other Notes

After reading our information regarding the Oracle APEX prerequisites, if you are interested in learning more about APEX and how a migration from Oracle Forms to APEX can be advantageous for you, please check out our article here about the advantages of moving from Oracle Forms to APEX. Please feel free to contact PITSS at any time if you are interested in learning more about APEX and how PITSS can best assist you with your migration to APEX.

The post Oracle APEX Prerequisites appeared first on PITSS US - Oracle Forms Upgrade, Forms to ADF, Forms to APEX, Migration.

Earlier we reported that the NPAPI plugin embedded in web browsers to run Oracle Forms applications are not only out of support but also have been removed from web browsers such as Chrome and Firefox. More information on this may be found in our article here. Starting in Oracle Forms 12c, Oracle has certified two other ways to launch Oracle Forms besides using the NPAPI plugin: Java Web Start (JWS) and Forms Standalone Launcher (FSAL). FSAL is a browser-less solution which allows you to run your Oracle Forms applications without needing to use a web browser. Users may be able to access the application by either running a command from Command Prompt or by running a CMD script on the desktop similar to the days when Oracle Forms was a client/server application back in the Forms 6i days. Before you can get started with using FSAL, the following prerequisites need to be met before you can run Oracle Forms using Forms Standalone Launcher:

Prerequisites

1. A couple of web-based parameters will need to be added to the application server’s formsweb.cfg file (more information is covered in this article)
2. Each end user must be provided a jar file, frmsal.jar, from the application server in which Oracle Forms is installed
3. Each end user must either have a JDK or JRE installed. For Oracle Forms 12.2.1.4.0, only JDK 1.8.0_211+, JRE 1.8.0_211+, or JDK 11.0.4+ are supported. Keep in mind that JDK 11.0.4+ is only supported with Forms when using FSAL.
4. The JDK or JRE must be in the end user’s PATH environment variable

Setup

Once all prerequisites have been met, you may proceed with setting up your Forms and Reports environment to use FSAL:

1. Open up formsweb.cfg in $DOMAIN_HOME/config/fmwconfig/servers/WLS_FORMS/applications/formsapp_12.2.1/config

2. Locate your configuration section for your applications. The name of your application section will be surrounded by brackets such as [app]. If you are not using separate configuration sections for your applications, you may configure this within the [default] configuration section. However, if you do so, this must be done before the [sepwin] section.

3. Add the following parameters to the end of your application configuration section:

• If you are not using WebUtil
  • fsalcheck=true
• If you are using WebUtil
  • baseSAAfile=webutilsaa.txt
  • fsalcheck=true

4. Save and close the file

5. If you have not already done so, locate your frmsal.jar file in $ORACLE_HOME/forms/java and provide this to all end users whom will run the Forms application(s).

Launching Your Oracle Forms Application with FSAL

Now that your Oracle Forms environment has been configured, your end users may now run your Forms application(s) using Forms Standalone Launcher:

1. Make sure all end users have either a JDK or JRE in their PATH environment variable.

• Example: PATH=C:\Program Files\Java\jre1.8.0_261\bin;…

2. Open up Command Prompt or cmd.exe.

3. Run the following command to call the app (in this example we will have our application section called “app_fsal”):

• java -jar <PATH_TO_frmsal.jar>\frmsal.jar -url “http://<app_server_url>:<forms_port>/forms/frmservlet?config=fsal”
• Example: java -jar C:\Users\Pitss\Downloads\frmsal.jar -url “http://app-server.domain.com:9001/forms/frmservlet?config=fsal”

Alternatively, you may also configure a batch or CMD script to be set up on end users’ PCs to easily run the java command above. All you will need to do is create the script to run the same java command in item #3 above and place the script on the users’ desktops.

After launching the java command either from Command Prompt or from a CMD script, your Oracle Forms login screen will now appear. You may now log into your application normally. This will allow you to run the app independently from the web browser. If your Oracle Forms application needs to run a report with Oracle Reports, Oracle BI Publisher, JasperReports, etc, a web browser will be launched to run the report using your default web browser.

PITSS.CON is also able to be used with Forms Standalone Launcher. Click here to learn more on how this can be done. For more information regarding Forms Standalone Launcher (FSAL), please feel free to check out Oracle’s white paper here.

The post How to Run Oracle Forms Using Forms Standalone Launcher appeared first on PITSS US - Oracle Forms Upgrade, Forms to ADF, Forms to APEX, Migration.

As of August 2020, there are a few different versions of Java SE currently available for public use. Examples include Java SE 8, Java SE 11, and Java SE 14, the most current release available. Oracle is currently planning to release the next version of Java SE, version 15, in September 2020. With all of the different releases of Java SE available in addition to archived releases such as Java 6 and 7, which are the Java versions supported with Oracle Forms 12.2.1.4.0?

Currently, Oracle Forms 12.2.1.4.0 is the latest and greatest release of Oracle Forms available for consumers from Oracle. As of today, there are no dates set in stone for when Oracle will release the next version of Oracle Forms. Forms 12.2.1.4.0 is currently covered under premier support from Oracle until August 2022. However, this date may always change depending on when Oracle releases a new version of Oracle Forms. With this in mind, these are the following Java versions supported with Oracle Forms 12.2.1.4.0 at this time. Please note that Java SE represents Oracle JDK, Oracle JRE, or both. For any of the Java SE releases not currently supported, we will discuss if these versions could be supported in the future or why they may not be supported:

Java SE 7

Oracle Forms 12.2.1.4.0 is not currently supported with Java SE 7, and Java 7 will not be supported in the future. The reason is that Java 7 has ended premier support back in July 2019. It is advised that all users who are using Java 7 for anything should consider looking into upgrading to at least Java 8.

Java SE 8

Oracle Forms 12.2.1.4.0 is supported with Java 8 Update 211 or higher for both the Oracle JDK and the Oracle JRE. This applies to all methods of running Oracle Forms: using the web browser with an NPAPI plugin, Java Web Start (JWS), or Forms Standalone Launcher (FSAL). Please keep in mind that Java 8 is planned be the last release that will have JWS available. At that point, Oracle will advise that all Oracle Forms users will need to switch over to FSAL when running Oracle Forms. Java 8 is currently available under premier support until March 2022. However, Oracle has stated in My Oracle Support Doc ID 2440615.1 that Java 8 will continue to be available for updates and support as long as Oracle Forms 12c is covered under support.

Java SE 9 and 10

Oracle Forms 12.2.1.4.0 is not supported with either Java SE 9 or Java SE 10, and Forms will never be supported with Java 9 and Java 10. Java 9 and Java 10 were only short-term releases and were taken out of support on March 2018 and September 2018 respectively.

Java SE 11

Oracle Forms 12.2.1.4.0 has limited supported with Java 11 (11.0.4+). It is only supported with JDK 11.0.4 or higher when using Forms Standalone Launcher only per the Oracle Fusion Middleware Certification Matrix for 12.2.1.4.0. Java 11 is not supported when running Oracle Forms 12.2.1.4.0 with the traditional NPAPI plugin (only available with Internet Explorer) or with Java Web Start. The reason is that a JRE is required to use the web browser or Java Web Start for launching Forms applications. Java 11 does not come bundled with a JRE; only a JDK is available. As a long-term release, Java 11 is currently available under premier support through September 2023. If you are interested in implementing FSAL for running Oracle Forms 12c, please visit our article for more information on how you can set up FSAL.

Java SE 12 and 13

Oracle Forms 12.2.1.4.0 is not supported with either Java SE 12 or Java SE 13. Java 12 and 13 were only short-term releases and were taken out of support on September 2019 and March 2020 respectively.

Java SE 14

As of August 2020, Java SE 14 is the latest Java version currently available. However, Oracle Forms 12.2.1.4.0 is not supported with Java 14. Java 14 will only be supported until September 2020. Due to this, it is extremely unlikely that Java 14 will be supported with any release of Oracle Forms.

Java SE 15

Oracle is currently planning to release Java SE 15 in September 2020 (subject to change). It will be covered under support until March 2021. There has been no word whether Oracle Forms 12.2.1.4.0 will have any form of support with Java 15. However, Java 15 is planned to be another short-term release, so the odds of Java 15 being compatible with Oracle Forms 12.2.1.4.0 is very low if not zero. We cannot speak for Oracle with regards to cross compatibility between Java and other Oracle products such as Oracle Forms and when they may release new certifications, but based on previous and current short-term releases of Java (9, 10, 12, 13, and 14), we do not see there being a certification of Java 15 with Forms 12.2.1.4.0 even with FSAL. Oracle will provide more information if Java 15 happens to be certified with Oracle Forms.

If you are interested in learning more about the currently available releases of Java SE as well as to download them, feel free to click here to go to Oracle’s page about Java SE.

If you are running an older version of Oracle Forms such as 6i, 10g, or 11g and you are using Java 7 and older, please contact PITSS today to learn more on how PITSS can help you upgrade your application to Forms 12c today.

The post Java Versions Supported with Oracle Forms 12.2.1.4.0 appeared first on PITSS US - Oracle Forms Upgrade, Forms to ADF, Forms to APEX, Migration.

Java Web Start (JWS) is a more secure way of running your Oracle Forms applications compared to the now deprecated plugin option. With JWS, you can launch your Oracle Forms application by downloading or running a JNLP file using Java Web Launcher. There are a couple available options for running Java Web Start: from a web browser and from an already downloaded JNLP file.

NOTE: Before preparing to use Java Web Start to run your Oracle Forms applications, please review this article to make sure your Forms 12c environment is set up to run Java Web Start.

Web Browser

Similar to accessing your Oracle Forms application using a plugin, you may continue to use the web browser to launch Oracle Forms using Java Web Start. Unlike the plugin where it is only available with Internet Explorer, Java Web Start allows you to access your application with all major web browsers including Chrome, Edge, and Firefox. The reason is that a JNLP file is downloaded, and the Java Web Launcher (comes with JRE 8) will proceed to run the application. However, each web browser handles the downloads of JNLP files differently:

Internet Explorer

Internet Explorer is able to launch JNLPs automatically upon accessing the Oracle Forms application via URL. By default, when the URL for the application is entered into the browser, the JNLP will automatically run without downloading any files. Please note that Internet Explorer is currently being phased out and being replaced by Microsoft Edge.

Google Chrome

Chrome will allow you to download and run JNLP files. The general process for launching a JNLP is done with these steps:

1) Enter the URL of the Forms application.

2) The JNLP file will now download. Unlike Internet Explorer and Firefox, Chrome requires that JNLP files are downloaded before they are run for security reasons. An option at the bottom of the browser will appear asking if you would like to keep or discard the download. Press “Keep” to continue downloading the file.

3) The JNLP will now be downloaded successfully. Click “frmservlet.jnlp” at the bottom of the window to launch the application. NOTE: If this goes away for any reason, you may find frmservlet.jnlp in your Downloads folder (C:\Users\%USERNAME%\Downloads).

Chrome does not allow you to configure a setting to always open JNLPs with Java Web Launcher due to security reasons. For example, if you click the drop-down arrow next to the JNLP download, the option to select “Always open files of this type” is grayed out.

However, if you would like to launch the application without having to download a JNLP every time, you may replace the “http” or “https” in the URL with “jnlp”, and you will only receive a single prompt asking if you would like to open up the JNLP using Java Web Launcher.

Microsoft Edge

Edge is also able to download and run JNLP files. The steps for downloading and running JNLPs are the same as Chrome. In addition, the same restrictions for allowing JNLPs to always open JNLPs with Java Web Launcher as with Chrome are applicable with Edge. Fortunately, the same workaround of specifying “jnlp” instead of “http” or “https” in the URL also works.

Mozilla Firefox

Firefox is also able to download and run JNLP files. Unlike Chrome and Edge, you do not need to download the JNLP file every time. However, Firefox by default does not have JNLP files associated with Java Web Launcher. This must be done manually in each end user’s PC. More information on how to set this up may be found in this article here with detailed steps.

Desktop Icon

Running your Oracle Forms application from a desktop option is the second of options for running Java Web Start. Instead of having to always download frmservlet.jnlp from a web browser, it is also possible to have a pre-downloaded JNLP and run that from your desktop. How this works is that frmservlet.jnlp will need to be downloaded using the steps above. After this is done, the downloaded JNLP may then be customized to be rolled out to all end users. These steps will allow you to set up a desktop icon:

1) Run the Forms application from either Microsoft Edge or Google Chrome so that the JNLP will be downloaded. Do not run the JNLP yet once it is downloaded.

2) Go into C:\Users\%USERNAME%\Downloads (where %USERNAME% is the name of your user account) and copy frmservlet.jnlp to your desktop.

3) The JNLP file has the URL of your Forms application hard coded into the file. If you are setting up the JNLP to access other Forms environments, the URL will need to be updated. If you are planning to use the existing URL, you may skip to step 4. Otherwise, please open up frmservlet.jnlp using a text editor such as Notepad or Notepad++.

Inside the file, look for the codebase parameter (should be the fourth line in the file). That is how the JNLP file calls the Forms application. If you are planning to run the JNLP against a different hostname than what is configured, you may change the hostname in the URL.

4) You may now deploy the JNLP file in all end users’ PCs. Please note that you may not be able to email users the JNLP file because many email servers will block Java-related files.

NOTE: For users to launch JNLPs, they must have Java Runtime Environment (JRE) 8 installed on their PCs. The JRE will come with Java Web Launcher, the program required to run JNLP files. Either 32-bit or 64-bit JRE 8 will work.

Oracle has some additional information regarding both Java Web Start and Forms Standalone Launcher in its white paper. You may click on this link here to read the white paper. Contact PITSS today if you would like any assistance setting up your Oracle Forms environment to run with Java Web Start or Forms Standalone Launcher.

The post Options for Running Java Web Start appeared first on PITSS US - Oracle Forms Upgrade, Forms to ADF, Forms to APEX, Migration.