| Author |
IBM Web Content Management Content in a Portlet Java Edition 1.1...
|
|
| mocheng 2004-03-16, 12:34 pm |
| Anyone get this to work? I can't get this to work, call IBM support, they are scratching their heads...
| |
| Michael Yashin 2004-03-17, 9:41 am |
| Hi,
What problem do you have (exactly)?
It works. Some problems with national suppor, but in general...
Regards,
Michael Yashin
| |
| mocheng 2004-03-17, 9:41 am |
| strange problem.... When i go to the portal, setup the content management portlets. click on Configure, put in all the information, clck on Edit on the Content's tab... I see the content management applet, select the one i want, and click update, it just
went back to the orginal screen. there's no content shown... I was following the "Quick Guide to using IBM Lotus Workplace Web Content Management Content in a Portlet...
Thanks,
| |
| Michael Yashin 2004-03-18, 9:40 am |
| Hi,
You have intalled ILWWCM on the same server with portal?
It doesn't work in such configuration. I don't know why. 
You can deploy ILLWCM on separate AppServer and all will be ok.
P.S. I'll try asking IBM support....
Regards,
Michael Yashin
| |
| berguss 2004-03-25, 11:34 am |
| I am having the same problem after I configure the content management portlet and hit update I go back to the login page.... Any help is appreciated
| |
| mocheng 2004-03-25, 11:35 am |
| for those of you installing them on the same machine, you need to rename the Server1 cookiename in the WAS console to something else other then JSESSION. i rename mine to JSESSION2. restart WAS, then it will be fine..
Cause it's having conflict with the websphere portal cookie.
| |
|
| Same here, changed the Cookie name and everything seems happy now.
However, I do have a question about the Help documentation in WAS Admin console -
************
Cookie name : Specifies a unique name for the session management cookie. The servlet specification requires the name JSESSIONID. However, for flexibility this value can be configured.
************
I'm curious exactly what this means and how it is affecting the WAS server.
Thanks for the help so far,
Scott
| |
| mocheng 2004-03-25, 12:37 pm |
| I thought the Content management crashing every 2 hours was the effect of changing the cookie names.
But since someone else was having the same problem without changing the cookie names(installed on 2 servers).
I think it has no effect so far...
You will experience crashing also. so be prepared...
by the way, does your company order any IBM support? I know it is quite expensive. But it took out a lot of headaches, especially for big application like websphere.
| |
| tamgroup_matt 2004-03-25, 8:56 pm |
| Use the following Environment variable to <most likely> fix your ILWWCM 1.1 server crashing problem on WAS 5.02.
JITC_COMPILEOPT=NQOPTIMIZE{com/aptrix/util/ReadWriteLock}{readLock};NQFSESCAPE{com/aptrix/indexing/*}{*};NMMI2JIT{com/aptrix/indexing/*}{*};
The jitc_F1.dll seemed to have fixed this for 5.01, but this dll is not supported in 5.02. Use the above variable.
Matt | |
| Massimo.Buonomo@deltadator.it 2004-05-12, 3:35 am |
|
<br><font size=2 face="Verdana">I tried the solution i post. It was successfull.
try This:</font>
<br>
<br><font size=2 face="Verdana">If you have both portal and ILWWCM running
in the same machine, you could<br>
edit the <ETC>/hosts file with the following setting. Mine
is in<br>
C:\WINNT\system32\drivers\etc<br>
<br>
127.0.0.1 localhost varad.raleigh.ibm.com<br>
varad.goodone.com<br>
<br>
When you configure the portlet you could use varad.goodone.com for the<br>
ILWWCM hostname and use varad.raleigh.ibm.com for accesing portal.<br>
This of course assumes that you will be accessing ILWWCM from your own<br>
machine. If you are accessing it from somewhere else, then add the<br>
following on the client machine's hosts file. (This has to be done if you<br>
have portal and ILWWCM installed on a vmware also. The DHCP address would<br>
be the ip address of the vmware.)<br>
<br>
<YOUR DHCP IP> localhost
varad.raleigh.ibm.com<br>
varad.goodone.com</font>
<br>
<br><font size=2 face="Verdana">Try also to specify in the portlet the
ip machine instead of the fully qualified host name.</font>
|
|
|
|