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; } } }

Install LSCS Authoring without installing Search first 7.3.1

Rob76

This is on Windows 2008 R2

Has anyone attempted to install LSCS Authoring on the TS server without first installing TS Search on the same server?

My understanding is LSCS Auth uses the IDOL instance that gets installed with Search. If search is not installed on the same server, no LSCS Auth.

If this is true, wasn't best practice prior to TS 7.3.1 to install Search on a separate server, especially in production?

Did this best practice change?

Find more posts tagged with

Comments

Migrateduser

You should be able to install LSCS Authoring and then update the necessary config files. The dependence between LSCS Authoring & TeamSite search is just the hostnames & port numbers in config files.

Rob76

You should be able to install LSCS Authoring and then update the necessary config files. The dependence between LSCS Authoring & TeamSite search is just the hostnames & port numbers in config files.

Doesn't the content have to live on the same server as the LSCS IDOL instance b/c the OD adapter calls IDOL to index that content locally?

To take a step back, if IDOL is required for LSCS, why is it using the IDOL Search instance? Why doesn't LSCS Auth have its own instance of IDOL? What if we don't want to use search but want LSCS Auth?

cecilb63

Search and LSCS use their own separate versions of IDOL

Topic_38908__Hide last columns in PDF via DEAPI__cwong.rptdesign

Adam Stoller

Search and LSCS use their own separate versions of IDOL

Hmm - according to a recent Support case - 7.3.1 uses only one instance of IDOL (AutonomyContent [on Windows]) for both Search and LSCS.

I haven't truly verified that - I was concentrating on Search and we had to go through some contortions to get the IDOL service running for it.

Rob76

Search and LSCS use their own separate versions of IDOL

This is not true, maybe you're thinking of LSCS Runtime, which does have it's own instance of IDOL.

For version 7.3.1 LSCS Auth uses the Search instance of IDOL. Which is insteresting b/c there is no dependence between the 2 shown in the installer. Probably b/c prior to 7.3.1 LSCS Auth did have its own IDOL instance and this change in architecture was missed.

So, if you install Search on the same server as LSCS Auth you're good to go, but in a production environment where you should install Search on its own server, LSCS Auth won't work.

I'm not exactly sure what configurations need to be updated such that LSCS Auth will work with a remote instance of IDOL, both from a preview and deployment perspective

Adam Stoller

...
So, if you install Search on the same server as LSCS Auth you're good to go, but in a production environment where you should install Search on its own server, LSCS Auth won't work.

I'm not exactly sure what configurations need to be updated such that LSCS Auth will work with a remote instance of IDOL, both from a preview and deployment perspective

As of 7.3.1 - Autonomy changed their architecture such that you now should install Search on the same server as TeamSite - not on a different server.

I kind of wonder if they did this to utilize IDOL for both Search and LSCS without, perhaps, taking into consideration the load imposed by doing indexing on the same server... however, that's apparently the recommendation now.

Rob76

As of 7.3.1 - Autonomy changed their architecture such that you now should install Search on the same server as TeamSite - not on a different server.

I kind of wonder if they did this to utilize IDOL for both Search and LSCS without, perhaps, taking into consideration the load imposed by doing indexing on the same server... however, that's apparently the recommendation now.

FYI - I understand what you're saying, BUT that's not my understanding from Autonomy - My understanding is that it still best practice to install Search on a separate box in prod, then make the required configurations such that LSCS Auth connects to that remote IDOL instance both from a preview and deployment perspective.

However, I've seen no documentation regarding how to do this.

We are considering installing Search twice, once on TS server only for LSCS Auth, then again on another server for Search

kkumar

As of 7.3.1 - Autonomy changed their architecture such that you now should install Search on the same server as TeamSite - not on a different server.

In our client machines for 7.3.1 on windows 2008 OS IDOL search and teamsite is in different-2 machines.

Will this create any problem in future as TS and IDOL is not in same machine?

Rob76

In our client machines for 7.3.1 on windows 2008 OS IDOL search and teamsite is in different-2 machines.

Will this create any problem in future as TS and IDOL is not in same machine?

What are your requirements for LiveSite Content Services (LSCS)?

This discussion is in scope of LSCS Authoring and its availablity b/c the architecture changed in 7.3.1. LSCS Auth 7.3.1 uses the IDOL instance that is available with TS Search. In 7.2.1 LSCS Auth had its own IDOL instance.

Adam Stoller

In our client machines for 7.3.1 on windows 2008 OS IDOL search and teamsite is in different-2 machines.

Will this create any problem in future as TS and IDOL is not in same machine?

There are a number of different references in the manuals - though, to be frank I don't see anything that explicitly recommends one way (one server) or another (two servers).

If you want to use two servers, you should be able to specify the host information in the SEARCH/etc/search.properties with regard to where TeamSite and IDOL are - and I believe you can configure where the Search server is in TeamSite's IWHOME/cssdk/cssdk.cfg - however, I think the IDOL installation (at least on Windows) is part of the Search - so I'm not entirely sure where you tell LSCS what server to look at for IDOL.

Migrateduser

When LSCS Authoring is installed for preview, there is a configuration file in the LiveSite Content Services installation directory called lscs-conf.properties. In here you can specify the location of IDOL. If TeamSite search is installed on a different host, you can update this config with the appropriate information.

From 7.3.1 onwards LSCS Authoring does leverage the IDOL shipped with TeamSite Search. The recommendation of having Search and TeamSite installed on the same box is to simplify the installation process. This is not a hard recommendation and Search can still be installed in a separate box.

Shashi

Rob76

When LSCS Authoring is installed for preview, there is a configuration file in the LiveSite Content Services installation directory called lscs-conf.properties. In here you can specify the location of IDOL. If TeamSite search is installed on a different host, you can update this config with the appropriate information.

From 7.3.1 onwards LSCS Authoring does leverage the IDOL shipped with TeamSite Search. The recommendation of having Search and TeamSite installed on the same box is to simplify the installation process. This is not a hard recommendation and Search can still be installed in a separate box.

Shashi

Thanks Shashi

After the updates are made to lscs-conf.properties, can you comment on what is required from a deployment configuration perspective when Search/IDOL is on another server?

We need to deploy that content to the remote Search/IDOL Server to have IDOL index it?

In 7.3.1 and beyond, what's the difference between LSCS Auth and LSCS Runtime from a technical perspective?