Support WebLogic & WebSphere

[GoogleCodeExporter]

This is important for large corps

Original issue reported on code.google.com by jeffreyl...@gmail.com on 4 Jun 2008 at 2:45

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I have already ported to Oracle. Now that weblogic belongs to Oracle, the 
preferred
platform for Oracle is less clear, because they have 2 really good application
servers. I would suggest to support my porting. 

Original comment by luis.per...@gmail.com on 22 Jul 2008 at 11:18

[GoogleCodeExporter]

Websphere is on the horizon at our company - having a connector available would 
be
very beneficial.

Original comment by timha...@gmail.com on 19 Aug 2008 at 6:27

[GoogleCodeExporter]

This issue means porting CM to WebSphere app server, not crawling websphere 
portal.

Original comment by jeffreyl...@gmail.com on 22 Sep 2008 at 7:36

[GoogleCodeExporter]

+1 for a version of the connection manager that runs on WebSphere Application 
Server
(WAS). I'm finding that clients are trying to consolidate server platforms - 
and they
are very hesitant to add another one (Tomcat in this case) after just 
eliminating
another. 

Has anyone successfully ported the connection manager to WAS? It looks like I'm 
going
to have to at least give it a good try.

On a related, but separate note, I think it will be much more of a challenge to 
port
the GSA Valve framework since a "valve" is Tomcat-specific technology. Note 
that the
GSA Valve has nothing to do with connection manager. It is a Google-provided SSO
helper for the appliance.

Brad

Original comment by Brad.Thu...@gmail.com on 16 Oct 2008 at 11:17

[GoogleCodeExporter]

Just wanted to quickly share my experience so far in getting the connector 
manager
[just] running on WAS 6.1. 

Basic steps
* Build the connector-manager.war from SVN source. I'm not sure if this is 
necessary,
but it is where I started.
* Edit applicationContext.properties in the .war file and add line:
catalina.base=F\:\\IBM\\WebSphere\\wp_profile

where the path points to your WAS profile or parent directory of your logs 
directory

* Replace the 2.0.x spring.jar with the 2.5.5 spring.jar. The 2.0.x Spring was 
having
trouble reading the connector's Spring bean file. I read somewhere that 2.5.3+ 
help
with this.

* I bundled my connector jar file in with the connector-manager.war WEB-INF/lib
directory, but it may be possible to add this later to the path. I'm not sure 
if WAS
would like this though since it has a more formal deployment process

* Open the admin console and install a new enterprise app. Point it to the
connector-manager.war file and provide connector-manager as the context path. 
Just
click next through the wizard.

That seemed to do the trick feeds are being sent to the GSA

Remaining issues (that I know of):
* The google-connectors.feedX.log.n files are being created, but they are all 0 
bytes
in size.
* SystemOut.log has numerous Warnings from
com.google.enterprise.connector.common.JarUtils about "Unable to access Jar 
Manifest"
* There are surely many more

Hope this is helpful to someone

Brad

Original comment by Brad.Thu...@gmail.com on 30 Oct 2008 at 3:13

[GoogleCodeExporter]

Original comment by mgron...@gmail.com on 6 May 2009 at 10:03

• Added labels: Milestone-Goal_2.4.0

[GoogleCodeExporter]

Original comment by jl1615@gmail.com on 18 Sep 2009 at 8:35

• Removed labels: Milestone-Goal_2.4.0

[GoogleCodeExporter]

Original comment by mar...@google.com on 4 Dec 2009 at 11:18

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Any news on this?

I see it has milestone 2.4.0 so websphere support should be there already?

Original comment by keesvanb...@gmail.com on 14 May 2010 at 11:09

[GoogleCodeExporter]

Original comment by jeffl...@google.com on 16 May 2010 at 2:55

[GoogleCodeExporter]

Priority lowered, no plan to fix in the near future.

Original comment by jeffl...@google.com on 16 May 2010 at 2:58

[GoogleCodeExporter]

Is there still no progress on running the Connection Manager on WebSphere 
Application Server?

Original comment by evanbory...@gmail.com on 29 Mar 2011 at 9:31

[GoogleCodeExporter]

Looking at Brad's notes, we're now using Spring 2.5.6, and I'm working on the 
bug that creates the "Unable to access Jar Manifest" warnings. The 
catalina.base definition is a known issue (the same workaround is needed for 
and works with JBoss), and the feed log behavior is normal.

If you want to help, bug reports (with detailed logs), possible workarounds and 
best of all fixes are always appreciated. If you can send a stack trace from 
WAS for the "Unable to access Jar Manifest" warnings or want to test the bug 
fix, let me know.

Original comment by jla...@google.com on 6 Apr 2011 at 6:17

[GoogleCodeExporter]

Hello,

I encounter problems on deploying on Weblogic 10.0 / connector-manager 2.6.6 / 
spring 2.5.6 : did you get further on the bug that creates the "Unable to 
access Jar Manifest" warnings ? (in comment 15 jla...@google.com mentionned 
that).

I applied the suggestions of this thread, but I still can't create DBconnectors 
in GSA console (whereas with tomcat it worked...). I get a message (sorry for 
maybe bad translation from french) "The planning version used by the connector 
manager is missing or unknown. Make sure you have registered a connector 
manager compliant with Google Search Appliance."

Another difference between tomcat and weblogic is that the servlet 
/testConnectivity do not return the app version :
http://___:9003/connector-manager/testConnectivity
<CmResponse>
<Info>
Google Search Appliance Connector Manager ; Sun Microsystems Inc. Java 
HotSpot(TM) Client VM 1.5.0_06; Windows XP 5.1 (x86)
</Info>
<StatusId>0</StatusId>
</CmResponse>

I would tend to think that these warnings are linked to the lack of version in 
the servlet. And then to the blocking message when deploying a connector in GSA 
console. Weblogic security problem ? Needs a specific non-standard packaging ?

Thanks for your help.

Yann

Original comment by yann.fey...@pole-emploi.fr on 4 Aug 2011 at 2:50

[GoogleCodeExporter]

This issue is filed as Google issue #6514021

Original comment by tdnguyen@google.com on 18 May 2012 at 9:52

• Changed state: Duplicate