[opencms-dev] architecture - how to call cms taglibs from outside the workplace

[Jordi Martí]

HI everyone,

 

I don’t think this is the first time someone faces this question, but if’ve
been looking through the forums with no complete luck, although it has shed
us some light about what the problem is.

 

The short question: 

 

*         is it possible / safe to make calls to opencms taglibs and the
cmsshell object from outside the server that has the workplace? 

 

The long one:

 

We're trying to make a decision about the architecture of a project that
will consist of:

 

1.- the workplace (in the intranet)

2.- the web being maintained (in the DMZ)

 

Because of security, the workplace has to be installed apart of the web. Of
course, that implies the workplace being in a server (in the intranet) and
the web being in other (accesible to the outside, the DMZ).

 

Both servers will be reading the same information that is in the opencms
database (if possible, of course). 

 

As I have read from other mails, I see there's a problem accessing the
CMSSHELL object from outside where you have installed the workplace... We've
seen some solutions based on making cmsShell a public object, but as we have
tested, it results in a another instance of the opencms being up.

 

So, my question is: is it safe to have two "instances" of the opencms: one
in which the workplace will be installed (the normal installation) and the
other one reading the opencms.jar and accesing it through <cms:>  taglibs...


 

What if I need to access the CmsSHELL from the web? for example, for
uploading a document throught the web. What's the best or advised approach
to do this?

 

As an additional point, it is needed to be said that we'll integrate the web
part with struts / spring; but we have already done that succesfully (and we
see that that should be no problem).

 

Thanks for everyone reading this mail. 

 

-- jordi 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20070523/a568fbee/attachment.htm>