C1000-174 Deploy and Administer Applications

Deploy and Administer Applications Detailed Explanation

Deploy and Administer Applications focuses on deploying applications efficiently and ensuring they remain stable. This section covers the deployment process, managing application versions, and monitoring application performance.

Deploying and administering applications is crucial to delivering software effectively. It involves ensuring environment consistency, automating the deployment process, and managing versions for stability and easy rollback when necessary.

a. Application Deployment Process

The application deployment process involves preparing and deploying applications in a structured and reliable way. It includes managing different environments, setting up automated deployment pipelines, and using containerization to ensure consistency.

1. Environment Consistency Management

Environment consistency management ensures that the development, testing, and production environments are aligned in their configurations, preventing issues that can arise from environment differences.

• Why consistency matters: A common issue in application deployment is that code might work in one environment (like development) but fail in another (like production) due to configuration differences.
• Best practices for consistency:
  • Use configuration management tools: Tools like Ansible or Terraform help ensure configurations are consistent across environments.
  • Standardize dependencies: Ensure all environments have the same versions of software, libraries, and dependencies.
• Example: If an application relies on a specific version of a database, ensure that the same database version is used in development, testing, and production. This prevents unexpected issues during deployment.

2. Automated CI/CD Pipeline

CI/CD (Continuous Integration/Continuous Deployment) pipelines automate the process of integrating, testing, and deploying code, making it faster and more reliable.

• Why CI/CD is beneficial: By automating deployment tasks, CI/CD pipelines reduce human errors and enable faster, more frequent releases.
• How CI/CD pipelines work:
  • Continuous Integration (CI): Every code change is automatically tested to ensure it doesn’t introduce bugs. Developers merge changes frequently, so the codebase remains stable.
  • Continuous Deployment (CD): After passing tests, code is automatically deployed to a staging or production environment.
  • Tools: Common tools for CI/CD include Jenkins, GitLab CI, and CircleCI.
• Example: When a developer pushes code to a repository, the CI/CD pipeline runs tests on the new code. If tests pass, the pipeline deploys the code to a staging environment, where it’s reviewed before going live.

3. Containerized Deployment

Containerization packages an application and its dependencies into a container, ensuring it runs consistently across different environments.

• Benefits of containerization: Containers make applications portable and easy to deploy, regardless of the underlying environment.
• Tools for containerization:
  • Docker: Docker packages applications in containers, making them easier to deploy and manage.
  • Kubernetes: Kubernetes manages and orchestrates containers at scale, handling deployment, scaling, and availability.
• Example: An application packaged in a Docker container can run on any server that supports Docker, ensuring consistency from development to production.

b. Application Version Control and Rollback

Version control and rollback strategies help manage application updates, ensuring stability and enabling quick recovery if an issue occurs.

1. Blue-Green Deployment

Blue-green deployment is a strategy for rolling out new versions of applications without impacting the existing, stable version.

• How blue-green deployment works:
  • Blue environment: The current stable version of the application.
  • Green environment: The new version of the application, deployed in parallel with the blue environment.
  • Switching environments: When the green environment is ready, traffic is shifted to it. If any issues arise, traffic can be quickly redirected to the blue environment.
• Benefits:
  • No downtime: Users experience no disruption during the switch.
  • Easy rollback: If problems are detected, it’s simple to revert to the blue environment.
• Example: Suppose a new feature is deployed in the green environment. After testing and verification, user traffic is gradually shifted from blue to green. If any issues arise, traffic can be immediately redirected back to the blue environment.

2. Version Rollback

Version rollback allows you to revert an application to a previous stable version if the new version has issues.

• Why rollback is important: Bugs or unexpected issues can arise in new versions, and the ability to quickly revert helps maintain stability.
• Rollback process:
  • Versioning: Each deployment is versioned so that it’s easy to identify and switch back to a specific version.
  • Automated rollback: CI/CD pipelines often include automated rollback processes to simplify reverting.
• Example: If an e-commerce platform releases a new update that unexpectedly crashes the checkout process, the rollback feature can quickly return the application to the previous version, minimizing downtime.

3. Continuous Monitoring and Optimization

Continuous monitoring and optimization ensure that the application is running smoothly and performing well after deployment. This allows for prompt responses to any performance issues.

• What to monitor:
  • Performance metrics: Track response time, error rate, and resource usage (CPU, memory) to ensure applications meet performance expectations.
  • User experience: Monitor user behavior and feedback to identify potential issues.
• Optimization process:
  • Adjust resources: If an application uses too many resources, optimize its configuration or scale resources as needed.
  • Update configurations: Refine configurations based on performance feedback to improve efficiency.
• Example: After deploying an application update, monitoring reveals that response times are high during peak hours. Scaling resources or optimizing the application code can address this issue.

Summary

Deploy and Administer Applications involves a structured approach to releasing, managing, and optimizing applications in the cloud environment.

1. Application Deployment Process: Ensures environment consistency, automates deployment through CI/CD, and uses containerization for reliability across environments.

2. Application Version Control and Rollback: Uses strategies like blue-green deployment for safe updates, allows for easy rollback, and continuously monitors applications to detect and address issues promptly.

Together, these practices create a robust deployment process that reduces downtime, improves stability, and maintains high performance.

Deploy and Administer Applications (Additional Content)

