Consume A Web Service

I'm trying to use TeamSite (7.4.1) web services to do the following:

1) From an external server, invoke a TeamSite web service to authenticate and create a Client instance

2) Invoke another TeamSite web service to import a file into a provided workarea

3) Call a final web service to de-authenticate

I've been combing the docs, and it's been a lesson in futility. So, I think I would use the util web services, found at

http://localhost/iw/services/cm/2.0/utilservice?wsdl

Beyond that, I can see it appears possible, but putting it all together seems murky.My goal is to have my external process construct a URL to consume the correct web serivce, then perform an HTTP post to the URL in order to import the file to the workarea. Is this possible? Any pointers you have would be a big help. Thanks.

Find more posts tagged with

Comments

Rick Poulin

JRomeo wrote:
Beyond that, I can see it appears possible, but putting it all together seems murky.My goal is to have my external process construct a URL to consume the correct web serivce, then perform an HTTP post to the URL in order to import the file to the workarea. Is this possible? Any pointers you have would be a big help. Thanks.

Yep, it's absolutely possible. I hope you left something out when describing your requirements though, because you could easily just post to a TeamSite URL itself.

In what language are you writing your web services client? That answer will drive most any development suggestions.

JRomeo

Posting to a TeamSite URL sounds perfect. This will be a text file. Just need to authenticate (right?), import the file the same way I would through ContentCenter to a workarea of my choice, and that's it. Do you have any links you might point me to for the option you suggest?

Rick Poulin

In this case, you'd be looking at building a basic Java servlet (see examples here) and running it in the ContentCenter application (see the UI customization guide).

The "magic sauce" is that in your web.xml, you'll want to wrap your custom servlet with the filter called "authentication". What this does is that if an unauthenticated user would attempt to use your servlet, it would first send them to the login page. Then, your reference to the CSClient object could be retrieved via

CSClient client = (CSClient) request.getAttribute("iw.csclient");

Alternately, you could allow anonymous uploads by creating a CSClient running as a service account (or SYSTEM or root) and then connect to TeamSite that way.

JRomeo

Great. However, there will be an external process posting this content, so redirecting to a login page for a web browser wouldn't apply.

The CSClient code you provided makes perfect sense, and I hate to seem like a TeamSite newb, but I'm not sure where this code would be placed. Do I create it as part of a servlet, write a JSP to access it, insert it all into the custom 'customer' area in TeamSite, reset the server, and I'm all ready?

Rick Poulin

Great. However, there will be an external process posting this content, so redirecting to a login page for a web browser wouldn't apply.

Sounds like you'd want to go with the anonymous access then. Depending on the context, you might want to employ some other strategy to validate that your URL is only called by your external process and not by some meddling users.

Do I create it as part of a servlet, write a JSP to access it, insert it all into the custom 'customer' area in TeamSite, reset the server, and I'm all ready?

You'd want to place all of these changes in TeamSite/local/config/lib/content_center/customer_src and then run the make_toolkit.ipl process. This is explained in the UI Customization Guide. And yes, the bit about getting a CSClient would be part of your servlet code.

JRomeo

I'll check it out. Thx.