Does 'Site Publisher' and/or 'Targeting' REQUIRE a LiveSite 3.0 install?

TeamSite 6.7.1
LiveSite 3.0

Can I just install Site Publisher and/or Targeting WITHOUT installing LiveSite ? Or are these two dependant upon LiveSite being installed?

Thanks!

Find more posts tagged with

Comments

shanon

LiveSite 3.0 is now broken down into the following pieces:

SitePublisher - TeamSite Content Center add-on ( WYSIWYG editor )

Runtime - Runtime Web Application

Targeting - Optional add-on to SitePublisher AND Runtime.

Basically pre-3.0, SitePublisher and Runtime were collectively referred to as "LiveSite".

So, to answer your question, No to SitePublisher ( b/c it IS LiveSite ) and Yes to Targeting as it's an optional module.

Shanon

RichDiaz

Targeting - Optional add-on to SitePublisher AND Runtime.

Shanon

Can we JUST install Targeting on SitePublisher and NOT in the runtime? (as we have our own runtime targeting module)

nbwoven

I don;t have enough info on your implementation scenario but you should be up and running with just this configuration on the same box : ts6.7.1/ls3.0/targeting1.0/od611 .

There will be only one Targeting install involved and thats with the Sitepublisher.

RichDiaz

on the same box : ts6.7.1/ls3.0/targeting1.0/od611 .

Thanks!

shanon

Rich,

Whats the point of using Targeting on SitePublisher and not in runtime? The entire purpose of the targeting module is so that you can use rules to (a) segment users and (b) personalize content. This *all* occurs in the runtime only.

Maybe I'm missing something ... can you please explain what you think you'd gain from having targeting "only in TeamSite" and how you would still be able to leverage your "runtime targeting module".

Then hopefully I can give you a better explanation of how we'd fit into your environment.

Thanks,
Shanon

publications_pmcid.rptdesign

RichDiaz

Hi Shannon,

We can not use .pages. So we can't use the targeting runtime application that *renders* .pages, but we're going to use all the other tools Smiley Happy

I know we can read the LiveSite database directly to access the Targeting data. So, once accessed, we'll interpret the data and render the webpage. :cool:

tec_iwov

you won't have access to the rules engine which is the foundation of targeting.

with out that the content DB is basically useless

RichDiaz

Hmm.

tec_iwov, by 'rules engine', you mean runtime on the websever right? (not the Teamsite/Livesite authoring environment)

We just need to be able to see the authored Livesite 'rules' data (in the authoring environment or where ever the data is deployed) and interpret it.

Can't we read the LiveSite database where the 'rules' are stored and process the rules ourselves?

I ran this idea by Sunil when he was in our offices a few weeks ago and he said it would work... so that's what I reported to my boss. Ooops?

tec_iwov

the rules will execute in preview but if you are doing custom work to render there are no direct hooks to execute rules, Rules are deployed from the rules repository to the rules engine. This is all internal code not exposed as an API.

RichDiaz

there are no direct hooks to execute rules

We don't need to execute the rules, we just need to SEE the rules as they were authored. I would think this information is available...

...Rules are deployed from the rules repository to the rules engine. This is all internal code not exposed as an API.

By 'rules engine', you mean runtime on the websever right? (not the Teamsite/Livesite authoring environment)

So, if there is no runtime webserver rules engine present then no rules data is deployed?

If that is the case we would have to deploy the rules data ourselves so we could interpret it, correct?

Thanks!