WebSphere ND 9.0.5 application deployment differs from containerized CI/CD models. Instead of Docker and Kubernetes, it relies on:

• EAR/WAR file deployments.
• WebSphere Admin Console & wsadmin scripting.
• Automated deployment using WebSphere Job Manager.
• Version control using multiple application versions.
• Monitoring with Tivoli Performance Viewer (TPV) and Performance Monitoring Infrastructure (PMI).

This guide covers WebSphere ND-specific deployment, rollback, and monitoring strategies.

1. WebSphere ND Deployment Methods

Unlike cloud-native deployments, WebSphere ND applications are packaged as Enterprise Archives (EARs) or Web Archives (WARs) and deployed via:

Deployment Method	Description
WebSphere Admin Console	GUI-based manual deployment.
wsadmin scripting	Command-line deployment for automation.
Job Manager	Automates deployment across multiple WebSphere nodes.

1.1 EAR/WAR File Deployment

Deploying via WebSphere Admin Console

1. Go to WebSphere Admin Console (https://Dmgr_IP:9043/ibm/console).
2. Navigate to Applications → New Application → Install.
3. Upload the EAR/WAR file.
4. Configure JNDI, classloaders, and security roles.
5. Click Save and Start.

Automating Deployment with wsadmin

wsadmin.sh -c "AdminApp.install('/opt/apps/MyApp.ear', '[-node Node01 -server Server1]')"

This command deploys MyApp.ear to Node01 → Server1.

1.2 WebSphere ND Deployment Automation

Instead of CI/CD tools like Jenkins, WebSphere ND uses:

Automation Tool	Function
Job Manager	Automates deployments across multiple nodes.
AdminApp Commands	Automates silent deployments.

Example: Deploying an EAR File Using Job Manager

1. Open WebSphere Admin Console → Job Manager.
2. Create a new job → Select Install Application.
3. Choose target WebSphere nodes.
4. Click Submit Job.

2. WebSphere ND Environment Consistency

Unlike Terraform and Ansible, WebSphere ND ensures consistency through:

Feature	Description
WebSphere Profiles	Isolated configurations for different environments.
Configuration Synchronization	Deployment Manager (dmgr) syncs all nodes.

2.1 WebSphere Profiles

Profile Type	Purpose
Cell Profile	Multi-node deployment (managed by dmgr).
Application Server Profile	Standalone WebSphere instance.
Custom Profile	Cluster member without admin capabilities.

Example: Checking WebSphere Profiles

wsadmin.sh -c "print AdminConfig.list('Server')"

2.2 Configuration Synchronization

To force node configuration sync:

syncNode.sh Node01

This ensures all nodes receive the latest application updates.

Example: Debugging Environment Inconsistencies

If an app works in development but fails in production, check:

• JVM heap size differences.
• JNDI data sources (ensure consistent database URLs).
• Security role mismatches.

3. WebSphere ND Version Control and Rollback

Instead of blue-green deployment, WebSphere ND uses:

• Multiple Application Versions (rollback capability).
• Parallel Deployment (running two versions at once).

3.1 Rolling Back to a Previous Application Version

WebSphere ND allows multiple versions of an application to be installed.

Example: Rolling Back an Application

wsadmin.sh -c "AdminApp.rollback('MyApp')"

This command reverts to the previous stable version.

3.2 Parallel Deployment (Side-by-Side Deployment)

This approach allows running two versions simultaneously.

Example: Running v1.0 and v2.0 in Parallel

1. Deploy v1.0 as the default application.
2. Deploy v2.0 under a different context path (/test).
3. Gradually switch users to v2.0.
4. If v2.0 fails, remove it and continue using v1.0.

4. WebSphere ND Application Monitoring

Unlike Prometheus/Grafana, WebSphere ND uses:

Monitoring Tool	Purpose
Tivoli Performance Viewer (TPV)	Monitors CPU, memory, and thread pools.
Performance Monitoring Infrastructure (PMI)	Collects real-time performance data.

4.1 Monitoring Applications with TPV

1. Open WebSphere Admin Console → Monitoring and Tuning.
2. Select Tivoli Performance Viewer.
3. Choose the WebSphere server to monitor.

Example: Investigating Slow Response Times

• Open TPV → Active Threads.
• If WebContainer pool is full, increase max threads.

4.2 Enabling PMI for Application Metrics

Enable PMI (Performance Monitoring Infrastructure) via wsadmin:

wsadmin.sh -c "AdminConfig.modify(AdminConfig.getid('/Server:server1/'), [['enablePerformanceMonitoring', 'true']])"

PMI collects JVM heap usage, database connection pool metrics, and request response times.

Example: Identifying a Memory Leak

1. Use PMI to track heap memory.

2. If memory usage steadily increases, analyze Garbage Collection (GC) behavior.

3. Adjust GC settings:

<jvmEntries initialHeapSize="4096" maximumHeapSize="8192"/>

4. Restart the WebSphere instance.

Summary: WebSphere ND 9.0.5 Deployment and Administration

Category	Best Practice
Deployment Methods	Use WebSphere Admin Console, wsadmin, or Job Manager.
Environment Consistency	Ensure WebSphere Profiles and Configuration Sync (syncNode.sh).
Version Control & Rollback	Use AdminApp.rollback() or Parallel Deployment.
Monitoring	Use TPV for thread pools and PMI for performance data.