How the integration with BEA is done?

Hi everybody,. Im newbbie in this area of Interwoven, I need to do the integration of BEA weblogic and Interwoven conter management, But I do not know anything about how can be this done? Any idea about how to start with this?
THX

Find more posts tagged with

Comments

sunil_j

Hi,

What do you want to achieve by integrating BEA weblogic and Interwoven content management Server ?

Regards
Sunil

Interwoven TeamSite Consultant

nipper

You can have a tight integration or a very loose one. It all depends on what you want to do. Can you characterise how you would like the products to work together ? What type of developers/content contributors do you have ? How do they work ?

We do pretty basic integration, create info via templates, push the templates, via DataDeploy, to a DB WLS can see, and then, using some proxy settings to allow the end users to peruse the final results. We are not using the Turbo, nor do we use the seperate DB views (that offers some interesting functionality but als complexity).

Now, if you are really a rookie & have no idea what you are doing, take my advice & don't try this at home. This is for a trained professionals & all you will do is really tick off your customers. Bring a consultant in or get some training. Both is prefered. Anyone half way competent could do this in a week if you know what needs to be done,

HTH

Andy

Migrateduser

We just finished a BEA integration DevNet webcast. You can find the recording here:
http://devnet.interwoven.com/site.fcgi/webcasts/index.html#webcast-27

This should explain the 3 types of integration most commonly done with BEA WebLogic.

Regards,

lissa

Migrateduser

Sunil, I need to integrate some functionality development in Java (registration form, dinamic information,etc) with the current site that is working with teamsite. I do not kown much about interwoven, but Im a java developer and I need to find out how to create this interaction about the interwoven content and the applications that Im developing.

Migrateduser

Lissa, thanks for the link I will read it

brave

Hi Lissa

I am interested in approach 2 outlined in the webcast. We would like to make our files (images, html, etc.) available to the portal via the filesystem (instead of putting them into the BEA Repository as in approach 1). We would like to store the Metadata in an Oracle database.

Slide 19 of the Weblogic Portal/Teamsite integration document seems to indicate that a Service Provider Interface (SPI) is necessary for communication between the RDBMS and the Virtual Content Repository.

Slide 20 makes it seem like the BEA SPI will handle communications between the RDBMS Metadata Repoisitory and the Virtual Repository.

How is the communications between the RDBMS Metadata Repository and the BEA VIrtual Repository accomplished? Does interwoven provide the SPI? Does BEA provide it? Would we have to write it ourselves (or have Interwoven Professional Services do it)?

brent1

I, too, have viewed the webinar regarding Interwoven/BEA integrations and (unless I am missing something) I think there is a hole that a JSR 170 compliant interface would fill.

The webinar outlined 3 approaches for integrating Interwoven and BEA.

1) TeamPortal - This really seems to address the requirement of accessing TeamSite *functionality* from the portal. While I see this as useful, I don't think it is meant to address the issue of accessing the actual *content* stored within TeamSite for other applications.

2) Create content files using standard templating techniques along with the appropriate .md.properties file for Bulkloader - The Bulkloader process has a major hole with regard to removing content. Any deleted content would have to removed from the BEA repository manually. Unacceptable.

3) Deploy to custom DB; build custom BEA SPI to this DB - This would be quite a bit of work. This work would probably have to be repeated for each application that we build as the custom DB changes. Not pretty.

It seems to me that TeamSite needs to be treated as a repository with a JSR 170 compliant interface (aka SPI). I know Interwoven does not like to think of TeamSite as a repository as it is not optimized for production content delivery. The good news is, that the application server can cache the content once it pulls it from the repository. This means TS does not have to be optimized for indexed searches and whatnot.

I believe Interwoven sits on the expert group for JSR 170 <http://jcrep-jsr.day.com/content/playground/en/jsr_detail.html>.

I look forward to hearing suggestions for overcoming this integration challenge.

Brent
Beckman Coulter Inc.

Migrateduser

Brave,
Your approach is the most flexible and powerful and is the route selected by many of our customers.

Since your (and each customer's) metadata structure is unique, the SPI interface to the Metadata repository needs to be built, . Interwoven services can build or support you in building the SPI.

Please contact me at paul.loeffler@interwoven.com if you would like to discuss this process further.

Regards,
Paul

Asit

Hello Paul,

I saw the webcast presented by you on the integration between BEA WLP and Interwoven TeamSite. I have also read the related forums.

I am interested in integrating the two for weblogicportal server 10.0 to be able to use the content managed by teamsite 6.7.1 to make it appear on the portal for the customers.

I have a few related questions of you could help me with them please

1. Do we have any other approach to the integration apart for the three approaches presented in the web cast.

2. I was thinking of one possible approach as follows. Wanted to validate the idea with you

Can I store the content as well as the metadata in a custom DB and then use SPI to help the portal fetch and display the data though the JSPs containing weblogic CM tags.

(A) Is this possible ? If so how can I develop the SPI. How can interwoven help in this.

(B) Will data deploy help me to store content created as DCRs in TeamSite into the custom DB (RDBMS).