SUPPORT DOCUMENTATION USER GUIDE

SUPPORT DOCUMENTATIONUSER GUIDESUPPORT REQUEST TICKETING SYSTEM

AUTOMATION FOR ORACLE® EBS & ORACLE® ERP CLOUD

March 2018

2

TABLE OF CONTENT.INTENDED AUDIENCE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3INTRODUCTION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

CONTACTING SUPPORT � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �4SUPPORT SERVICE HOURS � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �4

TICKET LIFECYCLE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5IMPORT CERTIFICATE TO BUILD BUNDLED JRE� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �5

TICKET POLICY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6TICKET PRIORITY AND RESPONSE TIME � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �6TICKET ASSIGNMENT � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 7TICKET ESCALATION � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 7

USING THE SUPPORT REQUEST. . . . . . . . . . . . . . . . . . . . . . . . . . 8LOGIN TO THE TICKETING SYSTEM � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �8OBTAINING A NEW PASSWORD � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �8CREATING A TICKET � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �8TICKET CLOSURE � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �12TICKET PRINTING � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �13

3

INTENDED AUDIENCE.The intended audience for this Support Request User Guide is customers and support engineers usingthe Support website.

The following contents provide the appropriate channels and proper procedures to open a SupportRequest Ticket (hereafter referred to as Ticket) and solve issues. Also provided is information on howto escalate a Support Request when an urgent response is needed.

4

