nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

LiveSite - ECM Connector Integration

Aryan

Hello,

Is there a way of picking up images from MediaBin in a livesite component?

What I mean to ask is this:

Using ECM Connector can I fetch images from MediaBin thru/in a livesite component?

Please let me know if this is possible.

Thanks,
Aryan.

Find more posts tagged with

Comments

nipper

I doubt you can go directly from MB to LS, you can put TeamSite in between and use the ECM connector to put the images to TS, then LS.

Aryan

Thanks nipper, I thought as much...

Any ideas, shanon???

Aryan.

cliff1

Shanon is the expert, but I can add a quick bit of information. The integrations to date have involved using the LiveSite page editor to invoke the ECM Connector browse dialog so page designer can leverage the MB assets on the page. This seems like the best approach if you are using the MB image on your LiveSite page(s), because you will want to deploy the appropriate renditions to your LiveSite production server and should have a snapshot (edition) of all of the deployed assets in TeamSite. Several customers have already deployed this type of solution on top of ECM Connector 2.0.

However, if you are looking to build a LiveSite component that allows the consumer of the website (i.e., the end user of the production site) to browse MediaBin and select images (maybe for the purpose of selling high-res images?), you are in new territory. Having the LiveSite page forward off to the MB Web UI would be easy, but if you want a custom MB UI for your website consumers, you are looking at more work.

What are you trying to accomplish?

-Cliff

shanon

Hey all-

I just posted a verbose HowTo on this subject ...

[post=83124]HowTo: Integrate MediaBin with LiveSite using the ECM Connector 2.0[/post]

Thanks,
Shanon

Aryan

Thanks a heap, Shannon and Cliff.

Cliff,

I am talking about the former approach. Can you eloborate the same???

Thanks
Aryan.

cliff1

I'm not sure what else I can add that Shanon did not cover in his document? Do you have any specific areas where you need further eloboration? The only step that is not covered in the documet is that you will need to deploy the imported MB assets out to production along with the rest of the LiveSite deployed files -- but the probably goes without saying since that applies to any assets stored in TeamSite that are referenced in the pages.

Aryan

I am sorry Cliff. I had not read the article completely. I thought you were talking about an altogether different approach.

It's clear now.

Thanks,
Aryan.

shanon

The only step that is not covered in the documet is that you will need to deploy the imported MB assets out to production along with the rest of the LiveSite deployed files -- but the probably goes without saying since that applies to any assets stored in TeamSite that are referenced in the pages.

Cliff, good point; you sure do need to deploy the images...

However, there's an easy way to get around this:

When you Save a page, LiveSite scans the page for static assets and sets their wa-relative paths into the following extended attribute:

TeamSite/LiveSite/DependentURIs

Try viewing the Properties of the

.page

file from ContentCenter and you'll see the attribute.

We're currently updating the LiveSite Submit workflow that comes out-of-box to attach these files to the job automatically so you just have to submit the page file and the static dependencies will be included in the job.

However, in the meantime, you just have to write a simple task that reads this attribute and attaches the files to the job... This is pretty straight-forward if you know TS workflow. If I have time I'll try and whip something up and attach it to this post, but no promises... Smiley Happy

Thanks,
Shanon