nd.gov - The Official Portal for North Dakota State Government
North Dakota: Legendary. Follow the trail of legends

WebSphere Deployment Guide

Deployment Requests

ITD's online Work Management System (WMS) may be used to submit a "WebSphere Deployment" service request. The following fields need to be completed.

  • Short Description
    • To provide guidance to the request processor, prefix the short description with the following choices.  The first field is whether the deployment is for either the test environment or production environment (see Deploy EAR file to).  The second field references the deployment schedule (see Deployment Schedule).
      • TEST-ASAP-Incident#
      • TEST-COORD
      • TEST-ANY
      • PROD-ASAP
      • PROD-COORD
      • PROD-ANY
    • Please include the application name
  • EAR File Location
    • For those customers who have shared disk with ITD, please provide location where EAR file is located.  For customers who do not share a file server with ITD, please utilize the Secure File Transfer System.
  • Deploy EAR file to
    • Internal Test
    • External Test
    • Internal Production
    • External Production
  • Initial Deployment
    • Indicate if this is the first time the application is deployed to a region.
    • Please allow for 24 hours to have initial deployments completed.  For re-deploys, see Deployment Schedule.
    • All initial deployments in any production region require Load Testing.  Attach the load test results or identify the location of the results in the comments section.  Subsequent deploys that contain new functionality of significant changes also require a load test.
  • Coordination Requirements
    • Identify any coordination requirements for this application deployment.
    • If additional service requests are either pre-requisites or dependents to this request, please identify them here.
    • Allow ample lead time to ensure resources are available.
    • If a coordinated deployment is needed after-hours, prior approval is needed to ensure resource availability.
  • Data Source Information
    • Required on new deployments that have database requirements
    • Not required on re-deploys if no change is required
    • Database Driver
    • Name
    • JNDI Name
    • Database name
    • URL Prefix
      • Please indicate the URL desired for this application
  • Database Connections flushed
    • Briefly describe why
  • Restart server
    • Briefly describe why
  • Secured Application
    • Does this application require SSL?
  • Context Root
  • Security Mappings
    • Security roles should match directory group names.  If for some reason this is not possible, list each role and to what group it should be mapped to.
  • Comments
    • Provide any additional information necessary to successfully complete this request.

Deployment Schedule

Initial Deploys

Please provide for 24 hours for new deployments to any region.

Test Redeploys

A deployment of a newer version of an existing application will be deployed based upon classification of deployment.  Please keep in mind that a re-deploy of an application is disruptive process to users of the application:

ANY
The deployments can be done anytime but no later than the following intervals.  Any request that is submitted on a business day prior to 4:30 pm will be completed by 8:00 am the next business day.  Requests that arrive after 5:00 pm and prior to noon the following business day will be completed by 1:30 pm that business day.  This will be the chosen schedule if a category is not specified.
ASAP
The goal is to complete these requests within 30 minutes of submission.  For large applications or situation involving complex deployment tasks, it’s possible this goal is unattainable.  This category is intended for all requests where deployment is critical to the continued use of the application. For example, if working a production incident and a deployment is needed to the test environment to ensure accuracy, include the incident number in the Short Description as described above.
COORD
This classification is intended for deployment requests that require coordination with other events, service requests or need to be completed at a certain time.  The goal for completion is largely dependent upon the coordination complexities.  This category is for use when either ANY or ASAP is unacceptable. Ample lead time is required to ensure resources are available at the requested time.

Production Redeploys

Deployments typically result in a short outage or disruption to end users of the application.  Deployments will be completed based upon the following classification:

ANY
The deployments can be done anytime but no later than the following intervals.  Any request that is submitted on a business day prior to 4:30 pm will be completed by 8:00 am the next business day.  Requests that arrive after 5:00 pm and prior to noon the following business day will be completed by 1:30 pm that business day.  This will be the chosen schedule if a category is not specified.
ASAP
The goal is to complete these requests within 30 minutes of submission.  For large applications or situation involving complex deployment tasks, it’s possible this goal is unattainable.  This category is intended for all requests where deployment is critical to the continued use of the application.
COORD
This classification is intended for deployment requests that require coordination with other events, service requests or need to be completed at a certain time.  The goal for completion is largely dependent upon the coordination complexities.  This category is for use when either ANY or ASAP is unacceptable. Ample lead time is required to ensure resources are available at the requested time.

Notes

  • For deployments that cannot be completed as requested, the requester will be contacted to discuss an alternate schedule.
  • During legislative session, internal production deployments to servers running legislative applications will be limited to times deemed acceptable and will require prior approval. Deployment requests for other servers will occur as normal.

Related Service

 

What Our Customers Are Saying

Great attention to detail. Thank you.

Pembina County Auditor
October 20, 2014