Personal tools

Partners

Upgraded Development Environment Deliverable Template

From MIKE2 Methodology

Jump to: navigation, search
This deliverable template is used to describe a sample of the MIKE2.0 Methodology (typically at a task level). More templates are now being added to MIKE2.0 as this has been a frequently requested aspect of the methodology. Contributors are strongly encouraged to assist in this effort.
Deliverable templates are illustrative as opposed to fully representative. Please help add examples to this template that are representative of the proposed output.

The Upgraded Development Environment task consists of completing the implementation of hardware and software needed by the developers that began in Phase 2. This is an ongoing infrastructure task. Once the development platforms are in place, this task will reactivate as necessary, usually at the beginning of a development cycle.

Contents

Example for a Upgraded Development Environment

Listed below is an example Upgraded Development Environment:

Client Development and Production Environment Requirements

Hardware Requirements

1. One Server with Intel processor speed of at least 1.5 GHz. Preferably a dual processor system.

2. 2 G RAM with 4 G swap space.

3. Minimum 1 GB Hard disk space. Recommended 20 GB for storing metadata source files and backups of the Client repositories. High-speed hard disk recommended.

4. TCP/IP and LAN access.

Network Setup

1. Development server must be accessible by the terminal services client from a client desktop that is on the AU domain.

2. Development server must be on the same network as the ClientStage servers. In other words, the Client server should be able to connect to the ClientStage servers over the network.

Software Requirements

1. Windows 2003 or Windows 2000. (ABC Task)

2. Microsoft Internet Explorer 4.01 or later. (ABC Task)

3. Microsoft XML Core Services 4.0 Service Pack 2. (ABC Task)

4. Microsoft SQL Server 2000 (with the latest services packs). (ABC Task)

5. Microsoft .NET runtime. (ABC Task)

6. Terminal services server. (ABC Task)

7. Outlook 2000 (required for setting up email notification in Client). (ABC Task)

8. ClientStage 7 Client software (Required by the ClientStage 7 MetaBroker in Client).

9. Client 7.5.1r1 (ABC or CSA Task)

  • Client Explorer
  • Client Architect
  • Client Administrator
  • Default Metabrokers
  • Client Listener
  • Process MetaBroker
  • All MetaBrokers that are provided on CD.
  • Apache Web Server. Will run on default port (9090).

10. CVS (File Version Control tool) (ABC or CSA Task)

  • CVSNT 2.0.51d or greater - CVS server for Windows (CVS is a file versioning tool)
  • TortoiseCVS 1.8.14 or greater - CVS client plugin for Windows Explorer
  • ViewCVS 1.0-dev-r6 or greater - Web Interface to CVS repository
  • ActivePython 2.4.1-247 or greater - Required by ViewCVS Web Interface
  • CVSgraph 1.5.2 or greater - Plugin for ViewCVS web interface to show graphical source tree

11. Internet Information Server running on default port. This is the client front-end for CVS. (ABC Task)

Server Logins

1. MSAdmin (Client Administrator) – NeABC to be part of the "Administrator" group privileges of the local computer. Login ID used for creating, extending and deleting Client directories.

2. MSUser (Client User) – NeABC to be part of the "Power User" group priviledges of the local computer. Login ID used for Client development.

SQL Server Logins

1. DBAdministrator (Database Administrator) – Has "Create Database" priviledges. This is required if the Client database gets corrupted and a new database neABC to be created.

2. MSAdministrator (Client Administrator) – Has "Create, Select, Insert, Update and Drop Table" priviledges.

Email Requirements

1. Set up email account in email server for Client to use.

2. Set up email profile in Windows 2003 for this email account.

Client Desktop Requirements

Basic Software Requirements

Number of desktops that need to meet these requirements – 3
1. Client 7.5.1r1.

  • Client Explorer
  • Client Architect
  • Client Administrator
  • Default Metabrokers
  • All MetaBrokers that are provided on CD.

2. Terminal Services Client.

Additional Software Requirements

Clientstage Client Desktop Requirements

Basic Software Requirements

  • Client 7.5.1r1.
  • Client Explorer
  • Client Administrator
  • Default Metabrokers

Client is required on the ClientStage client PC so that users can import (pull) metadata from Client. Installation of Client is only required on one development ClientStage Client PC per project.

Reason for Separate Development and Production Client (MS) Servers

  • The most significant reason for a DEV and PROD Client server is to maintain a high level of availability to users.
  • The development server is used for loading and testing the integration of new metadata sources with existing metadata that is held in development Client repository. Loading metadata into Client is a highly resource intensive process as the Client repository tries to use as much memory, CPU and database resources as possible. If we use a single server for performing, both, development activities and publishing production metadata, the performance of the server will be extremely poor and response times for viewing production metadata by business users will be slow.
  • If both, development and production loads are done on the same server, there is fair probability that the development processes may interrupt or even kill production processes.
  • Since the development server is used to test and load new metadata, there is the possibility of Client repository corruption. In this case, we may need to reboot the development server to fix the corruption issue. If the development Client repository and the production Client repository were on the same server, rebooting the server would result in making the production metadata unavailable
  • During development and testing, the Client developers require administrative privileges and the system for restarting various Client services and database resources. If the development repository and the production repository reside on the same server, we will not be able to have such operating privileges.
  • This approach follows standard best practice for delivery of software systems by separating development and production environments. It allows for controlled delivery of a system to a business as usual operations practice.
  • New versions of and updates to Client can be installed and tested separately without the risk of breaking the production installation. Dev and Prod installations cannot be logically separated on the Client system as they can be in a database.
  • The production environment can be handed over to production support in a discrete unit so that control and responsibility of the system can be clearly communicated.
Retrieved from "http://mike2.openmethodology.org/wiki/Upgraded_Development_Environment_Deliverable_Template"
Powered by omCollab