- VMware vSphere 4.x
- 1 vCPU with a 1GHz Reservation (Host
machine CPU 2.5GHz or higher)
Storage requirements of the
application libraries and binaries are limited to
approximately 5GB of space.
Specific client requirements and modifications might increase
storage requirements but this must be evaluated.
Database storage is used for minimum storage of user settings,
and customization. All other storage in the database is
related to client requirements for caching information read
from SAP. In large environments if a network SQL server is
available it is recommended to put the database on the network
Windows 2008 Server (32 bit)
- Minimum required memory is 2GB.
- Recommended memory sizing is 4GB
Required Application Services
- Microsoft Windows .Net Framework 3.5
- Microsoft Windows Internet Information
- Microsoft SQL Server access on required
Please note that the application
performance is relative to the client's environment and the
types of queries and data that will be retrieved / written to
SAP. CPU and memory requirements are dependent on the client's
requirements for entry and display of information and the
modules that are active.
Separate application servers
can be either independent or clustered in order to satisfy
the client needs or requirements.
Logical Application Architecture
Communi-T can be architected in
several different environments in order to respond to varying
solution requirements, being externally facing DMZ based or
fully secured internally facing. In some cases, Communi-T is
architected to provide access to both internally and
externally facing audiences by leveraging the Microsoft
Windows security model.
Communi-T requires a Microsoft
IIS application server with ports 80 and/or 443 opened. Access
to a Microsoft SQL database is required on port 1433 and
access to the required SAP systems on standard port 3300.
Communi-T recommends that its
application run on VM Ware being such a lightweight service.
The following diagram illustrates
the Communi-T flow at the logical layer:
In most externally facing
application scenarios, Communi-T should reside in a
well-secured DMZ with limited access to internal data.
Communi-T best practices demand that a well hardened Microsoft
Server be implemented with proper network security practices
in place in order to prevent malicious attacks on the
The diagram below illustrates a
simple solution where Communi-T resides on a well secured DMZ
and proper natting is in place between firewalls, limiting IP
based traffic by filtering IP Addresses and ports.
Customers should refer to their
internal security policies and guidelines and implement a
proper security model in order to reduce risk.