HP Software-as-a-Service

Transcription

1 HP SaaS POC Process for Performance Center HP Software-as-a-Service Table of Contents 1. GENERAL HOW TO REQUEST FOR A POC INSTANCE HOW TO CONNECT TO YOUR POC INSTANCE POC TERMS EXTENDING YOUR POC POC MODIFICATIONS ESCALATION PROCESS ONSITE COMPONENTS RESPONSIBILITIES REQUESTOR RESPONSIBILITIES HP SAAS RESPONSIBILITIES HP SOFTWARE SOLUTIONS ARCHITECT RESPONSIBILITIES POC CHECKLIST HP SOFTWARE SOLUTIONS ARCHITECT CHECKLIST CUSTOMER ROLES & RESPONSIBILITIES CUSTOMER CHECKLIST CONNECTIVITY REQUIREMENTS IOFW/MOFW DIAGNOSTICS...6 Page 1

2 1. GENERAL 1.1. How to Request for a POC Instance POC requests should be launched using the page: or for Partner POC. Check the appropriate boxes on the page, provide the information about your POC, and submit your request. Once HP SaaS receives your request off HP SaaS Portal, ticket will be open for you on Support Website, and you will be sent a ticket number in a separate . You can track the status of your ticket at You will need an HP Passport login and a SAID number to be able to login to HP Software Case Management System (SPARKS) How to Connect To Your POC Instance Within 3 business days of submitting your request you will receive an from HP SaaS with URL to access your Application Security Center POC instance: Login ID and password with administrative privileges MI Listener URL Diagnostics server URL Start and End dates of your POC 1.3. POC terms The project is valid for 30 days. 5 days prior to the expiration you will receive a reminder mail Expired projects will be deleted 90 days after the last expiration date If you would like to revive the project (within the 90 idle days), please contact the SOC, and the project will be valid for additional 30 days Please note: deleted projects will not be restored Extending Your POC Please send to extendsaaspoc@hp.com and include an original SPARKS case number (see Tracking Status of Your Request above) as well as business justification for your extension request. Page 2

3 1.5. POC Modifications In rare cases you might need to deviate from a standard POC provided by HP SaaS. Please be aware that such deviations will result in longer turn-around times and might be rejected by Product Management team of HP SaaS who approve such requests. If you need to modify a default POC, please send to enhancesaaspoc@hp.com Escalation Process Time critical issues can be escalated to the NOC who will help you resolve the issue and internally escalate as appropriate. Please see for Service Operations Center (SOC) 1.7. Onsite Components Installation and configuration of onsite components (injectors and monitors over the firewall) is requestor s responsibility. Please contact HP Software support organization for any issues regarding installation and configuration of onsite components. Page 3

4 2. RESPONSIBILITIES 2.1. Requestor Responsibilities You will be responsible for all scripting and load test setup for your prospect. You will be responsible for coordinating all activities between the prospect and HP SaaS. You will be responsible for demo of the product, integrations, features and functionalities. You will responsible for all onsite components configurations Hp SaaS Responsibilities HP SaaS will be responsible for the availability of your PC demo farm. HP SaaS will be responsible for creating the customer POC PC Project and user accounts and will work with the Solutions Architect to provide information regarding all managed components as deemed necessary for a particular POC. HP SaaS will be responsible for ensuring that a PC project and PC user account are available upon request for POC within 2 business days of submitting request Provide Diagnostic Probe Configuration details (if applicable) 2.3. HP Software Solutions Architect Responsibilities The Solutions Architect will be responsible for completing necessary forms and submitting it to saas-poc@hp.com. The Solutions Architect will be responsible for installing all onsite components (if needed) The Solutions Architect will be responsible for all configurations within PC upon initial customer instance setup by HP SaaS. The Solutions Architect will be responsible for coordinating all activities between the customer and HP SaaS. The Solutions Architect will be responsible for demo of the product, integrations, features and functionalities. Diagnostic Probe Configuration (if applicable) Page 4

5 3. POC CHECKLIST 3.1. HP Software Solutions Architect Checklist Please verify that the following items have been completed in advance of contacting HP SaaS for the POC: Timelines Agreement: There is agreement with the customer on timeline for POC Onsite Components Deployment: Please ensure that all onsite hardware is made available by the customer and install all onsite components as required by the architecture in the attached document. Connectivity Requirements: Identify what connectivity requirements are necessitated using the attached architecture document and ensure all connectivity requirements are dealt with before the start of a POC. In the case of Diagnostics HP SaaS requires an advance notice of 1 week, as HP SaaS will be required to open firewall rules and ports for 2 way connectivity. In the case of Diagnostics, HP SaaS will need an advance notice of 2 days to setup the commander Customer Roles & Responsibilities Often during POCs, the HP Software Solutions Architect needs additional technical or business information about how the application is implemented, deployed, and used. We ask that the customer will identify the individuals who fulfill the roles of Application Architect, System Analyst, Network Engineering and Security. We also recommend the customer let the team know that the Solutions Architect will be working on site and may possibly need some of their time Customer Checklist Please verify that the following items have been completed in advance of the HP Software Solutions Architect coming on site for the POC. NDA: If an NDA is required, please contact your HP Software account manager (see page 1) who will see that it is put into place. Work Area: Have you identified a work area for use by the HP Software Solutions Architect during the POC? If possible, please assure that a telephone and Internet access are accessible from the work area. Application to Monitor: Have you verified access to the Application to Monitor from the workstation(s)/server(s) that will be used during the POC? Customer Team: Have you identified one or two individuals that will work with the HP Software Solutions Architect throughout the day(s) of the POC? Note that at least one person should be present during the entire course of the POC. Page 5

6 4. CONNECTIVITY REQUIREMENTS Different components in PC require different connectivity requirements. This section outlines all the prerequisites for connecting onsite components to HP SaaS managed BAC. Please read through the connectivity requirements carefully for successful deployment of POC 4.1. IOFW/MOFW Description: If the customer requires an IOFW/MOFW due to the need to test an internal application, it's recommended that the Solutions Architect connect their OFW components securely via port 443. Please contact the NOC for the MIL IP to the PC Demo Farm. Requirements: IOFW/MOFW agents invoke the communication to the PC MIL through interval pings. The MIL will respond to a ping with it's instruction. This one-way invocation typically fits most customer's security requirements. The customer needs to ensure that their firewall allows for this one-way invocation from the IOFW/MOFW agents Diagnostics Description: For all HP SaaS customers as well as default for POCs, HTTPS communication is used between Mediator and Commander component. Requirements: Port 443 outgoing to be open from the customer environment Alternatives: It is not recommended but possible to specify non-secure HTTP traffic over port 80 instead, for example in order to save time for customer-side firewall rules. Please notify HP SaaS of this requirement. Page 6

7 5. APPENDIX A POC FLOWCHART The requester fills in the "POC with HP SaaS Page SOC open the project for 30 days, create user and pass and sends the details to the requestor The requestor details (especially address) will be added to the PC user Extend the expiration date in 30 days On the 25th day Site Scope auto process will open esar for production team to send expiration alerts Yes Request for extension? No The project expires after 30 days 2 1 Page 7

8 days from project expiration, Site Scope monitor opens esar for production to delete the project data No Yes Request for extension? Production team will delete the project data End Page 8