-> What is some typical implementation for an internet site with JBoss Portal? Cache, Hibernate, Clustering, AS? Others? Tomcat is really essential?
You need an Application Server. Tomcat allone isn't enough, because Portal needs the Application Server features.
-> On an internet site, what should we use as web server ? Apache connected to JB Portal? Or Tomcat? Or JBoss Portal in itself is secure enough?
You can't use Apache, because Apache is not Java Servlet Container. In the Internet, you will use an Application Server like JBoss AS, with a Servlet Container like Tomcat running.
-> Are there any reference docs that explain some of the typical sizing done on sites using JBoss Portal ? I need to start worrying about what kind of server (how many, etc) I'm supposed to buy.
This makes me ask, how many Users you are expecting. Im still rolling out JBoss Portal in the company i'm working in, so I can't provide some Numbers for you yet.
-> On an internet site, what should we use as web server? Apache connected to JB Portal? Or Tomcat? Or JBoss Portal in itself is secure enough?
-> Are there any reference docs that explain some of the typical sizing done on sites using JBoss Portal? I need to start worrying about what kind of server (how many, etc) I'm supposed to buy.
These questions are very application dependent and cannot really be answered abstractly... as there is no typical implementation: you cannot compare a "hobby" deployment of Portal for a personal website with a business critical deployment within a major company.
You might benefit from hiring one of our consultants who will work with you to help you figure out these issues based on your requirements and get you started faster. :)
Soon5, thanks for the inputs.
Regarding Apache, I was wondering if anyone was using it as the primary web server, with Tomcat/JB Portal behind it.
I've built a project before in which I used Tomcat to process the JSP pages, while Apache would stand in front and process the HTML pages and provide the security (offering more security because more widely used and tested). And there is a connector, to allow Apache to work seamlessly with Tomact (jk2 connector, if my memory serves me well).
Regarding the number of users, I'd say around 200 users, not much.
When you're rolling out your JBoss Portal, are you using different machines for some of the services (for example: Hibernate, AS, Clustering in 1; JBoss Portal, Tomact in 2)? I'm just trying to get a grasp on how I can distribute the services in machines.
So, if there are any more shareable insights, I'd appreciate. :)
Chris, I'll be sure to look into that, yes. But since I'm pressed on time and bureocracy limits my ability to hire services fast, that's why I was trying to get a first view on how a small site would distribute a JB Portal solution across a few machines.
I may well hire consultants for when i have a definite project and for sure I'll look into the consulting fees, I know the time saved will be well spent.
I know things are abstract, but for example I've been many times confronted with the fact that Mi***soft easily lays out some standard references that helps them 'selling' the product (and, no, I've been working with Java for years, never did any Sharpoint).
See an example from their 'solutionaccelerators'. Just examples, but give good food for thought.
Back to the point, actually I shouln't have asked for sizing, which seems definite, but I should have solicited something like a reference architecture for a small site (200 users, extranet like).