I got this document in which they provided how to implement SSL in standalone OC4J.
I have done all configuration according to the document but I got below message when I run the form in HTTPS mode.
Can anyone help me?
This document is for OC4J 10.3.5; I guess it simply doesn't apply to the version of oracle forms.
Why do you even bother configuring OC4J with SSL? This configuration most certainly isn't out in production, so it is a completely useless config to test with if you want to simulate a real scenario.
I didn't want to install a full blown application server for testing purposes either on my machine, so I simply installed it on a virtual machine which I start up when needed.
With a VM you also can make use of snapshots which means every time you might screw up the config you take a snapshot; if you screwed it up => revert to snapshot. If it works => delete the snapshot (or revert it if the changes are not going to be permanent). For testing purposes I never ever install Software on my host again. I have dummy-VMs for that; if the test-VM is going to last I simply copy the dummy vm.
You are absolutely right. Just i want to implement HTTPS with Oracle developer suite in my laptop VM as i can not install Application server in my VM due to performance issue.
Anyways Thankyou for the help.
Performance issue? How old is your hardware? I am running OAS 10.1.2.3 on a Server 2003 VM which basically consumes 512MB RAM and ludicrous amounts of CPU/IO.
In any case: as said if you want to test SSL in a real life scenario then enabling SSL in OC4J is not what you want to do. In production the configuration is completely different, as there you would configure Apache to run your forms via SSL.
What comes to my mind would be to install Apache 1.3 (this would be the version OAS 10.1.2 uses), configure mod_oc4j there and configure it with SSL. On the other hand this also isn't the configuration you have in production so this also is not exacly what you want.
If you want to verify if your forms application will run via SSL then most certainly it will run without changing your sources. The only things you might have to change would be if you do HTTP Requests from the database to your application server via utl_http or from the client to the application server via java beans or via the java importer.
But for tests I'd strongly recommend doing it via an application server installation, and not via developer suite.