05-14-04 05:37 AM
I found out this by myself. If any one else is having a same problems here i
s the answers
The trick is to use the proper publish URL and create the datasource properl
y. Because of the changes to datasources in WAS v5 with regards to J2EE 1.2
vs. J2EE 1.3 apps, you have to create a v5 datasource with a JNDI name of '
jdbc/wpcpsample'. This can point to any DB that IS NOT the same as the WPCP
authoring DB. If you use the same DB, then you'll hit some major problems
with the runtime and authortime WPCP resource tables overwriting each other.
Now, because the datasource is v5, and the portlets that pull the data back
are v5, you can't publish to <hostname>/wps/PersAdmin/publishtarget, as that
is a J2EE 1.2 app, and requires a v4 datasource. Consequently, there's ano
ther publish target in the sample10.war, which should have a URL like <hostn
ame>/wps/PA_1_0_69/publishtarget, you'll have to check where the sample10 go
t installed under WPS_HOME/installedApps (for the '1_0_69' part, yours may b
e different, as it depends on your WPS install)
[ Post a follow-up to this message ]
|