At the time of writing this post, Oracle Forms 11g installations are configured by default to work with a specific JPI (Java Plug-In) version: 1.6.0_12. You can verify this by checking your formsweb.cfg file: grep jpi-version formsweb.cfg #jpi_mimetype=application/x-java-applet;jpi-version=1.6.0_12 Unfortunately, it seems Firefox is very particular when it comes to JPI versions, and it will only run with the
Author Archives Garth
First of all, shutdown your domain (in this example, my domain is called ‘oldDomain’ and has one Managed Server): export MW_HOME=/u01/app/oracle/middleware export WLS_HOME=$MW_HOME/wls_10.3.6 export DOMAIN_NAME=oldDomain export DOMAIN_HOME=$MW_HOME/user_projects/domains/$DOMAIN_NAME $DOMAIN_HOME/bin/stopWebLogic.sh $DOMAIN_HOME/bin/stopManagedWebLogic.sh ManagedServer_1 Remove the domain entry from the Node Manager file: vi $WLS_HOME/common/nodemanager/nodemanager.domains …remove this line: oldDomain=/u01/app/oracle/middleware/user_projects/domains/oldDomain Remove the domain registry entry relevant to your domain: vi $MW_HOME/domain-registry.xml
The Oracle APEX Listener is a Java based alternative to using Oracle HTTP Server (OHS) with mod_plsql. In the past I’ve installed early versions of APEX 3 using this configuration, then later on started using EPG (Embedded PL/SQL Gateway) which worked fairly well. Recently however, I decided to try using the latest APEX Listener 2.0.1 on WebLogic 12c
A standard Oracle 126.96.36.199 database installation comes bundled with Application Express (APEX) 3.2.1 by default. I’m going to upgrade to the latest version of APEX (currently 4.2.2) and then configure the Embedded PL/SQL Gateway (EPG), which uses the Oracle XML DB HTTP components within the database itself, so I don’t need to run a separate HTTP server. First
Forms 11g – Java client hangs at security warning with “The application’s digital signature cannot be verified”
Having modified our formsweb.cfg file recently to configure WebUtil in our Forms 11g installation, we started hitting issues when trying to access various form-based application URLs. When the security warning window appears (below), usually you would tick the check-box and run the application: In this instance however, the window turned completely unresponsive and just hung, resulting in the Java
Having had to run through this process again recently, I thought I’d tidy up my notes on all of this, and put together a proper how-to post When SQL Server 2005 was released, the added functionality of Database Mail came with it, giving us the ability to use SMTP to send email from SQL Server instances.