Message Queue hardware requirements

I'm intrested in upgrading MessageQ 4.0a to MessageQ 5 in a Win2K server, but first I want to know what are the hardware requirements for this software and know if the server performance will be affected?

What do you mean by "process 150 million rows"? There is a pretty big difference between, say, building some materialized views on 150 million row tables and a process that has to do extensive processing and validation on 150 million rows.
What sort of time window do you have at month end? Does this need to happen in an hour or two, or is it acceptable if it takes all day?
What sort of hardware does your organization currently use? Do your admins have familiarity with Windows, Linux, Solaris, HP-UX, AIX, etc.?
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

Similar Messages

Oracle tuxedo and Oracle tuxedo message queue on top of a virtual machine.

Hi buddies.
how is it going?
A quick question.
So we are going to go live using Oracle Tuxedo 12.1.1.0 with Distinguished Bulletin Board Liaison and Oracle Tuxedo Message Queue 12.1.1.0 on top of a Virtual Machine (VMWARE) running Oracle Linux 6.2. However we want to know if there are any recommendations or mishaps in which we may face ahead by running Oracle Tuxedo on a virtual machine?
I mean, I am wondering if I have to worry about kernel parameters, virtual machine parameters or any other thing from which could mess up everything.
Another question.
Does oracle also provide virtual machines certification where Oracle tuxedo would run on top of ?
Todd Little-Oracle
Maurice G

Hi Bruno,
I'm not sure what you mean with Distinguished Bulletin Board Liaison. I'm guessing you mean a clustered or MP configuration? And is it truly a clustered configuration or just a single machine MP configuration?
Regarding configuration, are you using Tuxedo services as well or just Tuxedo Message Queue? The biggest issue related to OS configuration is around IPC resources. If you do a tmloadcf -c on your UBBCONFIG file, it will help you determine the minimum IPC resources required. In general I suggest configuring significantly more resources than the minimum to allow for future changes and for some of the parameters for heavier loads. In particular IPC message queue parameters are heavily dependent upon load. So make sure the maximum message size and queue size are large enough for your anticipated workload. You can monitor them under load using the ipcs command.
We don't certify virtual machine environment but support them as long as the VM vendor assures compatibility, which obviously VMware and Oracle VM both do.
Regards,
Todd Little
Oracle Tuxedo Chief Architect

Get/set message Queue ID in PI 7.1 Adapter module

Hello,
I have a special requirment to get and set message Queue ID in PI 7.1 adapter module.
I tried to use the method setConversationID for the Message Class, but this doest seem to available any more.
Any pointers to which class and method can be used.
Thanks in advance
Regards,
Abhishek

Hi, try [setSequenceId|http://help.sap.com/javadocs/pi/pi711sp03/com/sap/engine/interfaces/messaging/api/Message.html#setSequenceId(java.lang.String)]. Maybe you have to use setDeliverySemantics before in order to set EOIO.
regards, Martin

Message Queue Blocking / MSGMNI Setting

Hi All,
Firstly, many thanks to all that can assists. I am currently getting Message Queue
Blocking messages in my ULOG files in my Tuxedo Application. (Tux ver 7.1 in Unix).
I am not sure what is causing this, but started to look into the Tux Config (UBB.MP)
and System message queue setting. Detailed as follows:
1)
Listed below is the system message queue setting:
set msgsys:msginfo_msgmni=2000
set msgsys:msginfo_msgmax=128000
set msgsys:msginfo_msgmnb=100000
set msgsys:msginfo_msgssz=256
set msgsys:msginfo_msgseg=25088
set msgsys:msginfo_msgtql=1550
set msgsys:msginfo_msgmap=1000
According to the BEA site, the MSGMNI is determined by this formula:
MSGMNI = MAXACCESSERS + 7 + (no. of servers with REPLYQ) + (no. MSSQ sets) - (no.
of servers with MSSQ sets)
The following is my current Tux. Config (UBB.MP) is set as :
- MAXACCESSERS = 2300
- Each servers (4 types in total) has its own REPLYQ and RQADDR.
- The same type of servers are set the same across 4 application servers.
Hence, my MSGMNI should be a minimum 2339 (ie. MSGMNI = 2300 + 16 + 16 - 0 = 2339).
But my current MSGMNI is 2000.
Would this contribute to my Message Queue Blocking?
Is my understanding correct and is this something I should change to avoid Message
Queue Blocking? Any helps and advice is much appreciated.

