Some questions related to SAP XI

Question

Hello!
I would like to know the answers for the following questions regarding SAP XI-context (if it possible with Yes/No and a short comment/explanation)
<b>CAPACITY PLANNING GUIDELINES</b>
a) Guidelines to size the server(s)?
b) Guidelines for sizing the over all environment for High-Availability
<b>ARCHIVING CAPABILITIES</b>
a) Approach to archiving of obsolete data
<b>PLATFORM SUPPORT</b>
a) Software supported on HP-UX 11.i V2 (r6) on Itanium.
b) software supported on Windows 2003 sp1 (x64) on AMD Opteron 
c) software support aligned with release roadmaps for future versions of HP-UX and/or Windows Server
d) Software supported on OS clustered servers  (If mutliple products, please indicate if all are support or list areas where clustering may not be recommended and why)
<b>RELATIONAL DATABASE </b>
a) Does your system run native to the Oracle 10g RDBMS (RAC) and database tools?  If not, please explain the databases and tools supported.
b) database monitoring tools be used to manage impending maintenance needs and potential problems and performance impacts (i.e., tool will monitor and detect prior to real problem occurring)
c) standard pre-defined SQL queries and related calculations provided for use with industry standard reporting tools
d) database accept binary-large-objects (BLOBs) and  be referenced via the relational engine.
Thank you in advance!
Regards!
A.Henke

Answer 1

two questions related to this:
1. Why Java is designed to only permit single
inheritence, any stories behind the scene? I think
some major reasons why "prefer interfaces toabstract
classes" is accepted is rooted in this limitation.Yes, one of the reasons interfaces are better is that
you can only extend one class, but implement many
interfaces. Say you have a concrete class that should
"implement" two different types. If those types were
defined as abstract classes, you could only use one
type. You could implement both types if they were
interfaces though. So why java is designed to have this limitation? There may be some arguments before this is settled down. I always like to hear this kind of stories:)
2. Base on the fact that once an interface is outof
box and widely implemented, it is almostimpossible
to change it. So how you guys design yourinterfaces?
Could you share some? In my idea, I would designmy
interfaces as compact as possible.You could extend the interface and start using that
if you didn't want to break existing code. You
couldn't use that implementation as an Interface1
though, since the new methods only exist in
Interface2, so that's not an optimal solution.So we may always need to add a new interface when we just want to add a new method.