INTRODUCTION.Rapid4cloud provides technical assistance for all Rapid products and the Oracle e-Business Suite. Youcan open a Ticket at the Support website (https://support.rapid4cloud.com/). The web site is available24/7. It uses a standard web interface to make obtaining information and resolutions quicker andeasier.

CONTACTING SUPPORT

SUPPORT SERVICE HOURS

If for any reason the support website cannot be accessed, please call the following number and leave amessage or voice mail: +1 415 373 0180 (USA)The phone should be answered by a person 24x7 – but just in case – voicemail should be active whenno person is available

Electronic support: 24 hours per dayPersonal support: Refer to your support contract.

5

TICKET LIFECYCLE.IMPORT CERTIFICATE TO BUILD BUNDLED JRE.

In general a Ticket has the following lifecycle:New Request Open (Under Investigation Request More Info) Work inProgress Solution Offered Pending Autoclose Closed

When a new Ticket is created, an e-mail notification is sent to the Customer Care Manager who takesaction on assigning appropriately skilled staff as Ticket agents. Upon assignment from the CustomerCare Manager, an email notification will be automatically sent to the Ticket Owner and TicketResponsible agents who take responsibility of the Ticket.

Updates by the agents will generate an email notification to the requester. It is recommended that therequester regularly check the progress of the Ticket via the Support website to ensure that email orSPAM filtering is not interfering with delivery of updates or attachments. The process of a hypotheticalticket may be as follows:

SCENARIO:Day 1: New Request Open Under InvestigationDay 2: Request for more information Waiting for requesterDay 3: Still waiting for requester, support will send notification to the requester.Day 4: If the status remains unchanged, the requester will be notified that the Ticket will be closed by support Pending AutocloseDay 5: Support will close the Ticket Closed unsuccessful

The requester may reopen the Ticket by replying to an email notification generated under this Ticket or by visiting the Support website and reviewing closed Tickets.

6

TICKET POLICY.All Tickets will be monitored on a daily, weekly and on-demand basis. Daily• All outstanding Tickets are reviewed by Rapid4Cloud management.• An assessment on the quality of the interaction with requester is undertaken to ensure the information and actions being taken are a value add and professional in manner.Weekly• A weekly review by management is conducted to ensure that daily and weekly objectives are met.On-demand• Any Ticket open for more than 10 business days is monitored by management to ensure it is being addressed in the most expedient manner.

TICKET PRIORITY AND RESPONSE TIMEA Ticket, after review by Rapid4Cloud support team, will be assigned one of the following priorities:Very-High, High, Medium, Low, or Very Low.

VERY-HIGHResponse according to SLA.Your production use of the supported programs is stopped or so severely impacted that you cannotreasonably continue work. You experience a complete loss of service. The operation is mission criticalto the business and the situation is an emergency. A very-high Ticket has one or more of the followingcharacteristics:• A Rapid4Cloud product bug causes data becomes corrupted.• A critical documented Rapid4Cloud function is not available.• The system hangs indefinitely due to Rapid4Cloud, causing unacceptable or indefinite delays• for resources or response.• The system crashes and crashes repeatedly after restart attempts due to Rapid4Cloud.

Reasonable efforts will be made to respond to very-high priority Tickets within the agreed period.Rapid4Cloud will work 24x7 until the issue is resolved or as long as useful progress can be made. Youmust provide Rapid4Cloud with a contact during this 24x7 period, either on-site or by pager/cell phone,to assist with data gathering, testing and applying fixes. You are requested to propose this severityclassification with great care, so that valid very-high Ticket situations obtain the necessary resourceallocation.

HIGHResponse according to SLA.Reasonable efforts will be made to respond to high priority Tickets within the agreed period.

MEDIUMResponse by next working day within Rapid4Cloud business hours.You experience a severe loss of service. Important features are unavailable with no acceptableworkaround, however operations can continue in a restricted fashion.

7

LOWResponse within 3 working days within Rapid4Cloud business hours.You experience a minor loss of service. The impact is an inconvenience, which may require aworkaround to restore functionality.

VERY LOW Response within 5 working days within Rapid4Cloud business hours.Enhancement requests to KB or the tool itself.

TICKET ASSIGNMENTOnce a Ticket is opened, the Customer Care Manager is responsible for taking action or assigningappropriately skilled staff as ticket owners until it is completed.

TICKET ESCALATIONTo escalate a specific Ticket or discuss issues on any Ticket, you can contact the Customer CareManager. See section 1.1 Contacting Support for details.

8

USING THE SUPPORT REQUEST.LOGIN TO THE TICKETING SYSTEMUse the following steps when logging in to the Ticketing System:1. Connect to the Support website URL provided: https://support.rapid4cloud.com/2. Enter your User Name and Password. See Figure 4.1.3. Click Log In button.

OBTAINING A NEW PASSWORDUse the following steps if a user password has been forgotten:1. Connect to the Support website URL provided: https://support.rapid4cloud.com/2. Click on the Forgot password? link.3. Enter your User name and click the Submit button. An email will be sent directly from Supportteam with a new password to the email registered to that User name. See Figure 4.2.

Figure 4.1 The Ticketing System Login page.

Figure 4.2 Request new password page.

CREATING A TICKETAfter logging in to the Ticketing System, all the previous Tickets that have been created will be shown.See Figure 4.3.

Figure 4.3 My Tickets review page.

9

Create a new Ticket by selecting New Ticket from the menu. See Figure 4.4.

Figure 4.4 New Ticket submission form.

In order to complete the ticket request detail, fill in the form:

Subject: Provide a brief summary of the issue.

Text: Provide a detailed explanation of the issue. Include screenshots and version information forall products in use in addition to exhaustive steps to reproduce the issue.

Attachment: Upload all necessary supporting attachments to troubleshoot the issue. Includescreenshots, injection log files, debug log files, BR100 files, BWP files, etc.You can find a sample Ticket in the Figure 4.5.

10

Figure 4.5 Submit the new Ticket with extensive details and documentation.

To submit the new Ticket, click the Submit button, the system will create a Ticket number as seen inFigure 4.6.

Figure 4.6 My Tickets review page.

11

The Ticket has now been submitted to the Ticketing System. Support team members will beautomatically notified by email. Below are the meanings of the headings shown in Figure 4.7.

AGE: How long this ticket has been open.

SUBJECT: Provide a brief summary of the issue (provided by you).

STATE: The possible Ticket statuses are:• New: The Ticket is still new. Support has not yet taken any action.• Under Investigation: The Support agent is determining the type of issue and what needs to

be accomplished to resolve it.• Under Review : The Support agent has escalated the issue to management to decide the

course of action for the ticket.• Waiting on customer: The Support agent has requested additional information of feedback

from the Customer. f no feedback is received within the timeframe communicated by theSupport agent, the ticket will be changed to the appropriate Pending auto close status.

• Work in Progress: The solution is in development; in certain cases an ETA will beprovided.

• Pending auto close+: A solution has been provided or the issue has been determined to beunrelated to the Rapid4Cloud product. If no feedback is received within the timeframecommunicated by the Support agent, the ticket will be changed to Closed successful status.

• Pending auto close-: A solution has not been offered. If no feedback is received within thetimeframe communicated by the Support agent, the ticket will be changed to Closedunsuccessful status.

• Closed successful, A solution has been delivered and the Customer accepted or failed toprovide feedback on the success of the solution.

• Closed unsuccessful, Ticket has been closed even though the issue is not resolved.

QUEUE: Indicates the ticket type. For example, issues related to KB will go in one of thequeues “KB - Bug” or “KB - Enhancement

12

Once the issue is solved the Ticket can be closed. There are two ways to close a Ticket.1. When a notification is received via email that a solution has been provided: reply to that mailand ask Support to close the Ticket.

2. Close the Ticket on the Support website.2.1 Login as described in 4.1 Login to the Ticketing System.2.2 Search for the Ticket to be closed.2.3 Open the ticket. See Sample as shown as Figure 4.7

2.3.1 Explain why the Ticket is being closed.2.3.2 Select next state:

• Closed successful: The issue is resolved.• Closed unsuccessful: The issue is unresolved but no longer requires action by Rapid4Cloud support team.

2.3.3 Click Submit.2.4 A notification will be sent to the requester email confirming the closure of the Ticket.

Figure 4.7 Ticket closure by Customer.

TICKET CLOSURE

13

If desired, the Ticketing System provides print functionality. The following are steps to print a summaryof your tickets:

1. Login as described in 4.1 Login to the Ticketing System.2. Click ‘Search’ in the ticket menu and define the criteria.3. At the ‘output to’ section, select ‘Print’ and click ‘Search’ button. See Figure 4.8.

Figure 4.8 Ticket printing.

TICKET PRINTING

14

Figure 4.9 Ticket search results.

4.The results generate a printer-friendly summary of the tickets that fit the search criteria. SeeFigure 4.9.

AUTOMATION FOR ORACLE® EBS & ORACLE® ERP CLOUD

We will appreciate if you do not print this document.In case you really need to print it, please recycle.

Oracle and Java are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.