Understanding the installation

Hi,

I have a series of questions related to ELS installation. Also, I have questions on the overall fundamentals Here are a series of questions in no particular order:

1) When deploying ELS on a server where LES and LEA are already installed, is a separate tomcat instance required, or can ELS use the tomcat server already installed for LEA? Given that BPM requires 2 tomcats and 1 JBoss server, it's not unreasonable to assume that ELS might require the installation of more than 1 tomcat.

2) What exactly is (if any) the interaction between ELS web services and the EWS that come bundled with LES 971? For instance, if you make a SOAP request to the ELS server (by server, I mean the instance of tomcat on which ELS foundation is installed), does it talk to LES using EWS (i.e. either a forwarding of the SOAP request or a repackaging of it) or with a direct call on port 2099? The obvious implication of the latter is that one then would need ELS and LES to be on the same server or the traffic on port 2099 would need to be encrypted.

3) Does the installation process for Archive service merely install a new war for the tomcat server? Or does it install significantly more?

4) Related to 3, does the archive service require a separate database install from the ECR tablespace/db instance that would already be running in LEA? This was not 100% clear from the installation guide.

In the meantime, I will be poking around on the know zone image of ELS, but given that I may well be called to install all of this, I need to know these things ahead of time.

-Hugh

Find more posts tagged with

Comments

Anthony_Dodds

Hello Hugh,

1) which version do you refer to? ELS 10.0.1 is on the way to being released, it's expected to be finished till end of this week.

https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=14693367&objAction=browse&sort=name&viewType=1

What do you want to install on your machine: BPM, LEA, LES, ELS, ....

LEA version 9.7.1 does not bring a Tomcat any longer.

2) There is no interaction between the ELS Web Services API, and the Enterprise Web Services from LES. They use disjunct data models. I have to check what kind of communication is used between ELS Web Services and LES.

3) The Archive and Storage Services require RCS to be installed.

4) What do you mean by "Archive Service"?

Regards,

Hella

Anthony_Dodds

Hello Hugh, Hella,

Quoted hella on 07/15/2008 03:56 AM:

ELS Web Services as well as Livelink Enterprise Server Web Services (LES Web Services) are exposed with the jax-ws web services framework coming with Runtime & Core Services hosted by Tomcat (or Netweaver).

Internally LES introduced a generic communication mechanism (based on LAPI and thus using port 2099) that allows to make OScript "services" available in the java world as java interface.

Both ELS Web Services as well as Livelink Enterprise Server Web Services rely on this mechanism to expose OScript functionality to java. Actually this mechanism was originally mainly introduced for the Livelink Enterprise Server Web Services.

Therefore ELS Web Services and LES Web Services are somehow related (at lower levels) and ELS Web Services uses the infrastructure introduced for LES Web Services.

However as Hella mentioned at the Web Services level LES Web Services are independent from ELS Web Services. LES Web Services are more fine-grained and low-level. LES Web Services work more or less on the LES node level, whereas ELS Web Services are coarse-grained and deal with higher-level objects.

Regards,

Xaver

Anthony_Dodds

Hi,just an additional remark on2) "[...] or with a direct call on port 2099? The obvious implication of the latter is that one then would need ELS and LES to be on the same server or the traffic on port 2099 would need to be encrypted." This is to a greater or lesser extent correct. Unfortunately the communication with the `direct? LAPI port 2099 (or whatever it actually is) cannot be encrypted. (This is a limitation of LAPI/LES.)Of course there are other possibilities to secure that communication channel: One would be to use LAPI's "HTTP tunnel" mode over SSL (aka HTTPS). The code is in place but I'm not aware how you can configure the system to make use of it.Another possibility is e.g. to setup a ssh tunnel.