N1 Grid System Implementation

This section covers the realization of the architecture. Each phase of the implementation builds on the previous and is implemented within a pilot environment, outside of production.

A new wireless billing system is about to be deployed. Based on the steering committee's recommendations, the system is the first to receive the new N1 Grid system functionality. Phasing in of this functionality will be in conjunction with the other system testing that is being performed before the system goes into production.

ZYX-WV has a lab facility where these new products will be installed and integrated. After a successful pilot, the new wireless billing system will be brought into production using the new processes, tools, and management systems discussed within the architecture.

The new billing system uses the Sun Java Enterprise Server software stack and integrates with the identity management system that the company has also revamped and updated. The identity system is the cornerstone of the ZYX-WV desire to implement more foundation services that promote reuse and reduce cost and complexity.

Infrastructure Optimization and the Sun Management Center Software

Phase 1 targets the first tier of the wireless billing system and adds capabilities around network virtualization and security management. This phase introduces the ability to build a common platform, with the new common platform agents (Sun MC) as well as existing agents, such as NetBackup.

The utilization and availability management capabilities of the Sun MC software are also introduced in this phase. The Sun MC agents are installed and configured on each server automatically by using the golden image provided to the N1 Grid PS system. The Sun MC software has the ability to monitor web service applications and report availability and performance. This capability is introduced in this phase. However, it is not fully automated until the next phase application deployment automation.

Figure 12-2. N1 Grid PS and Sun MC Implementation

In FIGURE 12-3, Tier 1 web servers are built and brought into service using the N1 Grid PS. N1 Grid PS stores the server configurations, OS binaries, and common agent. All data, such as log files, are stored on NFS servers. Because of this, these servers do not need to be backed up by NetBackup, reducing the number of systems that must be backed up each evening. Phase 1 moves into production after a successful pilot.

Figure 12-3. N1 Grid SPS and Service Monitoring Implementation

Application Optimization

Phase 2 builds on Phase 1 by adding application provisioning and optimization capabilities. This phase enhances the ability to deploy and control applications and includes building clustered systems and application (Tier 2) and database (Tier 3) servers. Also in this phase, service availability using the Sun MC software is extended to end-to-end service level monitoring by using real-world transactions that hit each tier of the wireless billing complex.

Strategic Flexibility

After Phase 1 and 2 have successfully gone into production, Phase 3 adds additional functionality through strategic flexibility. A new service is being introduced that enables customers to view their billing information through a portal. The portal system for wireless access is a foundation service, managed by the foundation services application group. For this phase, wireless billing and wireless portal resources are going to share some of the same resources. Part of the wireless billing complex is only needed during billing cycle processing, which happens twice each month.

The wireless billing services are using N1 Grid Containers to ensure service levels and zone features to enhance security of the applications. These containers are provisioned by the N1 Grid SPS. Because components have been built for the N1 Grid SPS for these applications, as well as the portal applications, the IT department is able to manually move these applications based on need or on a schedule.

FIGURE 12-4 shows how the N1 Grid SPS can be used to deploy applications within N1 Grid Containers. Each application is mobile and can be redeployed within the resource pools, as needed. The application must be shut down before it can be moved, and all of it must be installed by the N1 Grid SPS; however, this does not offer mobility through the N1 Grid system. This resource pool is dedicated to offering database services for the rest of the applications. The billing service (App 1) and wireless portal (App 2) services share the same web servers and the 4x resource pool.

Figure 12-4. N1 Grid Containers and Application Mobility Implementation

Both services rely on containers to ensure QoS. Resource shares are increased and decreased based on the business priority of the service at the time. These tasks are controlled with the N1 Grid system. This phase is also put into production after a successful pilot.