Kidda urgent --Portal, Apache, OC4J -- the Saga Continues

Question

Ok, so OC4J is great! Wonderful!
As I've mentioned in a previous post, I'm developing a JSP portlet using JDeveloper. I'm deploying it to an OC4J server -- the same computer where I have the Portal installed. It seems to work, but...not really.
I CAN see my JSP portlets, I CAN redirect to different JSP pages I've created (all the in the context of the Portal), but I CAN NOT save anything in the SESSION object.
After spending a day investigating into it, I've realized that, for some odd reason, every time I click on a link in my JSP page in the Portal, I get a different SESSION (used session.getId() method). Thus, I can not save anything in the SESSION.
I've added in my Apache HTTPD.CONF file the 3 lines of the MOD_PROXY (guidelines in "getStart.htm"), but I've also noticed that at the end of the file there are still 'commands' telling it to use JServ.
I think that the SESSION problem is caused because of 2 issues:
1) The transition from JSERV to OC4J was incomplete. When I try to take those last few lines that deal with JSERV off the HTTPD.CONF file, the HTTP ORACLE service (in Windows) doesnt come up at all.
2) There's also the problem of cookies -- the Apache server is on one port, the OC4J on another. So cookies can not be saved. I've "CHECKED" the thingy in the Portal where you define a Porlet Provider ("Same cookie domain" or something), and it didnt help.
SO! First, I wish to turn the Portal from using JServe to using OC4J. Does anyone have COMPLETE instructions on how to do it? Step by step please....
Second, I also ran into the problem of 'translating' JServ 'terms' into OC4J. When registering a JSP portlet, you must include some aliases in JSERV files -- files that DO NOT exist in OC4J. (jserv.properties, etc). You know how you're supposed to run a certain test, like "IsItWorking" to know that your portlet is fine? So how? (using OC4J, of course)
I realize that this must be the LONGEST post anyone has ever written, but I thought it would be best to describe EVEEEEERYTHING to get the best answers.... :-)
Thanks in advance!
Dan

Answer 1

Dan,
It is great to see you already developing portlets on OC4J. In PDK April, we are offering a production pre-release of PDK-Java release 2 based on OC4J. You can use that to display your J2EE-based application as a portlet on Oracle9iAS Portal 3.0.9.x.x and/or Portal 9.0.2 (when available). We will provide detailed articles and this should be a very easy setup especially if you are already familiar with OC4J.
One thing... from your question, it also sounded like you were considering moving Oracle9iAS Portal (not just PDK-Java) from JServ to OC4J. Just to clarify, you will be able to register your J2EE-based portlets using PDK-Java 9.0.2 (available in PDK April -- by next week) again Oracle9iAS Portal running JServ.
Oracle9iAS Portal itself is support on OC4J in version 9.0.2. This release will be available as part of Oracle9i Application Server release 2. The only supported, tested, and certified way to move Oracle9iAS Portal 3.0.9 to OC4J is using the Oracle9iAS release 2 universal installer, it will update your files and enable Oracle9iAS Portal to successfully run on OC4J instead of JServ.
I strong suggest you wait for the release to migrate and in the meantime, use PDK-Java 9.0.2 to display your portlets against Portal 3.0.9
Hopefully this helps,
Sue