date:20010118

RE: Clusters!!!!

2001-01-18 Thread Kevin Duffey


I have tested Orion in a two server cluster and it worked for the most part
nicely. My HttpSession beans were not all that properly done, so that may
have been the quirks I saw.

You do have to buy a license for each Orion server, 1 per SERVER not per CPU
per server, unlike most applications.


 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Mohit Palhan
 Sent: Wednesday, January 17, 2001 8:09 PM
 To: Orion-Interest
 Subject: Clusters
 Importance: High


 Hi! there,
 I want to know if

 1 anyone has Orion servers in cluster's?
 2 Has done load balancing ? (which algorithm are you using etc..)
 3 Is there object clustering in Orion? (as in the case of Weblogic .The
 key technology that
 underpins clustered objects in WebLogic Server is the replica-aware
 stub. When you compile an
 EJB that supports clustering (as defined in its deployment descriptor)
 ejbc passes the EJB's
 interfaces through the rmic compiler to generate replica-aware stubs for
 the bean. For RMI
 objects, you generate replica-aware stubs explicitly using command-line
 options to rmic).
 Note:- I have both session and entity beans in my system!(not sure
 but have heard it corrupts
 database any pointers are welcome)
 4 To have clusters do I have to buy multiple licenses ??

 Thanks
 mohit palhan
 Have a nice day :-)
 PS- Any pointers are welcome viz must do's for clustering
 etc..design etc..)


 --
 **
 ***

 The information contained in this message (including any attachments) is
 confidential and may be legally privileged.
 If you are not the intended recipient, please delete it from your system
 immediately - any disclosure, copying or distribution thereof or any
 action taken or omitted to be taken in reliance thereon is prohibited
 and may be unlawful.AITPL makes no warranty as to the accuracy or
 completeness of any information contained in this message and hereby
 excludes any liability of any kind for the information contained herein
 or for the transmission, reception, storage or use of such information
 in any way whatsoever.  Any opinions expressed in this message are those
 of the author and do not necessarily reflect the opinions of AITPL.
 **
 ***

IBM DB2 database schema

2001-01-18 Thread hartmut wilms


Hello everyone,

has anybody created a DB2 database-schema? I copied oracle.xml and changed
some mappings. But I'm no DB2-dude, so I would really appreciate a working
DB2 schema.

I got some errors when auto-creating tables. Something must be wrong...

AW: Servlet Mapping and Access

2001-01-18 Thread hartmut wilms

Title: SV: Servlet Mapping and Access

Hi
Magnus,

You're right.
I must have missed that line

name - The name of the
web-application inside the (enterprise-)application.

But:
Some pieces are missing in the online docs. Sometimes the information about
orion config files just stops or breaks respectively in the middle of a
sentence.

Hartmut

-Ursprüngliche Nachricht-Von: Magnus Rydin
[mailto:[EMAIL PROTECTED]]Gesendet: Donnerstag, 18. Januar
2001 08:30An: Orion-InterestBetreff: SV: Servlet Mapping
and Access
Did you check the doc at http://www.orionserver.com/docs/web-site.xml.html
(refered to in the documentation outline) ? It says the following on this: web-app
application="default" load-on-startup="false" max-inactivity-time="123"
name="defaultWebApp" root="/catalog" shared="true|false" /
Reference to a
application - The name of the (enterprise-)application the
web-app exists in. load-on-startup - Optional
attribute specifying whether or not to preload this web-app, if false then the
app will be loaded when needed (at the first request). The default is
false.
max-inactivity-time - Optional attribute specifying number of
minutes of inactivity before this web-app can be shut down, if not specified
no shutdown will occur.
name - The name of the web-application inside the
(enterprise-)application. root - The path on this site
to bind the application to, if for instance an app is installed at "/theapp"
it is reached by the URL: "http://www.thesiteserver.com/theapp/".
shared - Whether or not multiple bindings (different
sites/context roots) are to be shared. Sharing implies sharing of sessions,
servlet instances etc. The default is 'false'
Although a lot of documents are missing, the Orion
configuration files are pretty well covered. WR

-Ursprungligt meddelande- Från: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Skickat: den 17 januari 2001 22:53 Till: Orion-Interest Ämne: AW:
Servlet Mapping and AccessHi Jeff,
everything works fine nw. Thanks very much.
Nearly all of my configuration was perfectly all right in the beginning. The problem was -
and still is in some
areas - that there is very few documentation for orion config-files and their relationships.
The solution:
default-web-site:
web-app application="gamsytest" name="junitee-web"
root="/gamsytest" /
My EAR archive contains a
WAR called junitee-web.war. I didn't realize,
that the name attribute in the web-app tag
references the WAR filename. After reading your mail I realized what was wrong. Thanks,
again.
Hartmut
-Ursprüngliche Nachricht- Von: Jeff
Schnitzer [mailto:[EMAIL PROTECTED]]
Gesendet: Mittwoch, 17. Januar 2001 22:09
An: Orion-Interest Betreff:
RE: Servlet Mapping and AccessHave you successfully installed the
sample junitee test in the JUnitEE
tutorial? You
shouldn't need to modify the global application.xml. Here's how my system is set up, given
that my ear contains two wars,
"similarity-web" and "similarity-test-web" (which
contains my TestServlet and JUnit tests):
server.xml:
application name="similarity" path="../applications/similarity.ear" / default-web-site: web-app application="similarity" name="similarity-web"
root="/similarity" /
web-app application="similarity" name="similarity-test-web"
root="/test" /
similarity-web's web.xml: servlet
servlet-name
JUnitTestServlet /servlet-name

description JUnit test harness /description
servlet-class TestServlet
/servlet-class
/servlet

servlet-mapping

servlet-name JUnitTestServlet /servlet-name
url-pattern /TestServlet
/url-pattern
/servlet-mapping After this, I can access my test
servlet as either http://localhost/test/TestServlet or http://localhost/test/servlet/TestServlet. The first
because it's configured in the web.xml, the
second because all servlets in the
WEB-INF/classes directory of the war are exported as under the fairly
standard path "root/servlet" (it can be
configured in the
global-web-application.xml). I'm a little confused by what you posted, but assuming that
your normal web
application is in gamesytest-web.war and your tests are in junitee-web.war, both packaged in "junitee-orion.ear", you
should configure junitee-web in the
default-web-site and remove the reference to it
from the global application.xml. Then you should be able to use either URL: http://localhost/junitee/TestServlet http://localhost/junitee/servlet/TestServlet
Jeff -Original Message-
From: hartmut wilms [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 17, 2001 5:16 AM
To: Orion-Interest
Subject: AW: Servlet Mapping and Access
Hi
Santosh,

45 matches

Mail list logo