Business News
Syndicate
Home arrow Sun Documentation arrow System Implementation
System Implementation
System Requirements PDF Print E-mail
User Rating: / 0
Introduction
The hardware and software requirements for running SunSystems 5 vary depending on the type of deployment you chose, either Standalone, Two Tier or Three Tier installation. Whichever type of deployment you choose, the requirements in this section should be regarded as the minimum.
Discuss in forum
Read more...
SunSystems Deployment Options PDF Print E-mail
User Rating: / 0
The SunSystems  can be deployed in several combinations to utilise the hardware configuration you have at your disposal.
Discuss in forum
The deployment combinations available are known as Installation Types and these are as follows:
  • Stand-alone Installation
  • Two Tier Installation
  • Three Tier Installation
  • Mixed Platform Installation.






Additional deployment options available are:
  • Thin Client Technologies
  • Report Server.


 

Stand-alone Installation
The stand-alone implementation is the simplest deployment of SunSystems 5. The Client,
Application and Database layers are present on a single machine. This type of installation suits single user sites, or where only one user requires access to the database at any one time.
Two Tier Installation
In this type of installation the Application and Database layers reside on the Server and the Client layer resides on the Client. More than one Client can be set up. All of the process logic is retained on the Server together with the data storage. This ensures a more secure application. This type of installation is suited to a LAN deployment due to expected bandwidth consumption. It also has the benefit of a low Client resource usage and additional administrative overheads are
reduced, due to user file propagation from the server, which allows central control of these files on the server. Connection across the LAN from the Client to the SunSystems 5 Application layer on the Server is made via TCP/IP.
Three Tier Installation
In this type of installation the Client, Application and Database layers are distributed across at least three machines, and more than one Client can be set up. A three tier installation is best suited to LAN deployment and gives the greatest distribution of resource usage between at least three machines, and as such is suited to high volumes of concurrent users where performance is critical.
Integration of Additional Application Servers
It is possible to distribute the workload of an Application Server by introducing additional Application Servers and assigning each server a number of Clients. See SunSystems 5 Configuration in a Load Balancing Environment for details.
Mixed Platforms
SunSystems supports some mixed environments of operating systems and RDBMS that participate in a single installation. For example, in a three tier installation the client machines could be Microsoft Win32, the SunSystems application server could be Microsoft Advanced Server 2000 and the database may reside as Oracle on a UNIX Server.
Thin Client Technologies
Thin client technologies enable SunSystems 5 to extend beyond the LAN environment onto the WAN and the Internet. These technologies also have the potential to add an extra layer to the deployment methods previously explained. The two best-known technologies are Citrix MetaFrame and Microsoft Terminal Server, which have the capability to deliver SunSystems 5 presentation to a thin desktop such as a web browser, and help minimize network bandwidth consumption. Both technologies have unique technical advantages and merits together with associated cost implications. These should be considered with the help of your regional support representative if you intend to deploy SunSystems 5 with either of these enabling  technologies.
Citrix MetaFrame
This installation is typically used to run SunSystems 5 over a WAN and can be deployed in a multi-tier environment. For example, the Citrix server could act as the client machine, with the application loaded on a separate server, and the database on another server. The database could also be on the same server as the application, depending mainly on the number of users. SunSystems 5 can also be deployed on Microsoft Windows Terminal Server although deployment is limited to a LAN. It is recommended that just the Client layer be installed on the Microsoft Windows Terminal Server and on the Citrix Terminal Server.
Discuss in forum

Write Comment (1 Comments)

SunSystems Architecture PDF Print E-mail
User Rating: / 0
According to the client-server paradigm SunSystems comprises of three main components or layers.
The Client Layer
This layer can be installed as a complete entity onto one machine, known as a Client. It enables the user to interact with SunSystems 5 via a Graphical User Interface (GUI). All user input and validation is performed within the Client layer. All communication with the server i.e. downloading updated forms, is handled by the Comms Routines.
The Application Layer
This layer can be installed either with the Client and Database layer in a stand-alone deployment, with the Database layer, or on dedicated Application Server machine(s).
The Database Layer
This layer is dedicated to database management, which can be managed by a proprietary Relational Database Management Systems (RDBMS) i.e. Microsoft SQL Server or Oracle. It can be installed on the same machine as the other layers, or on a dedicated Database Server machine.
These components can be installed either as a complete entity onto a single machine, or distributed amongst several client and server machines.
Discuss in forum

Write Comment (1 Comments)

SynSystems Implementation Flow Chart PDF Print E-mail
User Rating: / 2
In this article I would like to highlight the major system implementation steps required to successfully implemet SunSystems5:
Read more...
SunSystemst Post Installation Checklist PDF Print E-mail
User Rating: / 0
After installing SunSystems, restart the computer and complete the following checklist:
Database Server

  • Check that the database has been created using the relevant DBA tool.
  • Check that the SuperUser, e.g. SUN and SSA logins have been created.
  • Check that SuperUser, e.g. SUN is the owner of the database and SSA has been created as a user.
  • If the database was copied from the installation CD, check that the PKP tables, views and processes exist.
  • Ensure that you have run the Filter Data Dictionary Regeneration tool from Navigation Manager. To check that the tool has been initiated, open Account Inquiry (AQ) from Navigation Manager. If an error message appears, Filter Data Dictionary Regeneration has not been run.
Application Server

  • Check the ODBC DSN has been configured correctly and connects with the database.
  • Check that SunSystems Session Manager is running. 
Client

  • Check that Navigation Manager runs successfully logging in as SuperUser, e.g. SUN.
  • Ensure that SunSystems is serialised.
  • Create a new operator and log out, then log in again as the new operator.
  • Check that the ODBC is connected successfully by running a report.

Discuss in forum
























Read more...
<< Start < Previous 1 2 Next > End >>

Results 1 - 9 of 11
Latest Articles
 
 
Popular Articles
New Forum Topics
Place your ads here: