Confusion on v2 of PDK install

Question

All,
Pardon me for stumbling here; Im converting from Microsoft to Oracle :) So much of this is foreign to me.
I have successfully downloaded the most recent 9iAS v2 release dated August 25th I believe. Ive installed the infrastructure and the enterprise edition (I selected all). I have language support going too. The portal runs great on port 7779 and Im hungry for more.
Ive downloaded the current JPDK and unzipped it and read the install docs. Im not getting something. :(
Ive compared the jpdk.ear files and the new download is more current and as per instruction, I just copied it right over the old jpdk.ear. The server.xml reflects correct information already <application name="jpdk" path="../applications/jpdk.ear" />
. I had to change the http-web-site.xml to reflect <web-app application="jpdk" name="jpdk" root="/jpdk" />
I restarted the Enterprise Process Manager hope this starts the OC4J? Verified via EM on port 1810 and they are all running. Launched my browser and went to http://{server}:{port}/jpdk/providers/ and got a list of all the providers. Congratulations! You have successfully reached your Providers Test Page. Sounds good so far eh?
When I type in any of the provider names, I receive the following error: 500 Internal Server Error oracle.webdb.provider.v2.utils.soap.SOAPException: Cant read deployment properties for service: Lottery .
Reads like I did not properly deploy the ear file or something. My goal is to utilize the URL and Web Services features of the PDK.
Am I on the correct path?
Thanks You All
Chase

Answer 1

Hi Chase,
Here are a few pointers to your issues,
1) The JPDK Framework has uses the following timeout values
- executionWarningTimeout (default value is 20 seconds)
- executionKillTimeout (default value is 80 seconds)
The "warning timeout" lets you identify portlets that consistently fail to meet performance targets and the "kill timeout" attempts to interrupt any requests that appear to be hanging.
Yoy can get more information on this from the document pdkjava.v2.releasenotes.html that comes along with your pdk.zip download.
The "Slow Rendering Sample" tries to highlight this feature.
2) At any point of time you can have only one jpdk.ear file deployed on your OC4J (under the same name jpdk). You can always have different instances of jpdk.ear file deployed but with different names eg. jpdk_1.ear etc.
So each context of JPDK inside your OC4J would have its unique directory structure.
Now when you register a provider you provide the context path like
http://host.domain:port/jpdk/providers or for another jpdk_1 instance as
http://host.domain:port/jpdk_1/providers
Since, the context root varies (jpdk or jpdk_1) you can find out which portlet inside that is getting rendered.
3) As regards the version of JPDK, we usually follow the JPDKv1 & JPDKv2 convention. Here, JPDKv1 (is JPDK 3.0.9) & JPDKv2 (is JPDK 9.0.2). Every month we have a new release of JPDK by the name like JPDK October which will contain both JPDKv1 & JPDKv2.
If any of your doubts are unanswered please get back.
Regards,
Abhinav