BMC Remedy Action Request System 7.6.04: BMC Remedy Mid Tier ...

More documents

Recommendations

Info

BMC Remedy Action Request System 7.6.04 78 BMC Remedy Mid Tier Guide If you have placed support files under any subdirectories, they must be added to the URL. For example, if you have created an additional directory and a supporting file, enter: http://midTierServer/arsys/apps/ARSystemServer/applicationName/ resources/SubDirectoryName/fileName NOTE To access application support files, you must have a valid AR System login ID. Specifying parameters in URLs for direct access You can use the ViewFormServlet to open a specific form and pass parameters such as a user name or a qualification. NOTE When a user enters a URL from a previous version of AR System (a legacy URL), the system redirects the user to the proper form if the URL uses ViewFormServlet. If the URL does not use ViewFormServlet, users must enter the new URL. At a minimum, you must supply the server name and form name. If more than one view of a form is available, the system selects a view based on certain criteria, as described in “How a view is selected” on page 89. Values in URLs are case-sensitive. For example, ViewFormServlet and viewformservlet are not the same. Supported parameters in AR System A list of available views for the user is generated based on parameters specified in the URL. At a minimum, you must specify values for form and server. Include additional parameters as necessary, depending on the number of views available for the form and the requirements of the user. The following table lists supported parameters, their descriptions, and possible values. All parameters and values are case sensitive. Table 3-2: Supported parameters (Sheet 1 of 2) Parameter Description Possible Values form (required) Name of the AR System form to be accessed. URL-encoded string view View label for the preferred view. See “How a view is selected” on page 89 for information about how a list of possible views is generated for the user. URL-encoded string app Application (container) name. If specified and valid, the file for the view is called from the application-specific directory. URL-encoded string
Table 3-2: Supported parameters (Sheet 2 of 2) URLs for forms and applications Parameter Description Possible Values server (required) Name of the AR System server to be accessed. The server used must be an available server listed in the Mid Tier Configuration Tool. mode Mode in which the form will be opened. If not specified, Search will be used. eid Request ID of a form entry. Provides direct access to a specific request on the form. If specified, the qual value is ignored. qual Qualification criteria for a search operation. If specified, the mode value is ignored. URLs with parameters for accessing forms and search results The following examples show the URL syntax for accessing forms and search results. In these examples, arsys is used as the default context path. Example 1: URL that bypasses the Login window and displays the specified form http://midTierServer/arsys/servlet/ViewFormServlet?form=formName &server=serverName&username=userName&pwd=password WARNING If you use the pwd parameter in a URL, passwords are exposed by the browser in the locator and in bookmarks or favorites. For URLs that include the pwd parameter, use https://. Example 2: URL that displays search results in the specified form http://midTierServer/arsys/servlet/ViewFormServlet?form=formName &server=serverName&qual=%27Assigned+To%27%3D%22firstName+ lastName%22+AND+%27Status%27%3D%22Fixed%22 After the user logs in, the system displays the form with results of the following search: 'Assigned To'="Firstname Lastname" AND 'Status'="Fixed" URL-encoded string Search, Submit URL-encoded string representing the request ID number URL-encoded search string (size restricted by URL length) username User name used to log in to AR System. URL-encoded string pwd Password used to log in to AR System. URL-encoded string auth Authentication string for the user. See the Configuration Guide, “Setting up an authentication alias,” page 76. URL-encoded string Chapter 3 Working with applications that will be viewed in a browser 79
Page 1 and 2:
BMC Remedy Action Request System 7.
Page 3 and 4:
Customer Support You can obtain tec
Page 5 and 6:
Contents Preface 11 Audience . . .
Page 7 and 8:
Deleting report definitions. . . .
Page 9 and 10:
Appendix F Mid tier caching best pr
Page 11 and 12:
Preface Audience IMPORTANT The comp
Page 13 and 14:
Release Notes Information about new
Page 15 and 16:
Chapter 1 Configuring the mid tier
Page 17 and 18:
Configuring the external firewall C
Page 19 and 20:
Accessing the Mid Tier Configuratio
Page 21 and 22:
Table 1-1: Overview settings (Conti
Page 23 and 24:
Table 1-2: General settings General
Page 25 and 26:
Table 1-2: General settings (Contin
Page 27 and 28: Table 1-3: AR Server settings Figur
Page 29 and 30: 1 In the Mid Tier Configuration Too
Page 31 and 32: Table 1-4: Cache settings (Continue
Page 33 and 34: Persistent Cache option Cache setti
Page 35 and 36: Cache settings How the prefetch pro
Page 37 and 38: Cache settings arsystem.ehcache.re
Page 39 and 40: Table 1-5: Maximum number of elemen
Page 41 and 42: User and group permissions for pref
Page 43 and 44: Table 1-6: Report settings Setting
Page 45 and 46: Connection settings Connection sett
Page 47 and 48: Connection Pool Status Table 1-9: C
Page 49 and 50: Logging Table 1-10: Log settings (S
Page 51 and 52: View logs Activate profiling Change
Page 53 and 54: Real Number field Decimal Number f
Page 55 and 56: Chapter 2 Customizing AR System sty
Page 57 and 58: Order of precedence Overview of CSS
Page 59 and 60: Table 2-1: Style sheets used in AR
Page 61 and 62: Figure 2-2: Associating a customize
Page 63 and 64: Figure 2-3: Customized style for bo
Page 65 and 66: Chapter 3 Working with applications
Page 67 and 68: Click this arrow to hide the toolba
Page 69 and 70: Header text Customizing views for f
Page 71 and 72: Table 3-1: Form Action fields (Shee
Page 73 and 74: Customizing views for forms in brow
Page 75 and 76: Figure 3-5: Application Properties
Page 77: URLs for forms and applications As
Page 81 and 82: Figure 3-6: URL encoder utility 1 O
Page 83 and 84: URLs for forms and applications The
Page 85 and 86: URLs for forms and applications 6 C
Page 87 and 88: Using the Object List Using the Obj
Page 89 and 90: How a view is selected For the mid
Page 91 and 92: Including parameters in saved or de
Page 93 and 94: Form help text Field help text Figu
Page 95 and 96: Chapter 4 Configuring AR System for
Page 97 and 98: Figure 4-2: Designing a report Abou
Page 99 and 100: Managing reports with the Report fo
Page 101 and 102: Report form fields used by applicat
Page 103 and 104: Running a report by using an Open W
Page 105 and 106: Managing localized Crystal and Web
Page 107 and 108: Managing localized Crystal and Web
Page 109 and 110: Defining report types Defining repo
Page 111 and 112: Recommended entries Table 4-4: Run
Page 113 and 114: Setting limits on reports that user
Page 115 and 116: Chapter 5 Using Crystal reports wit
Page 117 and 118: Mid tier installation options for C
Page 119 and 120: Configuring BusinessObjects Enterpr
Page 121 and 122: Report definitions for Crystal repo
Page 123 and 124: ODBC driver configuration for Cryst
Page 125 and 126: Crystal Reports tips for the Web 8
Page 127 and 128: Appendix A For your end users: Tips
Page 129 and 130:
Creating requests To restore the f
Page 131 and 132:
Creating requests NOTE The rich-tex
Page 133 and 134:
3 Complete the following fields: 4
Page 135 and 136:
How the Back button behaves How the
Page 137 and 138:
Appendix B For your end users: Runn
Page 139 and 140:
Finding a request by example Param
Page 141 and 142:
Finding a request by example For ex
Page 143 and 144:
1 Click the Advanced Search button
Page 145 and 146:
Table B-3: Keywords (Sheet 2 of 3)
Page 147 and 148:
Values Using the advanced search ba
Page 149 and 150:
Table B-4: Operators (Sheet 3 of 3)
Page 151 and 152:
Saving searches To find all request
Page 153 and 154:
Loading search criteria without exe
Page 155 and 156:
Appendix C For your end users: Crea
Page 157 and 158:
“Adding to or overriding a report
Page 159 and 160:
Running reports Finding reports Run
Page 161 and 162:
Running reports TIP Although you ca
Page 163 and 164:
Exporting AR System reports Running
Page 165 and 166:
Restrictions on modifying queries a
Page 167 and 168:
3 Delete, disable, or enable report
Page 169 and 170:
Figure C-4: Example list report bas
Page 171 and 172:
Creating reports For example, a tub
Page 173 and 174:
Creating reports Minimum—Shows t
Page 175 and 176:
Using the advanced query builder Cr
Page 177 and 178:
1 Select the report in the Report C
Page 179 and 180:
Creating reports Entries that are s
Page 181 and 182:
Creating reports You can use text,
Page 183 and 184:
Export file formats for AR System r
Page 185 and 186:
Appendix D For your end users: Usin
Page 187 and 188:
Drilling down to information in fla
Page 189 and 190:
Appendix E ITSM 7.0.00 applications
Page 191 and 192:
Appendix F Mid tier caching best pr
Page 193 and 194:
Use the following steps to disable
Page 195 and 196:
3 Select the Pre-Load checkbox next
Page 197 and 198:
Create, modify, or delete a form C
Page 199 and 200:
Index A A B C D E F G H I J K L M N
Page 201 and 202:
J A B C D E F G H I J K L M N O P Q
Page 203 and 204:
A B C D E F G H I J K L M N O P Q R
Page 206:
**183971** **183971** **183971** **
show all

BMC Remedy Action Request System 7.6.04: BMC Remedy Mid Tier ...

Create successful ePaper yourself

Delete template?

Save as template?