Malcolm,
Your information and explanations behind these error messages are very useful.
It allow me to further understand Tuxedo internal processing and at the same time
give me a chance to start analysing these fields.
I am reluctant to ask further questions at the mean time. I will use your suggestions
as a starting point.
I will certainly keep you posted of the outcome when I have made the changes in
my UBB config and machine parameters.
Many thanks with your help/explanations Malcolm. It helps alot!
Cheers.
David.
"Malcolm Freeman" <[email protected]> wrote:
>
Hi David,
The MSGTQL reference you give (Solution S-00488) refers to the BEA MessageQ
product
and is not relevant to Tuxedo.
The error messages indicate that the queue buildup is probably due to
a restartable
server failing. What happens is this:
When a restartable server fails its IPC queue remains in place and continues
to
receive messages (which will be processed when the server restarts).
Depending
on the time taken to restart, the queue could become full and unable
to receive
any more messages, and this is probably why you got the message CMDTUX_CAT:1380
indicating that the BRIDGE process was unable to put a message on the
server's
queue.
A server is only restarted when the BBL does a SANITYSCAN check. If,
for example,
your SANITYSCAN interval is 300 seconds and your server fails immediately
after
the previous scan, then there will be a delay of almost 5 minutes before
the failure
is detected and the server restarted - plenty of time for the queue to
fill up.
There are a few things you could do:
The key thing would be to find out why the server is failing, and fix
the problem.
If this is not possible immediately, consider some of the other ideas
below.
Have several servers form an MSSQ to service this queue; then if one
fails the
others will continue processing the messages while the failed server
restarts
(this assumes, of course, that your application does not require the
messages
to be processed in strict order through the server).
Reduce the SANITYSCAN interval (but don't make it too small). This would
reduce
the average time taken to restart the server.
Increase the size of the IPC queue (MSGMNB) so that it can hold more
messages.
I'm not sure why you got a LIBTUX_CAT:1485 message, but this could be
due to a
BRIDGE failure as a result of the congestion.
The NETLOAD parameter would reduce the number of messages going to the
remote
machine, but only if the local machine offers the same service. If the
remote
machine is the only source of the service then NETLOAD will have no effect.
I
recommend you do a search of this newsgroup for postings on "load balancing"
there's some good stuff which will explain how load balancing works.
Depending how things go, it might not be a bad idea to open a case with
BEA Support
and ask for guidance (remember to submit your ubbconfig (or preferably
do a tmunloadcf)
together with the complete ULOGs from both the master and the slave machine).
Hope this helps some.
Regards,
Malcolm.
"Dave" <[email protected]> wrote:
Hi Malcolm,
Thank you for your reply. Interesting point you have made about theMSGTQL
value.
Based on your suggestion I went hunting around the BEA site and found
the following
snipplet:
"- The MSGTQL parameter must be set to a value greater than or
equal to the MSGMNI setting."
(http://support.bea.com/application?namespace=askbea&origin=ask_bea_answer.jsp&event=link.view_answer_page_solution&answerpage=solution&page=msq/S-00488.htm)
If the above point is valid, then my MSGTQL is definitely way too low.
IF this
be the case, would you know of a method to work out what my MSGTQL bytes
value
should be?
Additionally, I have looked at other parameters which I could tune,and
would
adding a NETLOAD parameter in the *MACHINES section will reduce remote
servers
call? Which potentially, maybe reduce message queue blocking?
FYI:
The error messages I am seeing in my ULOG file are:
"LIBTUX_CAT: 1477 : ERROR .SysServerDied
LIBTUX_CAT: 1476 : ERROR: .SysServerRestarting"
Which then leads to message queue blocking
"CMDTUX_CAT: 1380 : ERROR: Message queue blocking prevented delivery,
Qaddr=..."
and potentially "LIBTUX_CAT: 1485 .SysNetworkDropped."
Many Thanks. Hope to hear from you (Malcolm) or other parties out there
that can
assists.
Thanks.
David

How to determine the hardware requirements based on the Services' payload

hello,Guys
i am wondering if i can calculate the hardware requirements based on the services' payload ?
what factors should i consider when to determine the hardware requirements?
is there any documents related to my questions? ;)
Thanks
Regards
Wen

Payload size is not the only factor while determining size of the system (h/w). You need to consider number of services, nature of services (sync/async), payload size, frequency of messages (load), peak load value, security constraints, performance requirements etc..
You may contact your local Oracle Sales Representative/ Oracle Support to get help in determining size of the system. They will provide you a sizing questionarre and on the basis of that they may suggest sizing as well (Oracle has an internal tool for proposing sizing)
Regards,
Anuj

Revised product name: "Oracle GlassFish Enterprise Message Queue"

Hello,
the release notes for OpenMQ 4.5 build 16 include a note about a revised product name, "Oracle GlassFish Enterprise Message Queue". Is this planned to be the future product name for the commercial product (the product formerly known as Java System Message Queue), or is this meant to be the name for both versions?
Many thanks in advance,
Michael Justin
Edited by: 801285 on 10.10.2010 01:49

Hi all,
I have finally solved the problem, it seems somehow on my windows home premium I can't run the install script (on H:\ ) from the command line. I manually ran the batch script by double clicking on it, it ran fine and I was finally able to install ORE (server + supported + client) on my laptop. Now the connection -- followed through the manual, created user and granted all the roles. Now that I want to test the connection, I open R console and below are the input and output error message though it seems I can connect to the database:
R>
R> library(ORE)
Loading required package: OREbase
Attaching package: ‘OREbase’
The following object(s) are masked from ‘package:base’:
cbind, data.frame, eval, interaction, order, paste, pmax, pmin, rbind, table
Loading required package: OREstats
Loading required package: MASS
Loading required package: OREgraphics
Loading required package: OREeda
Loading required package: OREdm
Loading required package: lattice
Loading required package: OREpredict
Loading required package: ORExml
R>
R>
R>
R> ore.connect(user = 'scott', sid = 'sinha', host = 'win7', password = 'tiger', port = 1521, all = T)
Error in .oci.GetQuery(conn, statement, data = data, prefetch = prefetch, :
ORA-06520: PL/SQL: Error loading external library
ORA-06522: Unable to load DLL
ORA-06512: at "RQSYS.RQEVALIMPL", line 17
ORA-06512: at "RQSYS.RQEVALIMPL", line 14
ORA-06512: at line 4
R>
R>
R> ore.is.connected()
[1] TRUE
R> I get the exact same error when I try to use even the ORE user "rquser". Any suggestion how to resolve this error?
Thanks,
Sourabh

Hardware requirement for Oracle Universal Content Management

Hi Experts,
What are the Hardware requirements for Oracle Universal Content Management ?
Regards
Nasir

does this help?
Oracle WebLogic Server 11g (10.3.3) System Requirements
Oracle WebLogic Server supports a number of platforms including:
– Linux
– Sun Solaris
– HP-UX
– Windows 2000, 2003 Server, XP
• Processor:
– At least one 1 GHz CPU is recommended.
– Intel and UNIX processors are supported.
• Hard disk drive:
– A full installation requires approximately 2 GB of disk space.
– The Linux value for file descriptors must be 4096 or greater.
– Samples are optional (download from OTN).
• Memory:
– A minimum of 2 GB RAM is recommended for WebLogic
Server.
– Consider the number of simultaneous users and sessions.
– Consider in-memory programs, such as Coherence.
System Requirements
The following are some of the basic system requirements for Oracle WebLogic Server 10.3.3:
• The Oracle WebLogic Server installer requires a Java Runtime Environment (JRE) to run.
Oracle WebLogic Server is certified with JDK6.0. As part of the installation, it gives the option
to install the JRockit JDK 6.0 version. As part of postinstallation, prefix the bin directory of
the JDK to the PATH environment variable.
• The Oracle WebLogic Server installer requires a temporary location in which to unpack the
files. Typically, the installer requires approximately 2.5 times the amount of temporary space
that is required by the installed files.
Note: In this release of WebLogic Server, users can choose which components of WebLogic Server
they use. Specifically, this release allows users to choose whether the Enterprise JavaBeans (EJB),
Java Message Service (JMS), and J2CA services are started when WebLogic Server is started. The
benefit of excluding some services is reduced memory footprint and reduced startup time.

ISE Hardware Requirements

Cisco's docs are not providing the information in regards to ISE hardware requirements. I am looking at 3 different documents and see 3 different requirements.
Does anyone have the tried an true numbers for the ISE deployment? Specifically for the PSN?
Also, i there a hardware restrictions on the servers that can be used in the event the customer decides to go with their own hardware rather than using VM?
thanks for any assistance anyone can offer.
Mike
Received answer from Cisco...
Posting in case anyone else needs this info
Your Question:
If I am using a distributed deployment, for example, running 1 node as admin and monitoring, another node for PSN, would I need 250gb disk space for each node? Or would I use a shared 250gb disk space on a storage server?
Answer:
As you informed that you are " running 1 node as admin and monitoring, another node for PSN, would I need 250gb disk space for each node ", so YES each node will have individual 250Gb of space.
Now the node running as admin and monitoring would have to share the 250Gb available on the ISE on which they would be implemented.
Your Question:
Additionally, say I were to scale and create 2 admin nodes, and 4 PSNs, how would the disk space work in that case?
Answer:
As the 2 Admin nodes would be on individual ISE hardware appliance, so individually they would have 250Gb of space and if the 4 PSN are also the same ISE hardware, then each PSN would have it's own 250Gb space.
Your Question:
If however, the admin node and PSN were on the same chassis, different VM (if supported) how would the disk space work then?
Answer:
If the VM used for the above scenario is only one and is configured according/equivalent to ISE hardware appliance, then the space mentioned (250Gb as example) would be shared between the two persona's.
Message was edited by: Michael Mistretta

Hello,
The Below link's might help you out:-
http://www.cisco.com/en/US/docs/security/ise/1.0.4/install_guide/ise104_vmware.html
and
http://www.cisco.com/en/US/prod/collateral/vpndevc/ps5712/ps11637/ps11195/data_sheet_c78-656174.html

Hardware requirements for SAP ERP 2005 using ECC 6.0

Hello everyone,
i am already new and need information about the min. hardware requirements for a SAP ERP 2k5 System using ECC 6.0 with IDES 7.10.
I read the Master Guides about ERP, but i am not even more clever than before.
The OS is MS Windows 2k3 Server EE.
The last information i had from another one to this configuration is:
1 dual-core cpu (? Ghz)
4-6 GB RAM
300 GB HDD
Does it fit? Can anyone help me out?
Thanks in advance.
Message was edited by:
        Marcel Jahn
Message was edited by:
        Marcel Jahn

Hi,
IDES 7.10?!?
If it's an IDES system you want to set up, HDD space may be the bottleneck. It's sufficient for installation, but you may run out of disk space since note <a href="https://service.sap.com/sap/support/notes/1013391">1013391</a> states
Hardware Requirement
                 MS-SQL ORACLE   MaxDB   DB2 Win/Unix AS/400
DB size (GB):    160     220      220          160       280
Since IDES is for education and training purposes only the rest should be sufficient.
I'm running an ERP 6.0 IDES system (32 bit) on a single core, 3.2 GHz, 4 GB RAM, 250 GB System and 500 GB SAP/DB HDD with pretty good response time.
Peter
Points always appreciated

LIBTUX_CAT:681Failure ro create message queue

Hi,
We get this error when we start more than 3 Appserver.
(Solaris 8 + Oracle)
Any information would be appreciated. Thanks.
It's my /etc/system file...
set maxusers=80
set shmsys:shminfo_shmmax=8589934590
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=15
set semsys:seminfo_semume=500
set semsys:seminfo_semmns=500
set semsys:seminfo_semmnu=500
set semsys:seminfo_semmsl=70
set semsys:seminfo_semmap=500
set semsys:seminfo_semmni=32
set semsys:seminfo_semopm=100
set semsys:seminfo_semvmx=32767
set semsys:seminfo_msgmap=780
set semsys:seminfo_msgmax=4096
set semsys:seminfo_msgmnb=8192
set semsys:seminfo_msgmni=500
set semsys:seminfo_msgssz=8
set semsys:seminfo_msgtql=40
set semsys:seminfo_msgseg=1024

And just to add to $0.02,
Oracle doesn't use message queues, only shared memory and semaphores. Here is the
/etc/system I use on my Solaris 7 system for development work:
* IPC Tunables - Shared memory
* max shared memory segment size (SHMMAX)
set shmsys:shminfo_shmmax=4294967295
* min shared memory segment size (SHMMIN)
set shmsys:shminfo_shmmin=1
* max attached shm segments per process (SHMSEG)
set shmsys:shminfo_shmseg=100
* shared memory identifiers (SHMMNI)
set shmsys:shminfo_shmmni=100
* IPC Tunables - Semaphores
* semaphores in system (SEMMNS)
set semsys:seminfo_semmns=4096
* semaphore identifiers (SEMMNI)
set semsys:seminfo_semmni=128
* entries in semaphore map (SEMMAP)
set semsys:seminfo_semmap=4096
* undo structures in system (SEMMNU)
set semsys:seminfo_semmnu=4096
* max semaphores per id (SEMMSL)
set semsys:seminfo_semmsl=2048
* max operations per semop call (SEMOPM)
set semsys:seminfo_semopm=256
* max undo entries per process (SEMUME)
set semsys:seminfo_semume=1024
* semaphore maximum value (SEMVMX)
set semsys:seminfo_semvmx=32767
* IPC Tunables - Messages - For Tuxedo
* entries in msg map (MSGMAP)
* set msgsys:msginfo_msgmap=2048
* max message size (MSGMAX)
* set msgsys:msginfo_msgmax=262144
* max bytes on queue (MSGMNB)
* set msgsys:msginfo_msgmnb=262144
* message queue identifiers (MSGMNI)
* set msgsys:msginfo_msgmni=1024
* message segment size (MSGSSZ)
* set msgsys:msginfo_msgssz=1024
* system message headers (MSGTQL)
* set msgsys:msginfo_msgtql=2048
* message segments (MSGSEG)
* set msgsys:msginfo_msgseg=2048
* Workstation Settings
* IPC Tunables - Messages - For Tuxedo
* entries in msg map (MSGMAP)
set msgsys:msginfo_msgmap=2048
* max message size (MSGMAX)
set msgsys:msginfo_msgmax=65535
* max bytes on queue (MSGMNB)
set msgsys:msginfo_msgmnb=512000
* message queue identifiers (MSGMNI)
set msgsys:msginfo_msgmni=1024
* message segment size (MSGSSZ)
set msgsys:msginfo_msgssz=1024
* system message headers (MSGTQL)
set msgsys:msginfo_msgtql=2048
* message segments (MSGSEG)
set msgsys:msginfo_msgseg=2048
Mervin Calverley wrote:
Fabrice:
The error implies that msgmni is set too low. msgmni is the total number of message
queues allowed in the system. Getting an error here implies that oracle or some
other process is consuming them.
For Tuxedo Classes we use the listed values as minimum for the kernel parameters
to perform the labs. In these classes the machine is only running Tuxedo. This
means the values are probably lower than those required by a production system or
one hosting Oracle as well as Tuxedo.
Message Queue Parameters:
MSGMAP 800
MSGMAX 32769
MSGMNB 42000
MSGMNI 400
MSGSSZ 64
MSGTQL 400
MSGSEG 2048
Semaphore Parameters:
SEMMAP 800
SEMMNI 800
SEMMNS 800
SEMMNU 800
SEMMSL 800
SEMOPM 64
SEMUME 64
SEMVMX 32769
SEMAEM 16384
Shared Memory Parameters:
SHMMAX 2097152
SHMMIN 1
SHMMNI 100
SHMSEG 64
SHMALL 2048
**Note: Some UNIX kernels do not support all of the above parameters or have additional
parameters not listed.
Hope this helps!
mervin
"Fabrice Poulard" <[email protected]> wrote:
Hi,
We get this error when we start more than 3 Appserver.
(Solaris 8 + Oracle)
Any information would be appreciated. Thanks.
It's my /etc/system file...
set maxusers=80
set shmsys:shminfo_shmmax=8589934590
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=15
set semsys:seminfo_semume=500
set semsys:seminfo_semmns=500
set semsys:seminfo_semmnu=500
set semsys:seminfo_semmsl=70
set semsys:seminfo_semmap=500
set semsys:seminfo_semmni=32
set semsys:seminfo_semopm=100
set semsys:seminfo_semvmx=32767
set semsys:seminfo_msgmap=780
set semsys:seminfo_msgmax=4096
set semsys:seminfo_msgmnb=8192
set semsys:seminfo_msgmni=500
set semsys:seminfo_msgssz=8
set semsys:seminfo_msgtql=40
set semsys:seminfo_msgseg=1024
Brian Douglass
Transaction Processing Solutions, Inc.
8555 W. Sahara
Suite 112
Las Vegas, NV 89117
Voice: 702-254-5485
Fax: 702-254-9449
e-mail: [email protected]

Message Queue vs RFC Queue

Can anyone tell me what's the difference between Message Que and RFC Queue?
Thanks
Mark

Dear,
Connectionless programming involves using a queue to hold user input to another application or server. Here, we may not have a permanent connection to the application or server. Instead you log your input in a queue and the other application or server then takes it from the queue, processes it, and sometimes it may put the result back to the same queue or to a different queue. Unlike UDP, here there is no chance of message or data loss once you log it into queues.
The Connection oriented is different from the aforementioned and talks about any standard database system (DBMS, RDBMS, OODBMS and ORDBMS) available these days. Presumably, I don't think that there should be an explanation required for connection oriented programming. Unlike TCP/IP, there is no chance of data packet loss and it will bring the data packet to the required destination.
In short, message queue is purely connectionless and gives an assurance that it won't lose any data which is in the queue.
Message queue will be used :
a.Storing insignificant information in the message queue while your database server is busy with other real time processing.
b.Process user input which is given by the user after getting supporting information from other source or applications that are not active or ready at this stage.
c.Because of database server outage, you might require keeping user input in the message queue and processing it as and when the database comes online.
d.Exchanging data with a mainframe system like SAP. Personally, the real time communication with SAP is often a problem. In such cases, the SAP system uses message queue for storing and forwarding information where real time communication is not possible at that time.
RFC Queue:
Communication between applications in different systems in the SAP environment includes connections between SAP systems as well as between SAP systems and non-SAP systems. Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. RFC calls a function to be executed in a remote system.
In short, essentially application infrastructure and business requirements determine whether you should use a message queue or not. Personally, I would suggest that itu2019s a good idea to work with a tool for a while so that you can get to the solution in which you should use it.
http://help.sap.com/SAPhelp_nw04/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/content.htm
Regards,
Syed Hussain.

Message Queue Enterprise Edition

I have Sun One Directory server Service pack 4 installed and configured in a multi-master configuration. I want to install identity sync to sync up with a 2003 server to support windows clients with single point of maintenance for accounts and passwords. The release notes for the identity sync tool 1 2004Q3 SP1 say I need Message Queue Enterprise Edition. I have a bunch of message queue packages already installed and need to know if what I have is enough, or what I need to download (and where) to make this thing work.
I have : SUNWiqdoc, SUNWiqfs, SUNiqjx, SUNWiqr, SUNWiqu, SUNWiquc, SUNWiqum
Thanks
...MJW

Customers who purchased the iPlanet Message Queue for Java version 2.0
Enterprise Edition, or the iPlanet Java Message Queue version 1.1 Business Edition,
who also have a current maintenance contract for this product, are entitled to a free
upgrade. Sun customers should use their normal support channels to request the
upgrade. All corporate customers with Sun Software Support contracts should be
automatically notified of the upgrade via the ProductTracker by SubscribeNet
program. If you haven't, please contact Sun Customer Service online or by phone at
888-786-8111. Parties interested in upgrading will be required to provide
proof-of-purchase. Customers of previous versions of the free Developer Editions, or
customers without a current maintenance contract on this product, can not upgrade
for free, they must buy the Sun ONE Message Queue 3.0 Enterprise Edition product,
or they can download the Sun ONE Message Queue 3.0 Platform Edition product for
free from: http://wwws.sun.com/software/download/download/5275.html

Edge server role hardware requirements

I'm new to Exchange Server 2007 and am in the early stages of planning the installation and deployment. This server will be used in a company with approximately 25 users.
My plan is to use a one machine for Client Access, Hub transport, Mailbox, and Unified messaging.
What are the hardware requirements for the machine that will be running the Edge Server role? Are they different than the machine that will be running the other four roles?
Would 25 CALS be required for the edge server and 25 for the server running the other four roles?
Thanks

You will find all Hardware requirements here (all roles)
http://msexchangeteam.com/archive/2007/01/16/432222.aspx
All clients only need one CAL for all Exchange server
I don't even think that you need a CAL for the EDGE server
You do need an Exchange Server License for every server you have
Deli

Sun ONE Message Queue 3.0.1 is now available

Sun One Message Queue 3.0.1 is now available. Sun ONE Message Queue 3.0.1
is an implementation of the Java Message Service version 1.1 specification.
It comes in two editions; a free Platform Edition as well as an Enterprise
Edition for full-scale, enterprise deployments.
Noteworthy changes in 3.0.1 (compared to 3.0):
* Substantial performance boost
MQ 3.0.1 provides message delivery throughput up to double that
attained with MQ 3.0, a performance boost that is especially important
under heavy load conditions.
* Certified for use with the Sun ONE Application Server 7.0
MQ 3.0.1 is certified for Sun ONE Application Server 7.0, and is used as
its native JMS provider. MQ has been integrated with the Application
Server, providing JMS messaging support in an Application Server
environment. You can configure the system for an internal MQ message
server managed with Application Server administration tools, or an
external MQ message server requiring MQ administration tools.
* Support for Linux Red Hat 7.2 (JDK 1.4.1)
MQ 3.0.1 is now certified for JDK 1.4.1 on Linux Red Hat 7.2 (and still
supported on Linux Red Hat 7.1).
* Bundled on Solaris
MQ 3.0.1 Platform Edition will be bundled with Solaris 9 Update 2 when
it ships in early 2003.
For more specific details about 3.0.1 please see the product Release Notes
at: http://docs.sun.com/source/816-6454-10/index.html
The two editions of Sun ONE Message Queue 3.0.1 are:
* The Platform Edition provides a free commercial grade JMS implementation,
ideal for small-scale deployments and development environments on various
operating environments.
* The Enterprise Edition delivers maximum scalability and security features
necessary for larger full-scale deployments.
For specific details about the editions see the Administration Guide at:
http://docs.sun.com/source/817-0354-10/overview.html#20864
For more information about the product or to download the current version
please visit:
http://www.sun.com/software/products/message_queue
Receiving feedback from current and potential customers is important to the
product team. If you have questions, thoughts for additional features or
think you have found a bug, we encourage you to send the team feedback.
Please send mail to [email protected]. If appropriate, be sure to
include the product version, information on the platform you are using and
steps to duplicate the problem you are experiencing. If you are interested
in purchasing the product and have a sales related question send mail to
[email protected]
Thank you for your interest in Sun ONE Message Queue!

Customers who purchased the iPlanet Message Queue for Java version 2.0
Enterprise Edition, or the iPlanet Java Message Queue version 1.1 Business Edition,
who also have a current maintenance contract for this product, are entitled to a free
upgrade. Sun customers should use their normal support channels to request the
upgrade. All corporate customers with Sun Software Support contracts should be
automatically notified of the upgrade via the ProductTracker by SubscribeNet
program. If you haven't, please contact Sun Customer Service online or by phone at
888-786-8111. Parties interested in upgrading will be required to provide
proof-of-purchase. Customers of previous versions of the free Developer Editions, or
customers without a current maintenance contract on this product, can not upgrade
for free, they must buy the Sun ONE Message Queue 3.0 Enterprise Edition product,
or they can download the Sun ONE Message Queue 3.0 Platform Edition product for
free from: http://wwws.sun.com/software/download/download/5275.html

Actor framework strictly typed message queues?

I'm just getting to grasps with the Actor framework. I have implemented "similar" stuff in the past but I've approached it differently.
One thing I noticed was how easy it is to send a message to an incompatible actor core which results in a nasty run-time "to more specific class" error.
In the example project included with LV 2012, if I make the change shown below (OK, I am purposely senidng a wrong message on the given queue) I get no feedback from the IDE that an incompatible message is being sent ont he queue. I think this has to do with the Message queues being for the base actor class.
Is there no way to have the actual queues more strictly typed so that we can say that Launching Actor Beta will result in a Queue reference which is only compatible with Beta (or children) objects or does this ruin the entire concept? If possible, it would prevent the ability oto send incompatible messages completely which IMHO would be an enormous benefit.
The presentations on the Actor framework have shown huge benefits in strict typing of state machines (I'm referring to a couple of videos I've seen ont he NI website) but this element of things seems to be just a pokey as a string flatten and unflatten. Send the wrong message to the wrong receiver and >bang< run-time error.
Just thinking out loud.
Shane.
Say hello to my little friend.
RFC 2323 FHE-Compliant

So two days and no reply...
I'm referring in essense to this part of the actor framework white paper as included with the template in LV 2012.
Messages from Callee to Caller
When a caller wants to send a message to the callee, the caller knows the type of the actor that it launched, so caller can easily choose the right type of message to send. But when an actor wants to send a message to its caller, the actor does not necessarily know what type of caller it has, so it does not know what type of message to send. Ideally, actors should be usable by many different callers. That maximizes code reuse. But making the actor truly independent of the caller requires more effort than is warranted for the situation. There are three techniques for defining messages that an actor sends to its caller
The High Coupling Solution—In this solution, the callee actor is written specifically for one type of caller, and can never be used with any other type of caller. In this case, the callee knows details about the caller's interface, so it may simply call the Send Message VI of the appropriate message. The message type is thus hardcoded into the actor.
The Low Coupling Solution—This solution works best when you have a known inheritance hierarchy of callers. In this solution, you create a matching hierarchy of callee actors. So suppose you have callers Hard Drive, Air Conditioner, and Fire Suppression, each of which needs to launch a Fan actor. You would create the Fan class, and then inherit from it Fan For Hard Drive, Fan For Air Conditioner, and Fan For Fire Suppression. Each caller launches its specific callee actor. All of the main Fan class' code is shared, but when it comes time to send messages, the Fan class has a dynamic dispatch method for doing the sending, and each of the children overrides that method to send the message appropriate for its caller. Each callee is still coupled to a specific caller, but the system as a whole is flexible to accommodate new caller types.
The Zero Coupling Solution—In order to make the callee actor independent from the caller, the caller must tell the callee what types of messages to send so the callee avoids picking a type itself. The best implementation of this solution has the caller record a message into the callee at the time the callee is launched. The callee provides a Set <Type> Message.vi method, where <Type> is the particular event that will trigger the message to be sent. The caller sets the exact message it wants to receive when this event occurs. When the event happens, the callee sends the chosen message, without any knowledge of what kind of caller is receiving that message.
Often the callee will define an abstract Message class that it uses as the input type for Set <Type> Message.vi. Callers create their own specific child of this abstract class. This setup gives the callee a way to set data into the message through the API defined by the abstract class, and gives the message a way to deliver that data in a form the caller can consume through the various overload and extension VIs.
Would it be possible to get some examples of the three different approaches to typing of the messages? I'm aiming for the high coupling solution (with the option of slipping to option 2 through common ancestors) in order to provide the ability to detect wrong messages on wrong queues at edit time.
Shane
Say hello to my little friend.
RFC 2323 FHE-Compliant

Message Queue hardware requirements

Similar Messages

Maybe you are looking for