Content Services Foundation vs CSSDK

I'm having a little difficulty figuring out whether I have the right stuff installed to do some experimentation. So far as I know (didn't do the install myself), CSSDK was not installed on our dev server, but when I look at Add/Remove Programs, I see Interwoven Content Services Foundation listed. Is this the same thing, or do I need to go ahead and install the SDK (tried to do it the other day, but ran into the problem where you have to call support (who aren't open until tomorrow) to get a tar file and do a manual install.

Is the best way to figure out if I can talk to it or not to just go ahead and write a perl script to connect via SOAP and see if it will take a request?

Find more posts tagged with

Comments

Bowker

You didn't say if you were trying to do SOAP or not.

You will need the following In the <IWHOME> folder (in my case: e:\apps\interwoven\teamsite):
cssdk.dll
cssdk.cfg
cssdkiface.jar
cssdkjini.jar
cssdksoap.jar (Available only if you have a developers license - I think)

In that folder I also have other folders including: docs, fastcgi, camples, wasp4.5.1,wsdl

I'm not really sure how many of the following files I really need in my classpath. If anyone knows and can set me straight, I would appreciate it.

On my client machine Ive got in my classpath: (all in c:\cssdkcl\)
axis.jar, commons-discovery.jar,commons-logging.jar, jaxrpc.jar, cssdksoap.jar (not sure I need this one here or not), jaxrpc.jar, jcert.jar, jnet.jar, jsse.jar,log4j.jar,saaj.jar,wsdl4j.jar,xercesImpl.jar, xml-apis.jar
Also in that file is some (very little) very important information about SOAP setup.

I'm now up and running thanks to a bunch of help I've received here. If you look at all my posts for the past few weeks in this forum, you may find information to help you get going.

Dan Bowker
Northern Trust
Web Publishing Technology

Migrateduser

Yes, my plan is to connect via SOAP from a remote application. My test app will probably just be a quickie perl script, but any actual applications that get built will probably be .Net. I have all of the files mentioned in the cssdk folder under <iw-home> (which is what confuses me since we didn't install CSSDK - I confirmed this with the app admin who did the install).

I'll take a look back through your posts and see if I can find what I need to get going.

Thanks
Rob

Bowker

From Perl, I'm not sure how to get the connections setup correctly. One thing we found that was STRONGLY suggested was that we setup a separate web/app server (we used Tomcat5.5) instead of the standard TeamSite Tomcat instance to handle the soap requests.

It also will make upgrades/support much easier to separate the two so when Iwov upgrades anything I'm not worried about them removing my code/classes/...

Good Luck

Dan Bowker
Northern Trust
Web Publishing Technology

Migrateduser

You mean get the tar file for the CSSDK and install it under a separate app server?

In the meantime, I've hit my first major snag following the documentation. The sample properties file on p.12 of the cookbook has


serviceBaseURL=http://mteverest:90

The unhelpful comment just says that the port is the port of the HTTP server. Given that the customer web server, the proxy server, iw-webd, and iwservletd all speak HTTP, the comment is pretty useless. I'm guessing I should either point it at port 80 or port 8080, but it's not clear which. I may have to resort to trial and error. In the long-term, if I follow your suggestion to set it up under a separate app server, then obviously it would be the hostname and port of that server.

Bowker

Almost...

That was my first hurdle too. Actually the TeamSite server starts the FASTCGI application when it starts up. The actual SOAP connection goes to port 80 on that same server. Remember TeamSite is the server that's actually servicing the back-end requests for information.

The "other" web/app server is handling the applications that make the SOAP connections. Therefore my ".properties" file looks like this:

# creates a CS SOAP factory
com.interwoven.cssdk.factory.CSFactory=com.interwoven.cssdk.factory.CSSOAPFactory
# use the machine name and HTTP port of the ContentServices SOAP server
serviceBaseURL=http://ilc2cha:80

I have also found it necessary to create a second properties file that lives on the same box as the TeamSite server so external apps that are triggered by workflows can use the getClientForTrustedUser method of the CSLocalFactory class. This is necessary for performing tasks like "transition" (IWCallback).

Dan Bowker
Northern Trust
Web Publishing Technology

Edited by bowker on 12/28/04 09:16 AM (server time).

Migrateduser

I think I'm beginning to get a clue about what I need to do to connect from a perl script. After reading chapter 4, it sounds like I need to generate a client stub. I don't really get why, since the book on Programming Web Services in Perl and the SOAP::Lite perldoc mostly talk about connecting to an existing web service directly.

So, I'm thinking I need a copy of WSDL2Perl or a similar util on the client machine, but not necessarily a copy of the CSSDK? Then I point WSDL2Perl to the one of the WSDL files (do I need to create a stub for each?) and generate a module on the client machine. After that, I can connect by using the module? Anyone have any insight on this?