MicroStrategy Narrowcast Server

Transcription

1 Microtrategy arrowcast erver ystem Administrator Guide Version 9.3.1

2 wenty-fifth dition, version o ensure that you are using the documentation that corresponds to the software you are licensed to use, compare this version number with the software version shown in About Microtrategy... in the Help menu of your software. Document number: opyright by Microtrategy ncorporated. All rights reserved. f you have not executed a written or electronic agreement with Microtrategy or any authorized Microtrategy distributor, the following terms apply: his software and documentation are the proprietary and confidential information of Microtrategy ncorporated and may not be provided to any other person. opyright by Microtrategy ncorporated. All rights reserved. H FWAR AD DUMA AR RVDD A AD WHU XR R LMD WARRAY F AY KD BY HR MRRAGY RRAD R AY WH HA B VLVD H RA, RDU, R DRBU F H FWAR R DUMA, LUDG, BU LMD, H MLD WARRA F MRHAABLY AD F FR A ARULAR UR, GD L AD FRGM, QUALY R AURAY. H R RK A H QUALY AD RFRMA F H FWAR AD DUMA WH YU. HULD H FWAR R DUMA RV DFV, YU (AD MRRAGY,. R AY L WH HA B VLVD WH H RA, RDU, R DRBU F H FWAR R DUMA) AUM H R F ALL ARY RVG, RAR, R RR. M A D ALLW H XLU F MLD WARRA, H ABV XLU MAY ALY YU. n no event will Microtrategy, nc. or any other person involved with the creation, production, or distribution of the oftware be liable to you on account of any claim for damage, including any lost profits, lost savings, or other special, incidental, consequential, or exemplary damages, including but not limited to any damages assessed against or paid by you to any third party, arising from the use, inability to use, quality, or performance of such oftware and Documentation, even if Microtrategy, nc. or any such other person or entity has been advised of the possibility of such damages, or for the claim by any other party. n addition, Microtrategy, nc. or any other person involved in the creation, production, or distribution of the oftware shall not be liable for any claim by you or any other party for damages arising from the use, inability to use, quality, or performance of such oftware and Documentation, based upon principles of contract warranty, negligence, strict liability for the negligence of indemnity or contribution, the failure of any remedy to achieve its essential purpose, or otherwise. he entire liability of Microtrategy, nc. and your exclusive remedy shall not exceed, at the option of Microtrategy, nc., either a full refund of the price paid, or replacement of the oftware. o oral or written information given out expands the liability of Microtrategy, nc. beyond that specified in the above limitation of liability. ome states do not allow the limitation or exclusion of liability for incidental or consequential damages, so the above limitation may not apply to you. he information contained in this manual (the Documentation) and the oftware are copyrighted and all rights are reserved by Microtrategy, nc. Microtrategy, nc. reserves the right to make periodic modifications to the oftware or the Documentation without obligation to notify any person or entity of such revision. opying, duplicating, selling, or otherwise distributing any part of the oftware or Documentation without prior written consent of an authorized representative of Microtrategy, nc. are prohibited. U.. Government Restricted Rights. t is acknowledged that the oftware and Documentation were developed at private expense, that no part is public domain, and that the oftware and Documentation are ommercial omputer oftware provided with RRD RGH under Federal Acquisition Regulations and agency supplements to them. Use, duplication, or disclosure by the U.. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in echnical Data and omputer oftware clause at DFAR et. seq. or subparagraphs (c)(1) and (2) of the ommercial omputer oftware Restricted Rights at FAR , as applicable. ontractor is Microtrategy, nc., 1850 owers rescent laza, Vienna, VA Rights are reserved under copyright laws of the United tates with respect to unpublished portions of the oftware. he following are either trademarks or registered trademarks of Microtrategy ncorporated in the United tates and certain other countries: Microtrategy, Microtrategy 6, Microtrategy 7, Microtrategy 7i, Microtrategy 7i valuation dition, Microtrategy 7i lap ervices, Microtrategy 8, Microtrategy 9, Microtrategy Distribution ervices, Microtrategy Multiource ption, Microtrategy ommand Manager, Microtrategy nterprise Manager, Microtrategy bject Manager, Microtrategy Reporting uite, Microtrategy ower User, Microtrategy Analyst, Microtrategy onsumer, Microtrategy mail Delivery, Microtrategy B Author, Microtrategy B Modeler, Microtrategy valuation dition, Microtrategy Administrator, Microtrategy Agent, Microtrategy Architect, Microtrategy B Developer Kit, Microtrategy Broadcast erver, Microtrategy Broadcaster, Microtrategy Broadcaster erver, Microtrategy Business ntelligence latform, Microtrategy onsulting, Microtrategy RM Applications, Microtrategy ustomer Analyzer, Microtrategy Desktop, Microtrategy Desktop Analyst, Microtrategy Desktop Designer, Microtrategy erm 7, Microtrategy ducation, Microtrategy erainer, Microtrategy xecutive, Microtrategy nfocenter, Microtrategy ntelligence erver, Microtrategy ntelligence erver Universal dition, Microtrategy MDX Adapter, Microtrategy arrowcast erver, ii

3 Microtrategy bjects, Microtrategy LA rovider, Microtrategy DK, Microtrategy upport, Microtrategy elecaster, Microtrategy ransactor, Microtrategy Web, Microtrategy Web Business Analyzer, Microtrategy World, Application Development and ophisticated Analysis, Best n Business ntelligence, entralized Application Management, nformation Like Water, ntelligence hrough very hone, ntelligence o very Decision Maker, ntelligent -Business, ersonalized ntelligence ortal, Query one, Rapid Application Development, Microtrategy ntelligent ubes, he Foundation For ntelligent -Business, he ntegrated Business ntelligence latform Built For he nterprise, he latform For ntelligent -Business, he calable Business ntelligence latform Built For he nternet, ffice ntelligence, Microtrategy ffice, Microtrategy Report ervices, Microtrategy Web MM, Microtrategy Web ervices, ixel erfect, ixel-erfect, Microtrategy Mobile, Microtrategy ntegrity Manager and Microtrategy Data Mining ervices are all registered trademarks or trademarks of Microtrategy ncorporated. All other company and product names may be trademarks of the respective companies with which they are associated. pecifications subject to change without notice. Microtrategy is not responsible for errors or omissions. Microtrategy makes no warranties or commitments concerning the availability of future products or versions that may be planned or under development. atent nformation his product is patented. ne or more of the following patents may apply to the product sold herein: U.. atent os. 6,154,766, 6,173,310, 6,260,050, 6,263,051, 6,269,393, 6,279,033, 6,567,796, 6,587,547, 6,606,596, 6,658,093, 6,658,432, 6,662,195, 6,671,715, 6,691,100, 6,694,316, 6,697,808, 6,704,723, 6,741,980, 6,765,997, 6,768,788, 6,772,137, 6,788,768, 6,798,867, 6,801,910, 6,820,073, 6,829,334, 6,836,537, 6,850,603, 6,859,798, 6,873,693, 6,885,734, 6,940,953, 6,964,012, 6,977,992, 6,996,568, 6,996,569, 7,003,512, 7,010,518, 7,016,480, 7,020,251, 7,039,165, 7,082,422, 7,113,993, 7,127,403, 7,174,349, 7,181,417, 7,194,457, 7,197,461, 7,228,303, 7,260,577, 7,266,181, 7,272,212, 7,302,639, 7,324,942, 7,330,847, 7,340,040, 7,356,758, 7,356,840, 7,415,438, 7,428,302, 7,430,562, 7,440,898, 7,486,780, 7,509,671, 7,516,181, 7,559,048, 7,574,376, 7,617,201, 7,725,811, 7,801,967, 7,836,178, 7,861,161, 7,861,253, 7,881,443, 7,925,616, 7,945,584, 7,970,782, 8,005,870, 8,051,168, 8,051,369, 8,094,788, 8,130,918, and 8,296,287. ther patent applications are pending. Various Microtrategy products contain the copyrighted technology of third parties. his product may contain one or more of the following copyrighted technologies: Graph Generation ngine opyright hree D Graphics, nc. All rights reserved. Actuate Formula ne. opyright Actuate orporation. All rights reserved. XML parser opyright Microsoft orporation. All rights reserved. Xalan XL processor. opyright he Apache oftware Foundation. All rights reserved. Xerces XML parser. opyright he Apache oftware Foundation. All rights reserved. F XL formatting objects. opyright he Apache oftware Foundation. All rights reserved. ortions of ntelligence erver memory management opyright ompuware orporation. All rights reserved. AHRequest library. opyright , All-eeing nteractive. All rights reserved. his product includes software developed by the penl roject for use in the penl oolkit. ( nternational omponents for Unicode opyright ompaq omputer orporation opyright Hewlett-ackard ompany opyright BM orporation opyright Hummingbird ommunications Ltd. opyright ilicon Graphics, nc. opyright un Microsystems, nc. opyright he pen Group All rights reserved. Real layer and RealJukebox are included under license from Real etworks, nc. opyright All rights reserved. iii

4 iv

5 ontents ystem Administrator verview xv About Microtrategy arrowcast erver xv arrowcast Administrator xvi Delivery ngine xvi ubscription ortal system xvi verview of system administrator tasks xvii rganization of this manual xviii Reference materials xviii ystem administrator task flow xviii ection ystem Administrator oncepts 1 hapter 1 Microtrategy arrowcast erver architecture 3 About the arrowcast erver system 3 ystem administrator responsibilities 4 ystem creation and identification 4 Best practices for folder use and maintenance 5 About the Delivery ngine 5 About the ubscription ortal 6 Administration objects 6 ubscription Book 6 Distribution managers 8 xecution engines 9 Microtrategy Logging erver and lients 11 nformation source modules and information sources 12 Document formatting modules and document formatters 21 nformation transmission modules (Ms) and information transmitters (s) 22 Devices 25 Locales and internationalization 25 Administrative accounts 30 Unverified administrative accounts 31 Application objects 32 ortal objects 32 ubscription ortal web server 32 nformation repositories 33 bject Repository 33 ubscription Book Repository 34 ortal Repository 35 hapter 2 stablishing upporting Resources 37 ervers required 37 v

6 Windows domain controllers 37 Domain name system servers 38 W servers 38 Relational database management systems 39 mart hosts/mail transfer agents (optional) 40 nternet proxy servers/wlb servers (optional) 40 Microtrategy ntelligence erver 41 ollocated services 41 etwork bandwidth, topology, and firewalls 42 stimating bandwidth requirements 42 etwork topology 42 High availability 43 Firewalls 43 nternet domain 44 Additional resources 44 hapter 3 onfiguring Machines 47 Hardware configuration 47 oftware configuration 50 lustering 52 Delivery ngine subsystem 53 ubscription ortal subsystem 59 Workload distribution in a cluster 59 U affinity 60 Failure recovery 61 egment failure 62 xecution engine failure 62 Distribution manager failure 62 etting up arrowcast erver for transmission 63 Direct mode 63 mart host mode 64 Device settings 64 esting M connectivity 65 etting up arrowcast erver for file transmission 71 Defining file delivery locations 71 Dynamically generating file or folder names: Macros 73 ontrolling device default settings 73 nabling users to define file delivery options 73 Defining file delivery location and settings: Addresses 74 Windows authentication and file transmission 74 etting up arrowcast erver for printing 75 Delivery location definition 75 ontrolling device default settings 77 nabling users to define printer locations 77 Defining printer delivery location and settings: Addresses 78 vi ontents

7 Windows authentication and printing 78 etting up arrowcast erver for text (M) transmission 78 onfiguring the Microtrategy Logging erver 80 Microtrategy Logging lient operation 81 Microtrategy Logging erver operation 82 Microtrategy Logging Module operation 82 Microtrategy Database Logger 85 Microtrategy Distributed Logger 86 Logging levels 87 hapter 4 Administering ystems 91 Recording transmission information 91 ending notification for file and print delivery 99 pecifying document creation options 101 Administering multiple systems 102 Maintaining separate environments 102 Migrating objects between systems 103 Migrating objects with dependencies 104 Repeated object migration 105 Migration scenarios 105 Using scenarios to prevent errors 107 Migration and folder structures 108 reating and restoring versions 109 ontrolling and monitoring multiple systems 110 Viewing system messages 111 etting the administrative notification 111 uning the Delivery ngine 112 Minimize report size 113 Reduce report count 113 ptimize system workload capacity 113 ontrol memory consumption 114 ptimize execution cycles 114 pecify queue sizes for segmentation 115 Maintaining arrowcast erver systems 118 Log files 118 Repository databases 119 opying Repositories 119 Using ommand Manager to automate key processes 120 ommand Manager support for Microtrategy ntelligence erver 120 ommand Manager support for arrowcast erver 121 Using ommand Manager 121 tatement syntax for arrowcast erver 123 Refreshing imported files 129 ontents vii

8 ection ystem Administrator nterfaces 131 hapter 5 Add arrowcast erver Administrative Accounts Dialog Box 133 Add arrowcast erver Administrative Accounts dialog box layout 133 hapter 6 Administrative otification Dialog Box 135 Administrative otification dialog box layout 136 Administrative otification Request dialog box 137 hapter 7 Assign Administrative rivileges to Account Dialog Box 139 Assign Administrative rivileges to Account dialog box layout 140 hapter 8 onfigure bject Management Dialog Box 141 onfigure bject Management dialog box layout 141 hapter 9 onflict Resolution Dialog Box 145 onflict Resolution dialog box layout 145 hapter 10 Device ditor 149 Device ditor layout 149 elect nformation ransmitter dialog box 151 ransmission tab 151 laintext tab 159 xcel tab 159 HML tab 159 DF tab 159 hapter 11 Distribution Manager onfiguration Dialog Box 161 Distribution Manager onfiguration dialog box layout 162 hapter 12 Document Formatter - xcel Dialog Box 163 Document Formatter - xcel dialog box layout 163 hapter 13 dit Available User roperties Dialog Box 165 dit Available User roperties dialog box layout 165 hapter 14 xecution ngine onfiguration Dialog Box 167 xecution ngine onfiguration dialog box layout 168 viii ontents

9 hapter 15 nformation ource Wizard 169 nformation ource Wizard layout 170 nformation ource dialog box 170 Welcome 171 ntelligence erver 171 Microtrategy ntelligence erver roperties dialog box 171 roject dialog box 175 Advanced roperties dialog box 175 Default Language 176 Default Authentication 176 ecurity and Dynamic ubscription upport 176 Default ecurity 177 rompt Resolution dialog box 177 User and ubscription roperties 178 Address roperties 179 ersonalization 181 ummary 182 ave nformation ource dialog box 182 hapter 16 et 183 nformation ransmission Module Dialog nformation ransmission Module dialog set layout 183 Register nformation ransmitter dialog box 184 -mail (M) 184 Wireless (M) 186 M (M) 188 Web (ortal) 189 hapter 17 Locale ditor 191 Locale ditor layout 191 hapter 18 pen Device File for mport Dialog Box 193 pen Device File for mport dialog box layout 193 hapter 19 Register Document Formatter Dialog Box 195 Register Document Formatter dialog box layout 195 hapter 20 Register nformation ource Module Dialog Box 197 Register nformation ource Module dialog box layout 197 hapter 21 Register ubscription Book Module Dialog Box 199 Register ubscription Book Module dialog box layout 199 ontents ix

10 hapter 22 Repository opy Dialog Box 201 Repository opy dialog box layout 201 bject Repository page 202 ubscription Book Repository page 202 ummary page 203 hapter 23 ystem Message Viewer Dialog Box 205 ystem Message Viewer dialog box layout 206 elect Message ypes dialog box 207 Log governing dialog box 209 Log formats dialog box 210 Log filtering dialog box 210 hapter 24 ystem ettings Dialog Box 211 ystem ettings dialog box layout 211 Distribution Manager tab 212 xecution tab 212 onsole tab 213 Recording tab 213 Document reation tab 213 ection ystem Administrator How Do...? 215 hapter 25 Managing Administrator Accounts 217 Add a login D to the local administrators group for Windows Workstation 217 Add a login D to the local administrators group for Windows Add an account 219 Assign privileges to an account 220 Remove an account 220 Remove privileges from an account 221 hapter 26 opying and Restoring bjects 223 opy objects to another system for backup/restore purposes 223 Restore all objects from a backup system 223 Restore a single object from a backup system 224 Revert the objects in one environment to the older object definitions from another environment 224 Update the objects in one environment with the new object definitions from another environment 225 hapter 27 Managing Distribution Managers 227 Add a distribution manager 227 Delete a distribution manager 227 x ontents

11 Run a distribution manager 228 top a distribution manager 228 hapter 28 Working with Document Formatters 229 Delete a document formatter 229 Register a document formatter 229 et the properties of an xcel document formatter 230 hapter 29 Managing xecution ngines 231 Add an execution engine 231 Delete an execution engine 231 dle an execution engine 232 Run an execution engine 232 top an execution engine 232 hapter 30 onfiguring nformation ransmitters 233 Allow users to specify file paths where their files should be saved 233 Allow users to specify printer locations where their services should be printed 234 reate a File device 234 reate an -mail (M) or Wireless (M) device 236 reate an M (M) device 238 reate a rint device 239 reate a Web (ortal) device 241 Delete a device 241 Delete an information transmitter 242 mport devices from a device library 242 Register an information transmitter 243 rint documents on printers within my network 243 et the properties of an -mail (M) information transmitter 244 et the properties of an M (M) information transmitter 246 et the properties of a Web (ortal) information transmitter 246 et up xcel properties for a device 247 et up HML properties for a device 247 et up DF properties for a device 247 et up plain text properties for a device 248 hapter 31 onfiguring nformation ource Modules 249 reate a Microtrategy nformation ource 249 Delete an information source 252 Delete an information source module 252 Register an information source module 253 hapter 32 reating Locales 255 reate a locale 255 Delete a locale 256 ontents xi

12 hapter 33 onfiguring a arrowcast erver ystem 257 Apply system governing settings 257 lear the ystem Message Viewer 258 onnect to a system 258 opy system messages to the clipboard 259 opy object repository 259 opy subscription book repository 260 opy object repository and subscription book repository 260 Destroy a system 261 Find a string in the system message 262 Filter the system messages 262 Migrate an object from one system (repository) to another 263 Modify the Microtrategy Logging erver configuration 263 Modify transmission properties regarding address display 264 Register a new ubscription Book Module 264 Remove all system components from a computer 265 Resolve conflicts related to object management 265 ave the system messages 266 ecure the bject Repository 266 ecure the ubscription Book Repository 267 elect the logging format for system messages 267 end notification for file and print delivery 268 et the administrative notification 268 et governing for system messages 269 et message types for system messages 270 pecify document creation options 270 pecify the rules for object management 271 tart the arrowcast erver system 271 top the arrowcast erver system 272 urn transmission recording on 272 urn transmission recording off 272 View system messages 273 ection V ystem Administrator Appendixes 275 Appendix A xecutable Files 277 Appendix B Language upport 279 Appendix arrowcast erver rror odes 281 Distribution Manager 281 egment xecutor 310 xecution ngine 325 nformation ource Module 331 xii ontents

13 nformation ransmission Module 331 Appendix D arrowcast erver ecurity 333 Microtrategy arrowcast erver M transmitter through network firewall 333 upported security measures 334 ecurity with Microsoft 334 Account privileges 334 ryptography 335 ubscription ortal subsystem 335 Distributed omponent bject Model 335 Remote Method nvocations 336 ample configuration options 336 onfiguration A: All components on one server 336 onfiguration B: ypical nstallation 337 onfiguration : nterprise dition using Windows load balancing 337 Appendix arrowcast erver Windows ervices 339 Appendix F erver 341 ervice xecution Flow in arrowcast ervice triggered and inserted into queue 341 Highest priority service selected, recipients per segment determined 342 ubscription et Ds and segment size passed to ubscription Book Module 342 egments created and information passed to distribution manager 343 egment assigned to execution engine and information provided 344 egment executor initialized and information sources identified 344 egment definition sent to ubscription Book Module to retrieve recipients 345 Recipient list sent to segment executor and analyzed 346 tep 1. nitialize transmitter 346 tep 2. nitialize formatters 347 tep 3: erform personalization bucketing 347 tep 4: egment executor sends information object request to information source module 350 Appendix G roubleshooting 353 roubleshooting tools 353 ystem Message Viewer 353 ortal Administrator error log 354 Log files 354 Monitor 354 ystem creation 354 tarting the Delivery ngine 356 ervice creation and execution 359 ubscription administration 371 -mail (M) 374 ontents xiii

14 rinting 379 nformation ource Module 380 HML Document ditor 380 ortal Administrator 381 Licensing errors 383 rror messages 383 rinting 384 aving to file 387 ection V ndex 389 xiv ontents

15 RDU ystem Administrator verview his manual provides arrowcast erver system administrators with information and steps to administer a Microtrategy arrowcast erver system. About Microtrategy arrowcast erver Microtrategy arrowcast erver is an information delivery platform designed for proactive transmission of information in the form of personalized messages. Microtrategy arrowcast erver includes a Delivery ngine that can: Gather information from any source (such as Microtrategy ntelligence erver, the web, directly from databases, from flat files, and so on) through an open ervice rovider nterface ersonalize the information gathered based on individual characteristics and preferences Format the information into text, HML, and Microsoft xcel documents Deliver the information via any channel such as , M, or a web portal, through an open ervice rovider nterface arrowcast erver comprises the following technical feature groups: arrowcast Administrator Delivery ngine ubscription ortal system arrowcast erver includes a ubscription ortal through which end users can specify their preferences and choose what types of information they would like to receive. arrowcast erver nterprise dition clusters across multiple machines to scale with available resources and provide failover support. arrowcast erver also implements a modular architecture where modules can be added or removed as needed to provide different means of gathering, xv

16 formatting, and delivering information. For example, alert information can be gathered directly from a database and delivered wirelessly via M, or content can be gathered from different websites, combined and reformatted, and delivered via HML or posted back to the web. Delivered information can be personalized based on specific individual preferences. arrowcast erver is an adaptable, scalable, robust platform for information subscription, gathering, processing, personalization, and delivery. arrowcast Administrator arrowcast Administrator provides a unified console through which arrowcast erver systems can be developed, controlled, and administered. t can be used on several machines at the same time for a single system, to facilitate rapid development and distributed deployment. arrowcast Administrator presents an easy-to-use interface for creating information delivery services and for administering a distributed arrowcast erver system. Delivery ngine he Delivery ngine is responsible for the content gathering, formatting, and transmission for information delivery services. ts open architecture is component-based to allow integration with custom data sources, formatting methods, transmission technologies, and directory management systems. he Delivery ngine can be administered remotely and can be clustered easily, providing workload distribution as well as automatic failover and recovery. With the addition of locale and time zone awareness, the Delivery ngine easily supports a multinational user community. he Delivery ngine provides the information delivery capabilities of a arrowcast erver system. ubscription ortal system Users control the content they receive by specifying what information they want to see using the ubscription ortal system. hrough the web-based portal, users determine the frequency, schedule, delivery device, and personalization of information services. arrowcast erver ensures that xvi ystem Administrator verview

17 individuals receive one-to-one, personalized information where and when it is most useful. he ubscription ortal system includes the following: ortal Administrator Wizard: he ortal Administrator Wizard provides a web-based interface through which a system can be configured and administered. his wizard allows the portal administrator to specify which arrowcast erver services are deployed in the ubscription ortal. ubscription ortal: ach ubscription ortal offers users the ability to view services and any arrowcast documents generated by arrowcast erver. Users can also administer user passwords and preferences, addresses, and subscriptions. Users can change schedules for their subscriptions and save preferences for future use. he ubscription ortal system provides the subscription and personalization capabilities of a arrowcast erver system. For more information about understanding the functionality of the ubscription ortal system see User elf ubscription in the arrowcast Application Designer Guide. verview of system administrator tasks ystem administrator tasks include installing and configuring all of the components of the arrowcast erver system. hey also include monitoring system performance, maintaining the system environment, tuning the system configuration, and troubleshooting problems. he full list of tasks are described below: lan your arrowcast system onfigure machines nstall software reate/configure a arrowcast erver system est the configuration Migrate administration objects Migrate application objects erform maintenance Upgrade the system Monitor the system roubleshoot the system upport a development and production environment verview of system administrator tasks xvii

18 nsure 7x24 operations erform error recovery rganization of this manual he information in this guide is divided into the following sections: oncepts: rovides information about product components and features. nterfaces: rovides interface-specific information. xplains the interfaces used to administer your arrowcast system. How Do...?: rovides steps to perform administrative tasks. he roubleshooting section at the end of the guide briefs you about the troubleshooting tools that are useful to resolve any errors related to arrowcast erver. Reference materials Before you begin any administration tasks, read the Microtrategy arrowcast erver Getting tarted Guide, which introduces the functionality of Microtrategy arrowcast erver. he Getting tarted Guide also provides basic terminology and information resources that can help you use the software and other manuals. ystem administrator task flow Many of the basic system administrator tasks are part of the ystem onfiguration Wizard, which is detailed in the arrowcast erver nstallation and onfiguration Guide. ortal administration tasks are described in the arrowcast erver Application Designer Guide. he following list describes more advanced configuration tasks. ask How Do... hapter 1. Add or remove a distribution manager. Managing Distribution Managers 2. Add a new arrowcast Administrator account. Managing Administrator Accounts 3. Add or remove an execution engine. Managing xecution ngines xviii ystem Administrator verview

19 ask How Do... hapter 4. hange system governing settings. Apply system governing settings 5. reate, modify, or delete a device. onfiguring nformation ransmitters 6. reate, modify, or delete an information source. onfiguring nformation ource Modules 7. reate, modify, or delete a locale reating Locales 8. Register an information source module. onfiguring nformation ource Modules 9. reate, modify, or delete a document formatter. Working with Document Formatters 10. reate, modify, or delete an information transmitter. 11. tart or stop an individual distribution manager and scheduler. onfiguring nformation ransmitters Managing Distribution Managers 12. tart or stop an execution engine. Managing xecution ngines 13. tart the arrowcast erver system. onfiguring a arrowcast erver ystem 14. et the administrative notification. onfiguring a arrowcast erver ystem ystem administrator task flow xix

20 xx ystem Administrator verview

21 ystem Administrator oncepts 1

22 2 ection ystem Administrator oncepts

23 1 architecture HAR 1 1.Microtrategy arrowcast erver his chapter explains how the architecture and object model of arrowcast erver enable the features and benefits described in the arrowcast erver Getting tarted Guide. his chapter explains how each of the administration objects impacts the behavior of a arrowcast erver system and what a system can do. About the arrowcast erver system A arrowcast erver system is a computer application that generates and delivers personalized messages containing analytical content to subscribers. t provides a web-based interface so that recipients can control which messages they get, how often, with what content, and through what technology medium. he arrowcast erver system is composed of a collection of machines (hardware), components (software) and objects (data). he machines use the components to process the objects. A arrowcast erver system includes two major components: the Delivery ngine and the ubscription ortal. he objects that make up a system are divided into three categories: Administration objects: hese objects define the architecture, or hardware and software configuration, that arrowcast erver uses to generate and deliver personalized messages, and to provide a web site to recipients for subscription administration. hese objects specify where and how recipient data is acquired and stored, and how content is retrieved, formatted, and transmitted. hese objects are created and configured by the system administrator, and are stored in the Administration folder in arrowcast Administrator. ertain components and administration objects can be set up to exist on two or more machines in a clustered machine configuration, although you can run the entire system on one machine. For more information about clustering, see lustering. 3

24 Application objects: hese objects define the generation frequency, content, and personalization of the messages produced by the system for recipients. At the highest level, an application object called a service defines what end users can subscribe to. he definition of a service is based upon a set of other objects that control when the service is executed to generate messages (schedules), what content is produced in those messages (publications), and which end user addresses receive the messages (subscription sets). hese objects are stored in the Applications folder in arrowcast Administrator. For more information on creating services and other application objects, see the arrowcast erver Application Designer Guide. ortal objects: hese objects define the appearance and behavior of the ubscription ortal for end users. hese objects also specify the hardware locations of the components that comprise the ubscription ortal. For more information on creating portal objects, see the arrowcast erver Application Designer Guide. ystem administrator responsibilities ystem administrators for arrowcast erver systems typically perform the following: rovide and maintain a usable network environment. his includes ensuring that the right network configuration, system resources such as relational databases and web servers, and security controls are in place. Define the arrowcast erver architecture and configuration. he ystem onfiguration Wizard in arrowcast Administrator guides you through setting up and registering your system, and creating and configuring the administration objects needed to support the system. Grant system access to other arrowcast Administrator users such as subscription administrators and application designers. Monitor and maintain the system to ensure correct, efficient operation. he information you need to fulfill these responsibilities is provided in this guide. ystem creation and identification You can create arrowcast erver systems using the ystem onfiguration Wizard, and through the utorial configuration process which is outlined in the arrowcast erver nstallation and onfiguration Guide. When a new arrowcast erver system is created, several tables are created in the specified bject Repository database. n addition, a number of sample services are added to the arrowcast erver system if the 4 hapter 1 Microtrategy arrowcast erver architecture

25 Microtrategy utorial for arrowcast erver has been installed. Finally, the system is given a name so that it can be easily identified and recognized. A arrowcast erver system name is used to identify a system once it has been registered. his name is displayed in arrowcast Administrator as the root in the Location box and in the Folder List pane. When registering a system during system configuration, if an existing system is chosen, the system is presented using the system prefix. For this reason, it is important to record arrowcast erver systems by both the system name and the system prefix specified when the bject Repository is created. his enables you to identify each system later when you register it using the ystem onfiguration Wizard. Best practices for folder use and maintenance When working with device and application folders, it is important to consider the impact that creating new folders and saving objects to various folders can have on your application. Use a folder structure that makes it easy for you and other users to find the objects you create. f a folder is published on a ubscription ortal site as a channel, any services or folders that you create inside that folder are also shown automatically on the ubscription ortal. f a device folder is selected for a device type using the ortal Administration Wizard, and you add a device to that folder, that device is available automatically on the ubscription ortal. About the Delivery ngine A Delivery ngine generates and delivers personalized messages with analytical content to recipients. t is composed of a collection of machines, components, and objects. ystem administrators administer the administration objects that the Delivery ngine needs for proper operation, and specify the hardware used by distribution managers, execution engines, and the Microtrategy Logging erver. hey also administer the hardware on which the Delivery ngine software runs. About the Delivery ngine 5

26 About the ubscription ortal A ubscription ortal is the portion of a arrowcast erver system that provides a website for end users to administer their addresses, preferences, and subscriptions. t is a collection of machines, components, and objects. hese objects control how the website behaves when users interact with the ubscription ortal. ortal objects reside in the ortal Repository and are manipulated with the ortal Administrator Wizard. For more information about understanding the functionality of the ubscription ortal, see User elf ubscription in the arrowcast Application Designer Guide. ystem administrators typically maintain the administration objects that the ubscription ortal needs for proper operation, and specify the hardware used by the ubscription ortal website. Administrators also maintain the hardware on which the ubscription ortal software runs. Administration objects Administration objects are the components of a arrowcast erver system that control system capabilities such as specifying what hardware the system uses, where system information is stored, how and from where content information is retrieved, how content information is transformed into messages, and how those messages are transmitted to recipients. ubscription Book he ubscription Book is an administration object that contains all the users, addresses, and subscriptions for the arrowcast erver system. t is stored in the ubscription Book Repository. 6 hapter 1 Microtrategy arrowcast erver architecture

27 he ubscription Book performs the following tasks when processing a arrowcast service: Divides the set of subscriptions to a service, called a subscription set, into segments for efficient processing. he number of subscriptions in each segment is called the segment size, and can be configured separately for each service from either the ervice Wizard or the ervice ditor. he Delivery ngine uses segments to control and limit the number of subscriptions that are processed simultaneously, thus ensuring that the memory resources available on an execution engine are not overwhelmed when a service with a large number of subscriptions is run. egmenting a subscription set takes place on the distribution manager machine. t involves identifying the D of the first and last subscription in each segment. Determines the subscriptions within a segment. his includes information about who will receive the service and any associated personalization instructions. his action is requested by the execution engine and takes place on the execution engine machine. nly one ubscription Book is allowed per system. You create it through the ystem onfiguration Wizard. For information about creating a ubscription Book using the ystem onfiguration Wizard on the ystem onfiguration Wizard, see ubscription Book configuration in the arrowcast erver nstallation and onfiguration Guide. More detailed information about the ubscription Book is included in the arrowcast erver Application Designer Guide. ubscription Book Module he ubscription Book is implemented as the component object model (M) component ubscription Book Module (BM). his component can be replaced by a custom component that implements the ubscriptionbook programming interface. A software developer can write such a M component and register it with arrowcast Administrator to provide a custom source for recipient information. For information about the ubscriptionbook programming interface, see the arrowcast erver DK Guide. ubscription Book Repositories When a new ubscription Book Repository is created, a number of tables with an optional prefix are created in the specified database. n addition, a number of sample users, addresses, and subscriptions are added to the ubscription Book Repository if the sample Microtrategy utorial Administration objects 7

28 project for arrowcast erver is installed. ubscription Book Repositories can be created using the ystem onfiguration Wizard or in arrowcast Administrator by right-clicking the ubscription Book icon. For more information on the configuration process, see the arrowcast erver nstallation and onfiguration Guide. For more information on the ubscription Book Repository, see ubscription Book Repository in this chapter. Distribution managers he distribution manager (DM) is the software component that controls system operations. ustomers with the nterprise dition of the software can have more than one machine running the distribution manager in a arrowcast erver system. nly one of these machines serves as the primary DM. he primary DM performs the following: Receives requests to execute services from either the Delivery ngine A or from scheduler ends the subscription set definition to the ubscription Book Module to determine the subscription D boundaries of each service segment Distributes service segments to the execution engines for execution and designates backup execution engines for failover racks the state of execution engines in the system and corrects problems caused by failed software components or hardware he primary DM constantly updates the backup DMs with its segment processing status, so that if the primary DM machine fails, one of the backup DM machines can take over processing at the point where the primary DM machine failed. After a distribution manager is started, its Windows ervice startup type is switched to automatic. When a distribution manager is stopped, its Windows ervice startup type is switched back to manual. An individual distribution manager can be started/stopped either from the Windows ervice ontrol anel or from arrowcast Administrator. arrowcast Administrator gives you the ability to start or stop the whole arrowcast erver system in addition to individual distribution managers. he ability to control a single machine is particularly useful for performing scheduled maintenance on a single distribution manager machine without disrupting system operation. he ability to control the entire system is essential for system shutdown; otherwise, a backup DM simply takes over system control when the primary DM is shut down. 8 hapter 1 Microtrategy arrowcast erver architecture

29 You can set up the distribution manager using the ystem onfiguration Wizard or the Distribution Manager onfiguration dialog box in arrowcast Administrator. o set up the distribution manager using the ystem onfiguration Wizard, see pecify Distribution Managers in the arrowcast erver nstallation and onfiguration Guide. For steps to set up the distribution manager using the Distribution Manager onfiguration dialog box, see Managing Distribution Managers xecution engines An execution engine () is a software component that controls service segment processing. he distribution manager receives the segment definitions for a service from the ubscription Book Module, then sends these and the service definition to execution engines. ach execution engine then spawns a segment executor that performs the following actions: he segment executor sends each received segment definition and the service definition to the ubscription Book Module. he ubscription Book Module then retrieves and returns the set of subscriptions within the segment. his subscription set includes the list of recipients for the segment as well as their address, subscription, and personalization information. Using the service definition and the address, subscription, and personalization information received from the ubscription Book Module, the segment executor determines what information requests need to be made to information sources to retrieve the required content for the service. he segment executor instantiates information source modules as needed, and makes requests for dynamic content to them. he segment executor receives the results from the information source modules and forwards that information to the appropriate document formatting modules. he segment executor receives the formatted content from the document formatting modules in the form of documents. he segment executor temporarily stores each personalized document until all of the subscriptions that need it have been fulfilled. When all of the documents for a particular subscription are complete, those documents are forwarded to the appropriate information transmission module where they are transmitted to the address used by that subscription. Administration objects 9

30 When each message is transmitted, the segment executor receives a message transmission notification from the information transmission module. he segment executor notifies the failover or backup execution engine that a message was sent for the related subscription, and records transmission information to the ubscription Book Repository. he segment executor notifies the distribution manager when a given segment has been processed. n a clustered environment, before an execution engine begins to process a segment, it passes a complete copy of the subscription set to its backup execution engine machine. As each personalized message is delivered, the execution engine notifies its backup execution engine of the completion status of the service execution segment, so that both execution engine machines have the most up-to-date information. his ensures that messages are not duplicated or lost if a hardware or software problem occurs on one of the execution engines in the cluster. Depending on the quantity and type of services you plan to run, your arrowcast system may require more than one execution engine machine. f your system requirements include high availability, you should use at least two execution engine machines for backup purposes. he ability to have multiple execution engine machines is available only with the nterprise dition of the software. xecution engine machines with adjacent rank numbers, for example, 1, 2, and 4, 5, should be comparable in workload capacity. his ensures that execution recording and failure recovery are relatively balanced, so that the work being performed by a machine with a higher workload capacity never has to be taken on by a machine with less capacity. he startup type of an execution engine Windows ervice should remain manual. Also, execution engines should not be started/stopped directly from the Windows ervice ontrol anel. he life cycles of the execution engines are controlled by the primary distribution manager. Because of the failure recovery technology in the product, if you attempt to shut down an execution engine using the Windows ervice ontrol anel, the primary distribution manager starts it up again. You can set up the execution engine using the ystem onfiguration Wizard or the xecution ngine onfiguration dialog box in arrowcast Administrator. o set up the execution engine using the ystem onfiguration Wizard, see pecify xecution ngine in the arrowcast erver nstallation and onfiguration Guide. For steps to set up the execution engine using the xecution ngine onfiguration dialog box, see Managing xecution ngines. 10 hapter 1 Microtrategy arrowcast erver architecture

31 Microtrategy Logging erver and lients he Microtrategy Logging erver (ML) and the Microtrategy Logging lients (MLs) capture and store logging data such as statistical data, error messages, system events, and segmentation status. Both the ML and MLs run as Windows services, under the ystem account. he MLs capture logging data from the Delivery ngine components that reside on the ML machine and relay that data to the ML machine. he ML provides the messaging infrastructure needed to collect all the information in one location and then redistribute it to consumers of that information. he ML does this through a publish and subscribe architecture, in which one or more consumers can ask for various types of information (such as errors, statistics, or status) and levels of information (such as critical, high, medium, or low). arrowcast erver includes a consumer that you can use to log this information to the Windows vent Log, a set of text log files, or the ystem Message Viewer. arrowcast erver also includes a buffer port that you can use for sending messages to the buffer. hese messages are viewed by arrowcast Administrator. o learn more about using these features with the Logging erver, see onfiguring the Microtrategy Logging erver. o learn more about how custom modules can be implemented to subscribe to the Logging erver, see Logging Module Directory in the arrowcast erver DK Guide. You can specify the ML and ML machines when you configure a arrowcast erver system using the ystem onfiguration Wizard. For steps, refer to pecify Logging erver in the arrowcast erver nstallation and onfiguration Guide. For steps to set up the execution engine using the ystem onfiguration Wizard, see lustering. All distribution manager and execution engine machines must have the ML component installed and running, which the ystem onfiguration Wizard automatically accomplishes. he arrowcast Administrator machine also requires the ML component. Administration objects 11

32 nformation source modules and information sources arrowcast erver provides an open architecture that allows information to be gathered from external sources for use in arrowcast erver services. he system component that enables gathering information from external sources is called an information source. arrowcast erver provides several out-of-the-box information sources, one of which gathers reports from Microtrategy ntelligence erver. hese reports, as well as other information objects, can be gathered from any number of sources and added to service content. When a new information source is added to a arrowcast erver system, the information source informs arrowcast erver of the kinds of information objects it can provide. his list of information objects appear in arrowcast document editors, grouped by the name of the information source. For example, the Microtrategy nformation ource provides Microtrategy grid and graph report information objects. his section explains what information source modules and information sources are and how they can be used. For information about configuring information source modules and information sources in arrowcast Administrator, see onfiguring nformation ource Modules. he information source module (M) is an interface between Microtrategy Delivery ngine software and the various data sources you can access from your arrowcast system. he M receives information requests from the ubscription Book Module and execution engine, and retrieves the requested information from the appropriate source. he M then sends the results back to the ubscription Book Module or execution engine. Microtrategy arrowcast erver comes pre-packaged with four information source modules: he Microtrategy nformation ource Module, which can get reports and documents from Microtrategy projects. he User nformation Module, which can provide personal information for each subscription such as the recipient s first name or phone number. he ubscription nformation Module, which can provide subscription information such as the physical address, subscription D, and other information used by the Delivery ngine during service execution. he ystem nformation Module, which can provide system information such as service name, service D, execution time or date. 12 hapter 1 Microtrategy arrowcast erver architecture

33 Additional information source module samples are available with the sample code and through the Microtrategy olutions website. o learn more about implementing additional information source modules, see nformation ource Module Directory in the arrowcast erver DK Guide. nformation source An information source () is an administration object that represents a specific use of an M. For example, you may have three Microtrategy projects to which you need to connect to gather data from. You can use a single M to create three information sources, one for each project. ach information source belongs to a particular M and is associated with a specific use. he M is the software component and each is a specific instance or implementation of an M. You create information sources using the ystem onfiguration Wizard or by right-clicking the desired M in arrowcast Administrator.You can also specify clustering information and backup server details. nformation sources can be stored only in the nformation ource Modules folder for an M. You must register an M before you can create an. Ms can be registered using the Register nformation ource Module Dialog Box in arrowcast Administrator. Remapping information objects: nformation bject Remapping ool When you merge arrowcast erver systems, you can merge multiple nformation ource Modules to the same project using the nformation bject Remapping (R) tool. his R tool is a standalone executable, which is installed %Application ath%\delivery ngine\, where %Application ath% is the folder in which arrowcast erver is installed. his tool updates the preference objects answering the remapped Question bjects, which are stored in the ubscription Book Repository. Before remapping the objects, the tool performs simple validations for object integrity. t verifies whether the project Ds match for the nformation ources to be mapped. f the project Ds do not match, it validates whether the report or document D in the nformation bject or Question bject to be remapped exists in the target nformation ource. he tool does not verify whether the report or document structure is identical in both the source and target projects. he remapping is allowed if the object Ds match. Administration objects 13

34 Remapping may affect the content of a service that users receive. Any changes in a report or document definition between the source project and the destination project will result in different content. Additionally, if there is a difference in authentication objects or security objects for the information sources, this will also affect content. rerequisites You must have connectivity access to the bject Repository and ubscription Book Repository. You must have an account in the arrowcast ystem and have either ystem Administrator or Application Administrator privileges. he bject Repository and ubscription Book Repository must be on a version supported by the current arrowcast erver product. teps to remap information objects 1. Browse to the %Application ath%\delivery ngine\, where %Application ath% is the folder in which arrowcast erver is installed. For example, :\rogram Files\Microtrategy\arrowcast erver. 2. Double-click Remapool.exe. 3. nter the parameters in the Data ource ame, Database type, Login, and assword fields. lick ext. 4. elect either the Remap new information objects option or Undo a previous remapping option. f you have selected Undo a previous remapping, go to step he R tool retrieves the nformation ources from the repository and displays them. elect the source nformation ource in the FRM drop-down list and the target nformation ource in the drop-down list. lick ext. 6. A list of all the nformation bjects from the source nformation ource are displayed. You can remap a subset of nformation bjects or all of them. his list is filtered as follows: nformation objects whose document or report does not exist in the target information source. nformation objects whose question objects points to a document or report that does not exist in the target information source. 14 hapter 1 Microtrategy arrowcast erver architecture

35 7. he R tool resolves the dependency link between all the selected information objects. f there are several information objects using the same question object, and you want to remap only a few information objects, the R tool prompts for a preferred resolution. You can select Remap All, Remap one, or Just do as say and Remap ome. 8. lick... (Browse) to specify the location of the log file or the undo file. he R tool remaps the selected nformation bjects, the associated Question bjects, and reference bjects (if applicable). he remapping is complete. lustering and Failover lustering is a strategy in which multiple machines are configured to provide common services in a unified manner. ntelligence erver provides out-of-the-box clustering capabilities. onnecting multiple server machines together, with each machine running ntelligence erver, leverages the load balancing and resource sharing capabilities of arrowcast erver. Failover, as it applies to ntelligence erver, is a strategy by which work is automatically transferred from a failed ntelligence erver cluster node (machine) to another backup node. Load balancing Load balancing is a strategy in which work is evenly distributed among a set of ntelligence erver machines within a cluster. he goal of load balancing is to use all the available resources in an efficient manner to improve system performance. he administrator can set the load balance factor for each of the servers, including the primary server. he default value for the load balancing factor is 1. Minimum value= -1 Maximum value= he value can be increased for more powerful servers in a cluster to provide an appropriate balance. A larger load balance factor for a server implies that the server supports a greater load in the server cluster in which it resides. For example, if two servers make up a cluster, with one server having a load balance factor of 3, and the other server having a load balance factor of 2, and 20 users log in, 12 users are supported by the first server and 8 users are supported by the second server. he load balance factor can be set to 0 for a machine to act as a backup server that takes the load only if all other nodes are down. Administration objects 15

36 he load balance factor can be set to -1 for a node that should get no jobs from arrowcast erver even if other nodes in the clusters are down. ntelligence erver load balancing is session-based. he load is calculated based on the number of sessions open with a node. At the time of connection, the session is opened on the node carrying the least load, and all requests within that session go to the same node. When arrowcast erver is ready to send a job to ntelligence erver, it communicates with the primary ntelligence erver or its cluster, as follows: f the primary ntelligence erver is available and not part of a cluster, the job goes to the primary ntelligence erver. f the primary ntelligence erver is available and is a part of a cluster, arrowcast erver sends the job to the node with the least load. f no nodes are available in the primary ntelligence erver cluster, arrowcast erver will try to communicate with the backup ntelligence erver. f a backup ntelligence erver is not available or is not defined, the job will fail. f a backup ntelligence erver is available but is not part of a cluster, the job will go to the backup ntelligence erver. f a backup ntelligence erver is available and is part of a cluster, then arrowcast erver sends the job to the node with the least load. he backup ntelligence erver can be part of the same cluster as the primary ntelligence erver. n this case, the job can be sent to the backup ntelligence erver if it is the node with the least load. nformation ource Module (M) he prepackaged nformation ource Module (M) provides a way to include reports and Report ervices documents in arrowcast erver service content. hese reports and documents can be personalized in various ways, as described below: Authentication objects: A distinct ntelligence erver login can be used to run the reports for each subscriber. his allows security filters to be applied to service content, if your ntelligence erver logins have security filters defined for them. n arrowcast erver, authentication objects are used to store this login information. You specify a default login in the information source definition. ach subscriber's authentication object, if it exists, is then used to override this default. 16 hapter 1 Microtrategy arrowcast erver architecture

37 ecurity objects: You can enforce data access security without having a distinct ntelligence erver login for each subscriber. arrowcast erver provides this option with the security object. A security object is defined for each user by answering an element list prompt. For example, in the Microtrategy utorial, the answer outh might be a security object for a prompt on the attribute Region. n the information source definition, you can specify which prompt object should be answered by the prompt answers in the security objects of subscribers. When a subscriber defines preferences, the prompt answer in his security object limits the data that is available for selection. When a report is run for that subscriber, the prompt answer limits the data that is returned for the report. references: rompts in Microtrategy reports are a powerful feature that can help application designers to serve the needs of more users with less work. his is accomplished by having subscribers answer prompts in a report to personalize the information they receive. hese prompt answers are called preferences. references can be created for each user, and prompt answers can be reused across multiple subscriptions. references can be created for and applied a specific subscription. Locales: ntelligence erver can use language information to control various aspects of the report results it generates. his includes number formatting, date and time formatting, and the language used for descriptive text. ersonalizing service content involves prompt and report design, service content development, and subscription administration. ee the arrowcast erver Application Designer Guide for more information on personalizing service content and using the M. Web subscription Using Web subscription, Microtrategy Web users can subscribe to reports and documents for delivery. rerequisites for enabling Web subscriptions: onfigured information source: An information source () must be defined for the project containing the reports and documents you want arrowcast erver to deliver. his must have Web ubscription enabled. You can create an using the ystem onfiguration Wizard. n the onfigure ources page, select the project for which you want to enable Web subscription, and choose nable report delivery from arrowcast erver. Administration objects 17

38 onfigured Microtrategy Web server: nce you have an created and configured, you can configure Microtrategy Web to allow subscriptions. ee the arrowcast erver nstallation and onfiguration Guide for information on configuring a Microtrategy Web server for this purpose. he cheduled Delivery to -mail, File xport, and rint options are not visible in Microtrategy Web unless an administrator enables their associated Web privileges in Microtrategy Desktop. Microtrategy offers cheduled Delivery to -mail, File xport, and rint. he following table describes these options and their respective Web privileges. cheduled Delivery Description Web rivilege Functionality -mail nables delivery of a report or Report ervices document to a specified address, based on a predefined schedule. You can deliver reports in various formats, such as DF, Microsoft xcel, Adobe Flash, or HML. You can deliver documents in DF, Flash, and xcel formats. end ow cheduled reate new address Allows sending s using arrowcast erver Allows scheduled s using arrowcast erver Allows Web user to create new addresses for subscriptions File xport nables delivery of a report or document to a specified network file location, based on a predefined schedule. You can export reports in various formats, such as DF, xcel, Flash, text, or HML. You can export documents in DF, Flash, and xcel formats. xport to file now cheduled export to file reate new file location Allows export to file using arrowcast erver Allows scheduled file delivery using arrowcast erver Allows Web user to create new file locations for subscriptions rint nables printing of a report or document on a specified network printer, based on a predefined schedule. Reports rint now cheduled printing reate new print location Allows sending print jobs using arrowcast erver Allows scheduled printing using arrowcast erver Allows Web user to create new printers for subscriptions in Flash format can be enabled only through customization; they are not supported automatically. However, customization is not required for Report ervices documents in Flash format. For details on customization, see the Microtrategy Developer Library (MDL). For information about an MDL product license, contact your Microtrategy account executive. 18 hapter 1 Microtrategy arrowcast erver architecture

39 User nformation he User nformation supports an extensible set of subscriber-user properties such as a subscriber s first name. By default, the following user properties are available: First name Middle initial Last name uffix itle alutation treet address ity tate Zip code ountry You can add new user properties or remove any of the existing properties by selecting dit Available User roperties from the ools menu in arrowcast Administrator. hanges made to these properties are automatically reflected in the ubscription ortal. he User nformation information source is automatically configured when you create a new system using the ystem onfiguration Wizard. ubscription nformation he ubscription nformation information source () supports subscription properties such as a subscriber's D and physical address. he following subscription properties are available: Address D Address display Device D Device name Locale D hysical address ubscription D ubscription set D Administration objects 19

40 ubscription set name User D All subscription data Unique message identifier he values for these properties are determined by arrowcast erver when each service executes. For this reason, they are not directly accessible through either the ubscription ortal or the User ditor in the ubscription Book ditor. hese properties can be useful for inserting information such as the Unique Message dentifier into service content for response tracking, or for additional personalization of XL processing using a compound document element containing multiple XML information objects. he ubscription nformation is automatically configured when you create a new system using the ystem onfiguration Wizard. ystem nformation he ystem nformation information source () supports service execution properties such as service name and date. he following properties are available: All service execution information ervice D ervice name ervice description ervice creation date ervice execution date ervice execution time ervice execution D xternal service execution D ervice segment execution D he values for these properties are dynamic system information, based on the specific service execution. xecution date and execution time are provided in either a standardized string format or can be configured by locale. he service execution date, service execution time, and service creation date timestamps match the time zone expressed in Universal ime oordinates or as specified by the user on the xecution tab in ystem ettings (see ystem ettings dialog box layout). ervice description is based on execution locale. 20 hapter 1 Microtrategy arrowcast erver architecture

41 hese properties can be useful for tracking and debugging messages, identifying when reports were generated or saved, and maintaining text files containing service names. he ystem nformation is automatically configured when you create a new system using the ystem onfiguration Wizard. Document formatting modules and document formatters he Delivery ngine uses document formatting modules (DFMs) to format message data. ach execution engine uses the document formatting modules to transform document definitions and personalized dynamic content into personalized, formatted arrowcast documents. ach DFM typically supports just one type of arrowcast document. arrowcast erver comes with three DFMs: he HML Document Formatting Module, which generates HML pages for content. he laintext Document Formatting Module, which renders tabular data into plain text tables and inserts the tables into text files. he xcel Document Formatting Module, which produces xcel workbook files from xcel templates and dynamic content. he source code for a sample DFM is installed with arrowcast erver, and additional samples are available on the Microtrategy olutions website. For details on implementing and adding document formatting modules to a system, see the Document Formatting Module Directory in the arrowcast erver DK Guide. A document formatter is an administration object that stores configuration and other information for using a document formatting module. he ystem onfiguration Wizard automatically creates and configures the three document formatters described below when a new system is created. You can create additional document formatters in the Document Formatters folder using arrowcast Administrator. For steps to create new document formatters in arrowcast Administrator, see Working with Document Formatters. HML document formatter: his document formatter lets you include Microtrategy graph reports in messages. t supports a variety of information object types including XML (grid), image (graph), plain text (user information), and others. everal devices are configured to work with this document formatter so that graphs appear correctly in message content when delivered via . Administration objects 21

42 laintext document formatter: his document formatter provides the best possible tabular output on mobile devices. t supports only XML and plain text information objects. everal devices are configured to work with this document formatter so that tabular results are formatted in the best possible way on a wide variety of mobile devices. xcel document formatter: his document formatter provides powerful formatting control capabilities for creating richly-formatted workbooks. XML and plain text information objects are supported. his document formatter does not support images in xcel workbooks, such as Microtrategy graph reports.you can define the formatting properties of an xcel document formatter using the Document Formatter - xcel Dialog Box. he xcel DFM creates temporary files on a disk while it formats xcel workbooks. he default location in which these temporary files are placed is %Application ath%\delivery ngine\emp, where %Application ath% is the folder in which arrowcast erver is installed. For example, :\rogram Files\Microtrategy\arrowcast erver. ee the arrowcast erver Application Designer Guide for more information on information objects and documents. nformation transmission modules (Ms) and information transmitters (s) An information transmission module (M) is a software component the Delivery ngine uses to package (for example, multi-part MM-encode) documents into messages, and to send those messages to recipients. When all of the personalized arrowcast documents for a message are complete, those arrowcast documents are sent to the appropriate information transmission module for packaging and delivery. he M uses an address s device to control how each message is packaged and transmitted to that address. For example, some devices may indicate that messages should be packaged using multi-part MM encoding, while others might specify UUencoding. Ms can support a wide array of distinct recipient devices. ach M typically supports one type of transmission technology, such as M. arrowcast erver comes with several Ms. hese modules are: he -mail (M) Module, which sends nternet using M and -M he M ransmitter, which sends M messages using M 22 hapter 1 Microtrategy arrowcast erver architecture

43 he ortal M, which stores messages in the ubscription Book Repository for retrieval and display by the ubscription ortal he source code for a sample M that writes files to disk is installed with arrowcast erver, and additional samples are available on the Microtrategy olutions website. o learn more about implementing and adding Ms to a system, see the nformation ransmission Module Directory in the arrowcast erver DK Guide. An information transmitter () is an administration object that represents a specific use of an information transmission module (M). An information transmitter has characteristics that differentiate it from other information transmitters defined for the same M. he ystem onfiguration Wizard automatically creates and configures several s when a new system is created. For information about the use of information transmitters during system configuration, see ystem configuration process in the arrowcast erver nstall and onfig Guide. hese include: he -mail (M) information transmitter he File information transmitter he rint information transmitter he M (M) information transmitter he Web (ortal) information transmitter he Wireless (M) information transmitter You can also create additional s in the nformation ransmitters folder using arrowcast Administrator. For information about creating and configuring new information transmitters, see onfiguring nformation ransmitters. -mail (M) information transmitter: his information transmitter () sends messages over the nternet, using the M and -M protocols. t supports both UUencoding and multipart MM encoding formats, allowing attachments and HML message content. Devices are configured to enable this to support different clients, so that graphs appear correctly in message contents while attachments such as xcel workbooks appear as attachments. his must be configured with a FRM address and a RLY- address before it can be used, but an advanced execution control document can be used to override these and other transmission parameters. For details on configuring the -mail (M), see - mail (M). o understand the various transmission scenarios for - mail, see etting up arrowcast erver for transmission. Administration objects 23

44 File information transmitter: his transmits files to networked computers and remote servers. t sends to file locations you designate as well as locations specified by Microtrategy Web users. his is configured automatically by the ystem onfiguration Wizard. o understand the various transmission scenarios for File, see etting up arrowcast erver for file transmission. rint information transmitter: his sends services to network printer locations. t sends to printers you designate as well as printers specified by Microtrategy Web users. his is configured automatically by the ystem onfiguration Wizard. o understand the various transmission scenarios for rint, see etting up arrowcast erver for printing. M (M) information transmitter: his sends M messages over the nternet using the M protocol. t must be configured to connect to a short message service center (M) and provide account information before it can be used. For details on configuring the M (M) information transmitter, see M (M). o understand the various transmission scenarios for M (M), see etting up arrowcast erver for text (M) transmission. Web (ortal) information transmitter: his stores messages in the ubscription Book Repository. he ubscription ortal retrieves them for display. t supports HML and plain text message content, and attachments with a variety of MM-types. his is configured automatically by the ystem onfiguration Wizard. Wireless (M) information transmitter: his sends messages over the nternet using the M and -M protocols, and uses the same M as the -mail (M). t supports both UUencoding and MM encoding formats. everal devices are configured to enable this to support a wide variety of mobile devices so that grid report results appear correctly in message contents. his must be configured with a FRM address and a RLY- address before it can be used, but an advanced execution control document can be used to override these and other transmission parameters. For details on configuring the Wireless (M), see Wireless (M). he -mail (M) and Wireless (M) information transmitters () can be configured to create (.eml) files on a disk. he location in which these files are placed is specified as part of the definitions. f no location is specified, the files are written to the avedmail folder in the Delivery ngine application folder. 24 hapter 1 Microtrategy arrowcast erver architecture

45 Devices A device is an object that specifies how arrowcast documents should be formatted and transmitted to a recipient. A device corresponds to the type of mechanism a recipient will use to receive the arrowcast erver message. For example, if you want to send messages via , and your recipients are using a mail client that supports M such as Microsoft utlook, you can create an M information transmitter (), then create a Microsoft utlook device for that. f you want to send files to a file location on a computer on your network, you can create a File, then create a file device specifying your network file location and file properties. f you want to send services to a printer location on your network, you can create a rint, then create a printer device specifying your network printer location and printer properties. everal devices are created for you by the ystem onfiguration Wizard when you create a new system. You can also create new devices using the Device ditor in arrowcast Administrator. You can import device libraries and device library updates by right-clicking the Devices folder and selecting mport Devices. You must have at least one and at least one document formatter before you create a device. Default devices and document formatters are created by the ystem onfiguration Wizard. Locales and internationalization Locales enable a arrowcast erver system to support a diverse, multinational user population. ach subscriber selects the locale of his choice. his choice then controls the ubscription ortal display and service content that is delivered to him. arrowcast erver includes eleven locales representing different languages and formats, plus the system locale. You can modify these locales and create new ones as needed using the Locale ditor in arrowcast Administrator. For steps to create a new Locale, see reating Locales. Locales impact the behavior of a system in several ways, as described in the following subsections: Localization of ubscription ortal Localization of object names and descriptions Localization of service content Administration objects 25

46 ontrol of Microtrategy report execution election of character set for message encoding Localization of ubscription ortal he ubscription ortal uses a subscriber s locale to determine which of the available languages to use to show instructions, labels, and other interface content. he list of locales is available from the references page of the ubscription ortal. his locale selection is also displayed in the ubscription Book ditor in arrowcast Administrator. Localization of object names and descriptions ach object can have one name per locale. hus, an object such as a folder named Reports in the system locale can have the name Berichte in the German locale and Rapports in the French locale. he name that is displayed in an interface depends on which locale the user has selected as his locale preference. n arrowcast Administrator, the Display Locale controls which names and descriptions are shown in the object browser, dialogs, editors, and wizards. n the ubscription ortal, the subscriber's locale preference controls which names and descriptions are displayed in the ubscription ortal interface. ote the following: f an object has not been given a name in the display locale (arrowcast Administrator) or user locale preference (ubscription ortal), the name in the system locale is shown. f you change the name of a locale as it appears when viewing a list of locales, the ubscription ortal web server must be stopped and restarted for the new name to be displayed on the User references page. Localization of service content o vary service content for different recipients, there are two types of locales: selection locales, which determine which users should receive which content, and execution locales, which determine how content is generated for subscribers. ach are described below. n most cases, the selection locale for a publication should match the execution locale for all arrowcast documents within the publication. However, it is possible to use one locale for the selection locale for a publication, and several different execution locales in different arrowcast documents within that publication where execution requirements (such as character sets) vary among documents. For example, for some mobile 26 hapter 1 Microtrategy arrowcast erver architecture

47 devices, the character set for the mobile device may differ from the subscriber s conventional alphabet. ee the arrowcast erver Application Designer Guide for information about working with services that support multiple locales and publications. election locales When a user is created, either the ubscription Administrator (via arrowcast Administrator) or the user (via the ubscription ortal) selects a locale for which he will receive content. When a publication is created, the application designer chooses a selection locale that determines which users should receive the content in that publication. f a user chooses a specific locale (for example, Locale A ), the application designer must choose the same locale for a publication as the selection locale, for the user to receive this publication. f a publication is set up to support the system locale, it can be used to generate content for subscribers from any locale. However, this only occurs if a publication in a given subscriber s locale is not available. For example: F User A is in locale A. User B is in locale B. ublication 1 is in locale A. ublication 2 is in the system locale. H User A receives ublication 1 and User B receives ublication 2. his feature can be used to provide either default content or error-handling content to subscribers. n the example above, ublication 2 could contain either generic content that is useful to locales A and B, or it could contain a generic error message (possibly in several languages) indicating that the service does not support subscriptions in the subscriber s locale. xecution locales When a arrowcast document is created, the application designer can specify that the document should be executed in a specific execution locale. he definition of the locale then controls how information should be gathered, formatted, packaged, and transmitted for this document. For example, an application designer might define a French and a German locale to gather information from ntelligence erver in the appropriate languages. f one of these locales is chosen as the execution locale for a arrowcast document, all report content in this document is retrieved using the language specified in the definition of that locale. ee ontrol of Microtrategy report execution for more information about how the execution locale performs report result localization. Administration objects 27

48 ontrol of Microtrategy report execution ntelligence erver provides multinational language and formatting support. arrowcast erver leverages this capability by including locale information in report requests. When arrowcast erver needs to run a report, it specifies which language (locale) ntelligence erver should use. ntelligence erver languages control such behavior as: umber formatting, including decimal and thousands separators Date and time formatting, including month representation, yearmonth-day ordering, and 12/24 hour time representation. Descriptive text language, such as standard words that are included with report contents. he locale used to run reports is not necessarily the same as the locale preference of the subscriber for whom the report is being run. ee the arrowcast erver Application Designer Guide for details. election of character set for message encoding M-based supports languages and alphabets that use the 128 characters that can be represented with 7-bit M encoding. he Unicode standard is a 16-bit character encoding standard that can represent every character used in almost every written language. he standard includes specifications for mapping characters from each character set to Unicode and back again. Many servers do not support the Unicode character set, and many clients are not able to properly display Unicode content, although they can display other character sets. ome only accept U-A. arrowcast erver fully supports the Unicode standard. o send messages to systems that do not support Unicode, arrowcast erver uses locales to control the character sets used by information transmitters (s) based on the -mail (M) Module. For example, to send Russian content to devices that only support the Russian character set, you configure a locale to use the correct Russian character set for any s, and then ensure that content is defined using that locale. ee the arrowcast erver Application Designer Guide for details about defining service content in specific locales. he following character sets are supported by the -mail (M) Module: Arabic ( ): 8-bit encoding. Also called Windows Baltic ( ): 8-bit encoding. Also called Windows hapter 1 Microtrategy arrowcast erver architecture

49 entral uropean ( ): 8-bit encoding. Also called Windows 1250 and Latin-2. hinese implified (GB2312): multi-byte (1 or 2 bytes per character) encoding. Also called Windows 936. hinese raditional (BG-5): multi-byte (1 or 2 bytes per character) encoding. Also called Windows 950. yrillic (K8-R): 8-bit encoding. Also called Windows 1251 and lavic. Greek ( ): 8-bit encoding. Also called Windows Hebrew ( ): 8-bit encoding. Also called Windows Japanese (-2022-J): multi-byte (1 or 2 bytes per character) encoding. Also called Windows 932. Kanji (hift-j): multi-byte (1 or 2 bytes per character) encoding. Korean (U-KR): multi-byte (1 or 2 bytes per character) encoding. Also called Windows 949. hai (WDW-874): 8-bit encoding. urkish ( ): 8-bit encoding. Also called Windows 1254 and Latin-5. U-A: 7-bit encoding of the A character set. UF-7: 7-bit, variable-length encoding of the Unicode character set. UF-8: 8-bit, variable-length encoding of the Unicode character set. Unicode 1.1 (-10646): 16-bit encoding of the Unicode character set. Western ( ): 8-bit encoding. Also called Windows 1252 and Latin-1 (A) he arrowcast erver installation and setup program does not install the code pages and conversion support needed for each of these character sets. f you use a character set that is not already supported by your operating system, service execution fails. For information on installing support for additional code pages, see Language upport. he locales available when you create a new system using the ystem onfiguration Wizard specify the correct character sets to use for the corresponding languages. Administration objects 29

50 Administrative accounts Administrators can create and assign access privileges to other administrators by creating arrowcast Administrator accounts. Accounts are based on Windows accounts. You must create a arrowcast Administrator account for each Windows account that an application designer, subscription administrator, or other system administrator will use to connect to the system via arrowcast Administrator. Accounts are assigned various roles. ach role has specific privileges on the arrowcast system. By default, a new account is assigned all four roles. You can assign the following roles to accounts using the Assign Administrative rivileges to Account Dialog Box in arrowcast Administrator: ystem Administrator. his role has privileges to create, delete, and modify administration objects, including other accounts. he system administrator cannot modify application objects. ach account assigned the system administrator role needs local administrator Windows permissions on each distribution manager (DM), execution engine (), and Microtrategy Logging erver (ML) machine that is part of his arrowcast erver system. ervice Designer. his role allows a user to create application objects only, and to modify and delete only those objects created and owned by this user. he service designer cannot modify administration objects. ach account assigned the service designer role needs log on locally Windows permissions on his local machine and each distribution manager (DM) machine. Application Administrator. his role is used as a super user for application objects. he application administrator can create, delete, and modify all application objects, regardless of who owns them. he application administrator cannot modify administration objects. ach account assigned the application administrator role needs log on locally Windows permissions on his local machine and each distribution manager (DM) machine. ubscription Administrator. his role allows a user to add, delete, and edit information in the ubscription Book, and create and delete subscription sets. ach account assigned the subscription administrator role needs log on locally Windows permissions on this local machine and each distribution manager (DM) machine. Windows permissions are set in the User Manager or the User Manager for Domains (a Windows utility). ee Managing Administrator Accounts, for information on how to add login Ds. 30 hapter 1 Microtrategy arrowcast erver architecture

51 Unverified administrative accounts When you create an administrative account, arrowcast erver must verify the existence of the specified user in a trusted Windows domain and gather a unique Windows D for this user, as described in the following options: f you browse a Windows domain to select a user, arrowcast erver can verify the existence of the user because the users listed when browsing are provided directly by Windows. f you manually type a Windows user name, arrowcast erver attempts to verify that the user name entered exists in a Windows domain: f you type a user with no domain, arrowcast erver searches all trusted domains. f you type both a domain and a user, arrowcast erver searches the specified domain. f arrowcast erver cannot contact the specified domain or cannot verify the existence of a user within a domain, you are asked whether you want to create an unverified administrative account. An unverified administrative account is an account that arrowcast erver cannot verify as existing in a trusted Windows domain and for which no unique Windows D has been found. his can result from situations including the following: he user is not in a trusted domain. he local computer is offline. he user is in a network that is not linked to the current network. he user does not yet exist. When a Windows user attempts to register a system using a domain and user name matching an unverified administrative account in the system, the user is allowed to connect and is verified solely based on the user s domain and login. his can be useful, for example, in network environments where not all users are part of Windows trusted domains. An administrator can add unverified administrative accounts for users using specific machine names. n this case, the domain and user name specified are Machine\User. Administration objects 31

52 Application objects Application objects are objects that are used to create and define services, define recipients, and schedule delivery. hese objects include: arrowcast documents ublications chedules ervices ubscription sets nformation objects Question objects mported files Application objects are created by the application designer and administered by the application administrator, which allows one application administrator to administer objects created by several application designers. ee the arrowcast erver Application Designer Guide for more information on application objects. ortal objects ortal objects are those objects that are used to control the behavior of the ubscription ortal. hese objects include: ites hannels Device types Device settings hese objects are stored in the ortal Repository. ortal objects are created by the application designer and administered by the application administrator, both using the ortal Administration Wizard. ubscription ortal web server he ubscription ortal Web erver is composed of Microsoft nternet nformation erver (), the ubscription ortal active server pages, and other ubscription ortal components. hese work together to provide a web interface to perform subscription administration tasks. 32 hapter 1 Microtrategy arrowcast erver architecture

53 nformation repositories arrowcast erver stores objects in three repositories: the bject Repository (R), the ubscription Book Repository (BR), and the ortal Repository (R). ach is described in the following subsections. For a given arrowcast erver system, these repositories can be created in the same database or can be stored in different locations. For example, it may be desirable to have the ubscription Book Repository (BR) be in the same location as an operational data store (D) because both the BR and an D are transactional data repositories on which occasional large queries are run. o maintaining these repositories in the same location helps the following: haring administrative efforts, including backup/restore, security, and maintenance roviding the ability to join subscription data with D data for service execution roviding the ability to make changes to the D based upon subscription changes in the BR he bject Repository and ortal Repository are used to store and access arrowcast erver objects. For database optimization purposes, it may be desirable to have database features such as table extents, database extensions, index creation, and failover configuration. File storage architecture differs significantly between the three repositories. ecurity needs of the repositories may also differ, since the ubscription Book Repository contains user information such as address information. bject Repository he bject Repository is the set of tables in a database where administration and application objects are stored. he table space occupied by these tables is fairly small, on the order of MB for a typical system. hese tables do not contain recipient addresses or subscription data. he bject Repository is accessed through the Microtrategy Delivery ngine A. For information about configuring the bject Repository, see ystem configuration process in the arrowcast erver nstallation and onfiguration Guide. nformation repositories 33

54 More than one arrowcast erver system (see About the arrowcast erver system) can be stored within the same database. toring more than one bject Repository in the same database can be useful because you can use a single database to store your development, test, and production repositories, as well as backup and archive repositories. ach arrowcast erver system bject Repository is stored in a database as a set of tables that may contain an administrator-specified system prefix on the table names. f you specify a different prefix for each arrowcast erver system, more than one arrowcast erver system bject Repository can coexist in the same database. hus, during system configuration, all existing arrowcast erver systems in the database location you choose are displayed, listed by the system prefix. hese systems can be registered, overwritten, or new systems can be created with new system prefixes. ubscription Book Repository he ubscription Book Repository (BR) is a set of tables in a database that store information about recipients, including names, addresses, personalization settings, and subscription specifications. hese tables also store message transmission information for transmission recording, and personalized arrowcast documents for the ubscription ortal. he BR is like a data warehouse containing lookup tables for the recipient data. When a service is run, information specifying the service recipients and their personalization is retrieved from the BR. Because the BR can be relatively large and is heavily accessed, consider putting it on the most powerful database platform you have available. f you expect to use dynamic subscription or page-mode personalization, you should also consider putting the BR in the same database as your data warehouse. his facilitates queries and reports that join your data warehouse and subscriber data. his setup provides better performance than if the warehouse data is returned first and then used to look up subscription data in a separate BR. nce you configure the BR in the ystem onfiguration Wizard, all other tasks involving this database are handled by the subscription administrator. For information about configuring the ubscription Book Repository, see ystem configuration process in the arrowcast erver nstallation and onfiguration Guide. More than one BR can be stored within the same database. ach BR is stored in a set of tables that may contain an administrator-specified system prefix on the table names. f you specify a different prefix for each BR, more than one BR can coexist in the same database. hus, during system 34 hapter 1 Microtrategy arrowcast erver architecture

55 configuration, all existing BRs in the database are displayed, listed by the BR prefix. hese BRs can be added, overwritten, or new BRs can be created with new prefixes. You may want more than one BR in a database so that multiple BRs can be developed for different purposes. For example, an BR can be created as a development and testing environment and another can be developed as the production system. ortal Repository he ortal Repository is the set of tables in a database where all your portal objects are stored. his repository is relatively small and does not contain recipient addresses or subscription data. he ortal Repository is accessed through the Microtrategy ubscription ortal A by the ubscription ortal and the ortal Administrator Wizard. A ortal Repository is composed of a specific set of tables, located in a database and identified by a certain table prefix. hese tables are created automatically when you create a new system using the ystem onfiguration Wizard, and also when you create a new portal configuration using the ortal Administration Wizard. For information about configuring the ortal Repository, see ubscription ortal onfiguration in the arrowcast erver nstallation and onfiguration Guide. he tables in each ortal Repository can be given a unique table prefix, so that multiple ortal Repositories can exist in the same physical database instance. ach ortal Repository can store the definitions of one or more sites. Multiple ubscription ortal systems can also share the same set of ortal Repository tables. nformation repositories 35

56 36 hapter 1 Microtrategy arrowcast erver architecture

57 2 upporting Resources HAR 2 2.stablishing his chapter describes preparation required before you create a production-quality arrowcast erver system. ervers required everal supporting servers are required for a arrowcast erver system. hese are described below, along with recommendations for system configurations with the highest availability, performance, and security control. Windows domain controllers arrowcast erver and arrowcast Administrator rely on Windows domain controllers for access control. hese controllers are used to authenticate arrowcast Administrator users and clustered, interacting arrowcast erver components. For security reasons, you should maintain a separate Windows domain for your production arrowcast erver system. reate a separate primary domain controller for your production system, to administer and control this separate domain. t is recommended that you access your test and production environments from the same arrowcast Administrator machine. his requires that you have a Windows account with access to both systems and therefore to both Windows domains. You can create an administration environment for your test system and use a domain that trusts the production system domain. You can then log into machines in your test system using production system Windows accounts. his lets you administer the test and production environments from a single machine, while maintaining a secure production environment and domain. 37

58 he closer (in terms of switches or routers) each arrowcast erver machine is to the domain controllers, the less time and network bandwidth is consumed performing Windows account authentication. For systems with high availability requirements, it is essential to have separate primary and backup domain controllers available, so that if the primary domain controller fails, the backup is still available for authentication purposes. Domain name system servers arrowcast erver uses a domain name system (D) service to identify the mail servers to transmit to when delivering . For example, to send messages to recipients in the microstrategy.com domain, arrowcast erver requests the available mail servers at that domain from a D service. t then uses the server names that are returned to connect to the remote servers and deliver the messages. Without access to a D service, arrowcast erver cannot send . he exception to this is when arrowcast erver is configured to use only a smart host. he closer each execution engine machine is to the D services, the less time and network bandwidth is consumed looking up remote server names. For systems with high availability requirements, it is essential to have separate primary and backup D services available, so that if one service fails the other is still available for requests. W servers arrowcast erver typically uses a Windows nternet ame ervices (W) server to locate machines on your local area network. For example, to connect to an execution engine, the primary distribution manager requests the address for the machine with the name designated for that execution engine. Without access to a W server, arrowcast erver components cannot communicate with each other. he exception to this is when arrowcast erver components are defined based on addresses. he closer each arrowcast erver machine is to the W server, the less time and network bandwidth is consumed looking up addresses. For systems with high availability requirements, it is essential to have separate primary and backup W servers available, so that if one service fails the other is still available for requests. 38 hapter 2 stablishing upporting Resources

59 hanging the name of a server in a system after the system has been configured causes other machines in the system to lose the ability to connect to and communicate with that server. Relational database management systems arrowcast erver cannot function without a relational database for the bject Repository, ubscription Book Repository, and ortal Repository. he ubscription ortal must be able to access the data warehouse to write back subscriber preferences if dynamic subscriptions and personalized page execution are used. upported database types and versions for these repositories are listed in the arrowcast erver nstallation and onfiguration Guide and the Microtrategy Readmes. he bject Repository is like a low-volume online transaction processing (L) database. mall queries are run on this database to retrieve object names and definitions, folder contents, and search results. nsert, update, and delete queries typically involve only a few records at a time. When an bject Repository is created using the ystem onfiguration Wizard, it generally consumes between 5 and 10 MB of table space, depending on the database platform used. he ubscription Book Repository is like a high-volume L database. mall queries are run on this database to insert, select, and update user and subscription information and record transmission information. Larger, more complex queries are occasionally executed by the ubscription Book Module to perform segmentation and retrieve subscription sets. he amount of data stored in the ubscription Book Repository depends on the number of subscribers, addresses, subscriptions, preferences, and ortal reports (which are HML, text, and xcel documents that get stored in the ubscription Book Repository). t is important to maintain a secure environment for your bject and ubscription Book Repositories. For steps to secure your bject Repository and ubscription Book Repository, see ecure the bject Repository and ecure the ubscription Book Repository. For systems with high availability requirements, use an RDBM that supports high availability. High-availability RDBM implementations support transactional integrity, but drop connections during a failure. arrowcast erver was designed to work with this behavior by reconnecting to the bject Repository and ubscription Book Repository during a connection loss. As a result, arrowcast erver can roll over seamlessly from a properly configured primary database server to a backup, without administrator intervention. ervers required 39

60 mart hosts/mail transfer agents (optional) he use of a smart host is not required. arrowcast erver can deliver e- mail messages directly to each recipient s mail server. However, a smart host can be used in the following instances: A smart host can be used to increase mail delivery throughput by caching, controlling, and reusing connections to remote mail servers in an optimized way. Without this capability, a large arrowcast erver cluster might overload receiving mail servers such that they begin to refuse additional connections. A smart host can introduce a demilitarized zone (DMZ) between the execution engine machines and the nternet, between the firewalls. ne firewall separates the DMZ from the nternet, while the other separates the DMZ from the internal corporate network. he execution engine machines sit on the internal corporate network, where they interact with the ubscription Book Repository database via DB connections. he smart hosts sit in the DMZ. he execution engines send messages to the smart hosts in the DMZ, which then relay those messages to the destination servers on the nternet. his arrangement effectively separates machines requiring database access from machines with nternet connections, helping to ensure the security of your system. For systems with high availability requirements, use a backup smart host if you have a primary smart host. therwise, if the smart host machine fails, arrowcast erver cannot deliver messages until the smart host is restored. nternet proxy servers/wlb servers (optional) he use of a proxy server is not required. arrowcast erver can provide web pages directly. However, a proxy server can be used for the following purposes: A proxy server or Workload Balancing erver (WLB) can be used to increase ubscription ortal performance by enabling a clustered ubscription ortal Web server configuration. When this configuration is used, inbound H requests are routed to the least busy web server, ensuring the best possible machine use and interface performance. 40 hapter 2 stablishing upporting Resources

61 A proxy server can be used to introduce a demilitarized zone (DMZ) between the ubscription ortal machines and the nternet, between the firewalls. he ubscription ortal machines sit on the internal corporate network, from where they interact with the repository databases via DB connections. he proxy servers sit in the DMZ. his arrangement effectively separates machines requiring database access from machines with nternet connections, helping to ensure the security of your system. For systems with high availability requirements, use separate primary and backup internet proxy servers, so that if one fails the other is still available for H requests. You can also place the ubscription ortal Web server in the DMZ, but locate the equelink erver services on the internal corporate network. Microtrategy ntelligence erver arrowcast erver was designed to work with Microtrategy ntelligence erver to retrieve useful information from operational data stores, data warehouses, and other corporate data stores. Like Microtrategy Web, arrowcast erver exchanges a large amount of data with ntelligence erver, particularly when it is executing a service with a large number of personalized reports or large report result data sets. deally, you can dedicate an ntelligence erver machine to your arrowcast erver system, but this is not always possible. For systems with high availability requirements, use separate primary and backup ntelligence erver machines, so that if one machine fails the other is still available for report requests. When configuring information sources, you can configure a backup ntelligence erver machine for each information source by clicking Advanced roperties to access the ntelligence erver roperties dialog box. ollocated services With smaller production systems, the workload handled by machines such as the W server is relatively light. t is a good idea to colocate some of these services on the same machines. For example, the primary Windows domain controller, D server, W server, and, in some cases, the distribution manager can be run together on a single machine with little if any reduction in performance. f the same colocation is done for backup servers, the total number of machines can be reduced. ervers required 41

62 etwork bandwidth, topology, and firewalls he arrowcast erver nstallation and onfiguration Guide describes network requirements for a arrowcast erver system. his section describes how to configure a arrowcast erver network environment for security, robustness, and performance. stimating bandwidth requirements arrowcast erver can generate a significant load on available network and nternet data line bandwidth. his may overload available network resources and cause poor system performance. nsure that your connection to the nternet (or to your internal network, depending on the application) has adequate bandwidth for your message delivery requirements. n average, each message creates approximately 4 KB of network overhead. With embedded graph images, HML markup text, and attached xcel workbooks, each personalized message can exceed 100 KB. A typical 1 line (~150 KB per second data transfer rate) can achieve a maximum theoretical throughput rate of 35 messages per second, and a typical rate closer to between 1 and 5 messages per second for a typical HML message. A 100 Mbit ethernet connection (~10 MB per second data transfer rate) can theoretically support nearly messages per second (assuming no message content), and typically supports between 100 and 500 messages per second for a typical HML e- mail message. he ubscription ortal must receive H requests and respond with HML pages and cached reports and Report ervices documents, including xcel workbooks and graphs. he network overhead for this exchange between the client web browser and the ubscription ortal server is similar to that for . etwork topology You should dedicate at least one network switch to your production arrowcast erver system. his switch should be directly connected (not connected through a router) to the following equipment, if possible: ach arrowcast erver component (for example, the distribution manager) rimary Windows domain controller rimary domain name system (D) server 42 hapter 2 stablishing upporting Resources

63 rimary W server he relational database management servers containing the bject Repository, ubscription Book Repository, and ortal Repository mart host/mail transfer agent hardware and software (optional) nternet proxy server/wlb hardware and software (optional) High availability For a system with high-availability requirements, you must duplicate much of the network environment to avoid single points of failure. A second switch that has integrated failover recovery with the first switch should be configured and connected to the same equipment as above, plus the additional equipment listed below, so that each machine has a network connection to both switches: At least one additional distribution manager for failure recovery At least one more execution engine than is needed to exceed arrowcast erver system delivery performance requirements Backup Windows domain controller Backup domain name server (D) Backup W server A high-availability relational database management server containing the bject Repository, ubscription Book Repository, and ortal Repository Web clustering hardware and software to divide the ubscription ortal subsystem across the two switches Backup smart host/mail transfer agent hardware and software (optional) -mail clustering hardware and software if a smart host is used lustered, redundant nternet proxy server/wlb hardware and software (optional) Firewalls An efficient place for a firewall is in the network switch described above. his switch then serves as the go-between for the internal corporate network and the demilitarized zone (DMZ) described above. etwork bandwidth, topology, and firewalls 43

64 A second firewall implemented between the DMZ and the nternet then ensures the overall security of the system. his second firewall must allow for M transmissions on ort 25 from either the execution engines or the smart hosts. t must also allow for H requests on ort 80 from ubscription ortal user browsers. he firewall for the corporate network must allow for communication between the various components and servers outlined above. For steps to set the arrowcast erver M transmitter, see Microtrategy arrowcast erver M transmitter through network firewall. nternet domain arrowcast erver was designed for use over the nternet. For arrowcast erver to function properly over the nternet, you must register a valid nternet domain, and then register the appropriate services on that domain, specifically and Web services. You also must ensure that the addresses provided for these services ultimately map to your execution engines and ubscription ortal Web servers, unless you are using an nternet proxy server or a smart host, in which case the addresses for those servers must be registered. Additional resources onsider the following additional resources when you plan your production arrowcast erver system: orporate -mail servers: For systems used to send messages to corporate mail servers, consider the mail volume that arrowcast erver will introduce into your corporate environment. Also, ensure that the corporate mail server is configured to allow the messages generated by arrowcast erver (which can include large xcel spreadsheets) to be processed and delivered. M enters: f you send M messages, you must contract with an M enter to transmit your messages over the wireless network. For more information on M, see chapter 3, etting up arrowcast erver for text (M) transmission. 44 hapter 2 stablishing upporting Resources

65 nternet and wireless service providers: f your system sends large volumes of personalized messages to nternet or wireless service providers for delivery to subscribers, you can contact these service providers in advance to ensure that your messages are recognized as business purpose and not spam. therwise, your messages might be rejected by service providers. Windows accounts: When you use arrowcast Administrator, you need to use a Windows account that is part of the same domain (or a domain trusted by the domain) in which your arrowcast erver machines are registered. f you access two systems at the same time, this Windows account must be able to access, and have an associated arrowcast Administrator account, on both systems. o prevent issues with password expiration, you can establish and use a arrowcast erver system account for all of the arrowcast erver services that cannot run under the local system account. hat way, you do not need to reconfigure these services every time the password changes. Additional resources 45

66 46 hapter 2 stablishing upporting Resources

67 3 3.onfiguring Machines HAR 3 his chapter explains how to configure the hardware and software that comprise your arrowcast erver system. his chapter assumes that you have reviewed the requirements described in stablishing upporting Resources. Hardware configuration his topic describes the hardware configuration requirements for setting up arrowcast erver. entral processing unit (U) he U configuration of your equipment includes two key variables: U count and U speed. he number of Us that you should allocate depends on the following: Your license type: tandard dition allows you to use only one machine in your arrowcast erver system. nterprise dition provides full product functionality, including the ability to cluster arrowcast erver components across multiple systems. Your license number, which corresponds to the number of Us you are allowed to use. For more information on license types and U licensing requirements, see nstallation rocedures and About arrowcast erver licenses in the arrowcast erver nstallation and onfiguration Guide. n general, the more machines you use to distribute your processing power, the better performance you achieve per U. his is because additional machines provide greater disk and network performance. Faster Us correlate directly to faster throughput and responsiveness for the Delivery ngine and ubscription ortal subsystems. 47

68 Memory he execution engines and ubscription ortal can consume large amounts of memory when processing large report results, generating xcel documents, processing large dynamic subscription and personalized page reports, or handling high concurrent user loads. his must be considered when configuring arrowcast erver system hardware. hysical memory is the amount of RAM on a arrowcast erver machine. he amount of physical memory available impacts the performance of your arrowcast erver system. More RAM allows the ubscription ortal to handle more concurrent users without paging to disk. t also allows the execution engines to handle larger data sets and subscription sets without page swapping. o ensure stable system operation, it is recommended that you do the following: onfigure each machine that will run one or more of these two highconsumption components with the maximum possible virtual memory. ontrol the memory consumption on the execution engines by limiting the number of subscriptions per segment within each service. his limits the total number of recipients for which an execution engine does work at any given time. ontrol the memory consumption on the ubscription ortal by limiting the number of simultaneous connections that your Web server accepts. Hard disk storage You should plan to have at least 256 MB, and preferably 1 GB, of free disk space after you complete the installation process. his space is used to store files such as temporary xcel workbooks, execution log files, and e- mail messages that have been saved to disk. ne important consideration for disk storage is fragmentation. While the execution log files generated by arrowcast erver are designed not to cause extensive fragmentation (they overwrite themselves in a cyclical fashion), the xcel workbooks and message files can cause severe hard disk fragmentation and subsequent system instability. t is advisable to create separate hard disk partitions for the following: ystem and program files such as the Windows erver operating system and the arrowcast erver program files emporary files such as the xcel workbook files Accumulating files such as messages which have been saved to disk 48 hapter 3 onfiguring Machines

69 Log files such as those generated by arrowcast erver You can control the drives and folders into which each of these types of files is written as follows: arrowcast erver program files: You can specify the drive and folder for arrowcast erver program files during the installation process. he default is :\rogram Files\Microtrategy\arrowcast erver\. xcel workbook files: You can configure the drive and path for temporary xcel files by editing the xcel document formatter definition. he default location is %Application ath%\delivery ngine\emp, where %Application ath% is the folder in which arrowcast erver is installed. For example, :\rogram Files\Microtrategy\arrowcast erver. -mail message files: You can specify where messages are saved to disk by editing the ave-to folder for the -mail (M) information transmitter. he default location is the avedmail folder inside the Delivery ngine program files folder. arrowcast erver log files: You can specify where log files are saved to disk by editing the log file path registry setting at: HKY_LAL_MAH\FWAR\Microtrategy\ Microtrategy Broadcast erver\7.0\ Distributed Logging ervice\loggingonsumer\ he default location is the Delivery ngine program files folder. For clustered configurations, it is important to have the same hard disk drive partitioning and lettering scheme. therwise, a folder or path for one of the file types might not be available on a particular machine. Hard disk management to support log files arrowcast erver system information is stored in log files. he arrowcast erver system administrator must administer every machine in the arrowcast erver system to support the use of log files over time. Log files often result in large files that can consume hundreds of megabytes of hard disk space. hese files can also become fragmented, which can slow hard disk performance. o avoid log file problems, perform the following steps: 1. reate a separate disk partition and set all log files for all applications to use this location. Hardware configuration 49

70 2. nsure that this partition has plenty of unused hard disk space. t is recommended that the partition be sized such that no more than 50 percent of the available space is used at maximum after all log files have been generated. 3. eriodically defragment your hard drive, check the size of log files, and delete unused log files. his routine maintenance should be performed at least once every few weeks. etwork o ensure adequate bandwidth, an ethernet network interface card with at least 100 Mbit throughput capability is recommended. For systems with high availability requirements, a second network interface card may be used to ensure connectivity to a second network switch and essential system resources. oftware configuration his topic describes the software configuration requirements for setting up arrowcast erver. perating system arrowcast erver uses Microsoft Windows as the operating system. For a list of Windows operating systems that are supported for arrowcast, see ystem software requirements in the arrowcast erver nstallation and onfiguration Guide. When configuring the Windows erver or Windows 2000 operating system, you must register the system as part of the Windows domain for which you have prepared a primary domain controller. You must also ensure that the Windows M environment variable points to a partition with adequate free disk space. Web server arrowcast erver uses Microsoft nternet nformation erver () to publish information and bring business applications to the Web. For information about configuring Microsoft nternet nformation erver () for security, see arrowcast erver ecurity. 50 hapter 3 onfiguring Machines

71 DB drivers arrowcast erver uses DB to connect to and communicate with all database servers in the system. For information about installing and configuring DB drivers and data source names, see DB and Ds in the arrowcast erver nstallation and onfiguration Guide. Languages arrowcast erver supports different character sets in various languages, when generating messages. For information about downloading and installing character set converters to support multi-language applications, see Language upport. Administration objects arrowcast erver contains the following objects and components that define the architecture of arrowcast erver. he following table describes the objects that need to be configured for the system to operate smoothly: bject bject Repository ubscription Book Repository Distribution managers xecution engines Microtrategy Logging erver Microtrategy nformation ources Description tores administration and application objects. For information about configuring the bject Repository, see ystem configuration process in the arrowcast erver nstallation and onfiguration Guide. tores information about recipients, including names, addresses, personalization settings, and subscription specifications. For information about configuring the ubscription Book Repository, see ystem configuration process in the arrowcast erver nstallation and onfiguration Guide. ontrols system operations. For information about configuring Distribution Managers, see Managing Distribution Managers. ontrols service segment processing. For information about configuring execution engines, see Managing xecution ngines. aptures and stores log data such as statistical data, error messages, system events, and segmentation status. For information about configuring execution engines, see onfiguring the Microtrategy Logging erver. Gathers information from external sources to be added to service contents. For information about configuring information sources, see onfiguring nformation ource Modules. oftware configuration 51

72 bject Document formatters nformation transmitters Devices Locales Accounts Description ransforms document definitions and personalized dynamic content into personalized, and formatted arrowcast documents. For information about configuring the xcel document formatter, see Working with Document Formatters. You must ensure that the xcel working drive and path, point to a valid local disk drive. referably, this is a separate partition from the one storing the operating system and the program files. ackages documents into messages and sends these messages to recipients. For information on configuring information transmitters, see onfiguring nformation ransmitters. f you configure the -mail (M) transmitter to ave to Disk, you must ensure that the ave o folder drive and path point to a valid local disk drive. referably, this is a separate partition from the one storing the operating system and the program files. You must also maintain this directory by deleting files that are no longer needed. pecifies how arrowcast documents should be transmitted to recipients. For information on configuring devices, see onfiguring nformation ransmitters. upports diverse and multinational user population that controls the ubscription ortal display and service content that is delivered to subscribers. For information about creating locales, see reating Locales. Allows to manage arrowcast Administrator accounts. For information on configuring accounts, see Managing Administrator Accounts. lustering lustering is a way of using machine resources to provide an efficient and robust processing environment for a arrowcast erver system. A cluster consists of two or more machines, each machine running at least one arrowcast erver system component. When designing a cluster, consider the two subsystems of arrowcast erver separately. t is sometimes desirable to physically separate the Delivery ngine subsystem from the ubscription ortal subsystem to ensure consistent performance of the ubscription ortal. he Delivery ngine subsystem components and ubscription ortal subsystem components described below can be installed on different machines to accommodate different load balancing, failover, and security requirements. For more information on configuring Delivery ngine and ubscription ortal components to meet security requirements, see arrowcast erver ecurity. 52 hapter 3 onfiguring Machines

73 Before creating a cluster, perform the following tasks: nsure that all machines in a cluster are registered in the same Windows domain, and that there is a network account in that domain that has administrative privileges on all the machines. Use this account to install and configure arrowcast erver. nsure that all of the machines in the system are part of the same subnet or connected to the same network switch. n high-availability applications, it might be necessary to separate the machines so that some are in one location and the rest are in a separate location. et up DB. very distribution manager machine should have the data source names (Ds) for the ubscription Book Repository and the bject Repository. very execution engine machine should have the D for the ubscription Book Repository. nstall the desired components of arrowcast erver on each machine. f you change the status of a machine from idle to active or add an additional machine to the cluster at run time and all available Us are already in use, an error message is displayed. You must reduce the number of Us currently being used by other machines. f you have upgraded your license and are adding a machine to the cluster, you must update the licensing information for your primary distribution manager machine. he primary distribution manager machine applies its license information to both to the local machine and to the machines in its cluster. Also update the licensing information for the backup distribution manager machines in the cluster in case the primary distribution manager machine fails. Delivery ngine subsystem he Delivery ngine is an active system. his means that after it is set up, the Delivery ngine continues to run services even if nothing interacts with it. Because of this, it is designed with clustering technology that differs significantly from typical passive clustering architectures. he components that form the Delivery ngine subsystem include: arrowcast erver logging system rimary distribution manager (DM) Backup distribution manager (BDM) xecution engine () lustering 53

74 A machine being used in one Delivery ngine subsystem might need to be used in a different system. For more information, see the following: hanging a machine from one system to another Manually changing a machine from one system to another Delivery ngine subsystems need to be configured for network connection failures. his involves both the primary and backup distribution managers. For more information, see onfiguring a system for network connection failures. arrowcast erver logging system For information on configuring the arrowcast erver logging system, see onfiguring the Microtrategy Logging erver. rimary distribution manager (DM) his component receives service execution triggers and distributes service data to the execution engines for processing. he primary distribution manager (DM) also designates failover execution engines and tracks the state of the other components in the system. You can add a DM that can become the DM using arrowcast Administrator. For systems with large numbers of execution engines or systems that will send large numbers of small services or segments, each distribution manager (DM) machine should have a high number of Us (two to four) and 1GB of RAM. f high availability is a requirement, two or more DM machines should be employed. ach DM server should be registered on the same Windows domain as the rest of the machines in the system. Also, the DM service account must be a network account with administrative privileges on all machines in the system. You can designate more than one DM, but only one machine serves as a DM. he other DMs serve as backups to the DM. You must update the licensing information on the DM if you upgrade your U license to add additional machines to the cluster. he licensing information on the DM applies to the cluster. Backup distribution manager (BDM) his component serves as a backup to the DM. f the DM machine fails, one of the backup distribution manager (BDM) machines becomes the primary machine and takes over processing where the failed machine left off. he ystem onfiguration Wizard allows you to add a DM, but you cannot designate whether it serves as a primary or a backup. 54 hapter 3 onfiguring Machines

75 You must update the licensing information on the BDM if you upgrade your U license to add additional machines to the cluster. f the DM fails and the BDM takes over, the licensing information on the BDM applies to the cluster. xecution engine () he execution engine () controls the execution and transmission of arrowcast messages called services, which are divided into processing units called segments. he execution engine receives a segment definition from the distribution manager, then performs the following: he execution engine checks the service definition for a list of required information sources. he execution engine initializes a segment executor and sends it all the information sources that are needed to run the service. When a message for every recipient in a segment has been delivered, the segment executor notifies the execution engine that the segment is complete. he segment executor is unloaded. he execution engine notifies the distribution manager that the segment is complete. he segment is updated in the execution queue. An execution record keeps track of the messages that have been successfully transmitted for each segment. his information is written to a file on the other execution engines in the cluster. f the segment has to be re-executed and fails over onto another execution engine, the new execution engine will not send messages that have already been recorded as transmitted. t only sends messages that were not sent successfully during the original segment execution. For systems with large numbers of subscriptions or complex services, each execution engine machine should have a higher number of Us (two or four) and 1GB of RAM. f high availability is a requirement, two or more execution engine machines should be employed. n the following diagram, the dashed lines indicate DB connections. very distribution manager in a cluster must have a data source name (D) for the bject Repository and the ubscription Book Repository. arrowcast Administrator can be on any machine, provided that it has Ds for both repositories. lustering 55

76 arrowcast Administrator DM ML BDM ML bject Repository ubscription Book Repository ML ML ML ML hanging a machine from one system to another f you have a arrowcast erver system that uses one or more machines as a distribution manager, execution engine, or Logging erver, and you want to use one of these machines for a different system, you must remove system components (distribution manager, execution engine, or Login erver) from the machine before adding system components for another system. he other alternative is to destroy the original system and lose all of its contents (including all application objects, system configuration, and governing settings). Any machine can only be used as a distribution manager, execution engine, or Logging erver for one system. hus, once a machine is used by a system, it is no longer available for use in other systems. Unregistering a system does not remove system components from the local machine or any other machine. Unregistering a system is equivalent to no longer viewing or connecting to this system, but does not impact any system components. f a system is unregistered with system components remaining on the local machine, you are warned so that you do not try to use this machine for a different system, as this will not be successful. 56 hapter 3 onfiguring Machines

77 For steps to complete these tasks, see onfiguring a arrowcast erver ystem. Manually changing a machine from one system to another f you encounter problems changing a machine from one system to another as described above, you can manually change a machine from one system to another. ach machine can be used by only one arrowcast erver system. Whenever a machine is used as a distribution manager (DM), execution engine (), or Microtrategy Logging erver (ML) for a arrowcast erver system, the following registry keys are created on that machine: HKY_LAL_MAH\FWAR\Microtrategy\ Microtrategy Broadcast erver\7.0\ etup\ystemgud HKY_LAL_MAH\FWAR\Microtrategy\ Microtrategy Broadcast erver\7.0\ etup\ystemame HKY_LAL_MAH\FWAR\Microtrategy\ Microtrategy Broadcast erver\7.0\etup\usedas hese keys prevent the same machine from being used in a different arrowcast erver system. When you remove a DM,, or ML from a machine, the corresponding usage is removed from the UsedAs registry key and, if that value becomes empty, the ystemgud and ystemame keys are removed as well. ince a machine can only be used by one system, these keys prevent administrators from accidentally damaging the configuration of a system by using a machine for system components from more than one system. However, in the event of a network or machine failure when a system is destroyed, these keys might not be removed and may cause difficulty when switching a machine from one system to another. n this case, you must manually remove several keys from the Windows registry, as described in the steps below. teps to manually remove registry keys Modifying registry values incorrectly can cause serious, system-wide problems that might require the re-installation of the operating system. Any edit of the registry is done at the user's own risk. ince these are user-initiated changes they are not covered by any Microtrategy warranty. Users should back up their registry or update an mergency Repair Disk prior to alterations. 1. From the tart menu, select Run. ype Regedit and click K. lustering 57

78 2. Browse for and delete the following registry keys: HKY_LAL_MAH\FWAR\Microtrategy\ Microtrategy Broadcast erver\7.0\ etup\ystemgud HKY_LAL_MAH\FWAR\Microtrategy\ Microtrategy Broadcast erver\7.0\ etup\ystemame HKY_LAL_MAH\FWAR\Microtrategy\ Microtrategy Broadcast erver\7.0\ etup\usedas HKY_LAL_MAH\FWAR\Microtrategy\ Microtrategy Broadcast erver\7.0\ DistributionManager\ Repositoryonnectiontring onfiguring a system for network connection failures he distribution manager requires the following two registry keys to operate properly: HKY_LAL_MAH\FWAR\Microtrategy\ Microtrategy Broadcast erver\7.0\ DistributionManager\ Repositoryonnectiontring HKY_LAL_MAH\FWAR\Microtrategy\ Microtrategy Broadcast erver\7.0\ DistributionManager\ HostListForetworkonnectionheck he first key provides the connection string to the bject Repository for the distribution manager. t is created automatically when a distribution manager is added to a Delivery ngine. he second key is created by the installation and is given a default string value of localhost. he distribution manager uses this list of servers to determine whether it has network connection by pinging each machine in this list. he check passes if the distribution manager can ping more than half of the machines. ither names or addresses can be used, and a string such as :2000 can be appended to specify the timeout (in milliseconds) for a particular host. You can place as many hosts as you want in the list. An example of a valid string is server1:3000;server2:2000;server3. f the list is empty, the check fails. he check always succeeds if the default value localhost is used. For the Delivery ngine subsystem to handle network connection failures, replace localhost with a list of dependable hosts that can serve as network connection references. 58 hapter 3 onfiguring Machines

79 ubscription ortal subsystem he ubscription ortal is a passive system. his means that it does nothing unless a user or another system interacts with it. t can be easily clustered with a variety of third-party clustering technologies. lustering can improve availability and performance by distributing the ubscription ortal workload across multiple servers. t is sometimes desirable to separate the components of a ubscription ortal subsystem for security, performance, and other reasons. he major components in the ubscription ortal are: ubscription ortal Web erver equelink he components are implemented as Windows services. As a result, it is possible to operate certain combinations of these components on separate machines, and configure them to communicate with each other over the network. ach is described below ubscription ortal Web erver he ubscription ortal Web erver provides a website through which end users and administrators work with arrowcast erver. t consists of a web server (Microsoft ) and a set of Active erver ages installed with the ubscription ortal that interact with that server. When ubscription ortal is installed, it automatically configures with virtual directories that point to these pages. ome of these pages provide the ortal Administrator Wizard, and others the ubscription ortal interface for end users. equelink equelink configures and manages data access across a number of data stores, operating systems, and deployment options. equelink provides a universal client for DB and JDB, and a centralized console for configuring and managing data access from a single point of control. equelink creates two services: LAgent 54, which is the Administrator, and Locket54, which is the erver. Workload distribution in a cluster ne advantage of clustering a Delivery ngine subsystem is to distribute work across multiple machines to increase system performance. he execution engine is the primary work horse in a Delivery ngine, and the Delivery ngine is designed to distribute work across the machines Workload distribution in a cluster 59

80 available as execution engines. his capability allows system performance to scale with the number of machines available as execution engines. his section describes the mechanism used to distribute work across the available execution engines. n a Delivery ngine, a segment represents one piece of an executing service. ystem workload is distributed by allocated segments. he capacity of each execution engine determines how many segments it can process simultaneously. While execution engines are busy, the remaining segments wait in a queue. he system administrator determines the size of service segments and the capacity of each execution engine. ach service has a setting for the number of recipients per segment. he segment size for each service should be based on the complexity of each service. For example, a simple with no attachments and no personalization can be split into larger (and therefore, fewer) segments than a service with the same number of recipients but with attachments and sophisticated personalization. he execution engine capacity is set based on the number of service execution segments that can be executed simultaneously, and on execution engine U power. his setting allows you to distribute work according to the capacities of different execution engines in your arrowcast erver system. he distribution manager uses the capacity setting combined with an execution engine s current workload to determine how segments will be assigned among available execution engines. When a service is executed, the ubscription Book Module divides the subscription set, which determines the entire subscription list of the service, by the service segment size to generate a list of segment ranges. A service execution segment is created for each segment range. ext, the distribution manager assigns the segments to execution engines based on the current workload and capacity settings of the available execution engines. he execution engines create a segment executor for each assigned segment. Finally, each segment executor processes the service for its segment of recipients. U affinity he ability to bind one or more processes to one or more processors is called U affinity or processor affinity. he arrowcast erver distribution manager(s) and execution engine(s) can take advantage of the U affinity when the machine has more than one processor. 60 hapter 3 onfiguring Machines

81 U affinity provides the following benefits: mproved cache performance: By keeping the data in only one processor's cache, cache performance is optimized, thereby preventing out-of-sync caches and cache invalidations. rocessor dedication: By dedicating a processor to one or more critical processes, the critical process receives the full attention of the processor. U affinity is possible only if the operating system supports the functionality. teps to set up U affinity 1. From the Windows tart menu, point to rograms, then Microtrategy ools, and then choose ervice Manager. he Microtrategy ervice Manager dialog box opens. 2. n the ervice drop-down list, select the Microtrategy Distribution Manager process or the Microtrategy xecution ngine process. 3. lick ptions. he ervice ptions dialog box opens, displaying the Distribution Manager ptions tab or the xecution ngine ptions tab, depending on the process you selected above. 4. elect the relevant check boxes for each processor as desired. f you do not specify the processor usage for the distribution manager or the execution engine, each process chooses the processors itself using the first, second, and so on processors to be used. 5. lick K to close the ervice ptions dialog box and return to the ervice Manager dialog box. 6. lick Restart to restart the distribution manager or the execution engine for the U affinity changes to take effect. Failure recovery ne advantage of configuring a clustered Delivery ngine is that in the event of a hardware, software, or network failure, failure recovery is provided. Any Delivery ngine subsystem that is intended to provide for failure recovery should contain more than one distribution manager and more than one execution engine for failure recovery purposes. Failure recovery 61

82 he components used for failure recovery include the following: he distribution manager, which assigns backup machines for individual segments, monitors execution engines for failure, and is backed up by another distribution manager he execution engine, which performs backup duties for executing segments he segment executor, which records segment execution hree kinds of system failures can occur, and the Delivery ngine handles each of them differently. hey include the following, and are described below: egment failure xecution engine failure Distribution manager failure egment failure he information source, information transmitter, or document formatter can return an error in a particular segment. When this occurs, the distribution manager is notified of the problem and executes normal failure recovery on another execution engine. xecution engine failure An execution engine failure is caused by problems such as a network crash or power outage on the execution engine. When the distribution manager detects a problem during its regular execution engine status check, it follows segment failure steps for each segment running on the failed execution engine. Distribution manager failure When a distribution manager (DM) initializes, it determines which other DMs in the Delivery ngine subsystem are active. f none are, it automatically assumes the role of primary DM. f another DM has already assumed this role, the new DM assumes the role of backup DM. f two distribution managers start up at the same time and it is not clear which started first, the primary DM is chosen by rank. Backup machines do not do any processing, although they receive data from the primary DM and confirm its active status. 62 hapter 3 onfiguring Machines

83 f that status changes due to some problem such as a network crash or power outage on the primary DM, the remaining DMs determine the new primary machine. he new primary machine notifies all the execution engines of the change in status. When the failed machine comes online, it acts as a backup DM. f the primary DM detects a problem with a backup machine through the backup s lack of a response, the primary DM stops recording status changes to the backup. When the failed machine returns to an online status, it once again acts as a backup DM. etting up arrowcast erver for transmission imple mail transfer protocol (M) is a protocol that enables transfer of messages between machines. arrowcast erver uses two modes when transmitting messages: direct mode and smart host mode. Direct mode When arrowcast erver is transmitting in direct mode, it attempts to connect directly to the recipient's server over the nternet. t locates this server using the following steps: 1. Retrieve domain mail server records. arrowcast erver isolates the nternet domain from a recipient s address (for example, microstrategy.com) by taking the characters following symbol. t then makes a request to the D server configured for the available network interface cards, asking for the MX or mail server records for the domain. 2. Locate mail server. arrowcast erver isolates the name of the mail server with the highest preference from the domain mail server records. t then determines the address for that mail server using a combination of D and W requests. 3. pen a / connection. arrowcast erver attempts to open a / connection on the port specified in the -mail (M) information transmitter settings, to the remote mail server. f a connection cannot be established, arrowcast erver tries to locate another of the servers returned in the domain mail server records. etting up arrowcast erver for transmission 63

84 4. pen a mail session. f a connection was successful, arrowcast erver opens up an session using HL (-M) if possible. therwise, HL (M) is attempted. f both protocols are rejected, arrowcast erver returns to step 2 and tries to locate another of the servers returned in the domain mail server records. 5. end a message. Depending on the session type, arrowcast erver uses the M or -M protocol to deliver the message to the remote server. 6. Locate the smart host. f all servers listed in the domain mail server records are unreachable or unworkable, arrowcast erver attempts to deliver the message using the smart host if it has been configured. t locates this mail server using a similar process to step 2, and proceeds with the rest of the steps above. f this process fails, the message is returned to the pending delivery queue. mart host mode When arrowcast erver is transmitting in smart host mode, it attempts to connect to the server configured in the device settings. t proceeds through steps 3-5 above in Direct mode. f the process fails, the message is returned to the pending delivery queue. he use of a smart host can help alleviate connectivity problems caused by some firewalls. For example, if your arrowcast erver system must transmit to recipients outside of the corporate firewall, you can configure it to transmit to a smart host inside the firewall that already has nternet access, and then let the smart host perform the transmission to the recipients. mart host configuration is part of the device configuration process. For more information about configuring devices, see ransmission tab. Device settings Device settings control how the content of a publication is packaged for delivery. For example, if an publication contains an HML message body with a graph report, an xcel workbook, and a subject line, the - mail (M) transmitter must package the HML message body, graph image file, and xcel workbook file as a single 7-bit U-A string before it transmits the message. wo encoding technologies are available for this packaging process: Multi-part MM and UUencoding. ach is described below. 64 hapter 3 onfiguring Machines

85 UUencoding he UUencoded format enables arrowcast erver to send messages as binary file attachments (such as xcel workbooks), but message contents are plain text, and HML message bodies are sent as attachments. ome e- mail clients, such as most mobile devices, do not support attachments. ee the Microtrategy Readmes for information about specific device capabilities and limitations. For information about configuring devices, see Device ditor. MM he MM message format enables arrowcast erver to send messages with HML message bodies, binary file attachments (such as xcel workbooks), and embedded images. t also allows a wide variety of character sets for message content, such as Latin-1 ( ), Korean (U-KR), and Japanese (-2022-J). ot every client supports all of these capabilities, so several device settings control specific aspects of how message parts are encoded within a MM message. ee the Microtrategy Readmes for information about specific device capabilities and limitations, and to chapter 10, Device ditor for information about configuring devices. haracter set requirements f services generate content that cannot be represented by U-A, ensure that the arrowcast documents with such content have the correct locale selections for document properties, and that the selected locales have the correct character set for the -mail (M) transmitter. therwise, when the -mail transmitter attempts to convert the arrowcast documents in the message publication from the Unicode character set used internally by arrowcast erver to the character set specified by the document locale, the conversion fails. When this happens, the message is not sent. For information about locales and arrowcast documents, see Locales and internationalization. esting M connectivity t is recommended that you test M connectivity before you attempt to start your system. You can test the ability of arrowcast erver to connect to and deliver messages to remote servers, using the information below. etting up arrowcast erver for transmission 65

86 teps to test D lookup 1. From the tart menu, select Run. ype cmd and click K. 2. ype the following command, which is case sensitive: :\>nslookup -type=mx domain name f you are testing on Windows 2000, you may need to type AY instead of MX to retrieve mail exchange domain records. 3. Look for the MX records (if any), and look at the preference value for each record. he lower the value, the higher the priority it takes. For example: :\>nslookup -type=mx microstrategy.com D request timed out. timeout was 2 seconds. *** an't find server name for address : imed out *** Default servers are not available erver: UnKnown Address: microstrategy.com MX preference = 100, mail exchanger = mail.uu.net microstrategy.com MX preference = 1, mail exchanger = mailgate2.microstrategy.com microstrategy.com MX preference = 50, mail exchanger = mailgate.microstrategy.com mail.uu.net internet address = mail.uu.net internet address = mail.uu.net internet address = mail.uu.net internet address = mail.uu.net internet address = mailgate2.microstrategy.com internet address = mailgate.microstrategy.com internet address = :\> n this example, mailgate2.microstrategy.com is the preferred mail server for the domain microstrategy.com. You might see something like the following: 66 hapter 3 onfiguring Machines

87 :\>nslookup -type=mx a.com D request timed out. timeout was 2 seconds. *** an't find server name for address : imed out *** Default servers are not available erver: UnKnown Address: D request timed out. timeout was 2 seconds. *** o mail exchange (MX) records available for a.com :\> his means that either the domain does not exist, a timeout was longer than expected, or there is a D configuration issue on that particular machine. heck for typing errors and try it again. f you do not get an answer, you need to verify the D configuration on that machine. teps to test connection to mail server When typing during the M connection, what you type is not displayed while you type it. f the D is working correctly or your information transmitter is configured to use only a smart host, you can test the connection to the mail server or the smart host. 1. ype the following at the command line: :\>telnet server port where server is the desired mail server to connect to and port is the ort used for M delivery (the standard port is 25). For example: :\>telnet mailgate2.microstrategy.com A telnet window opens. t either establishes the connection or returns an error message. A successful connection starts with a 220 string, similar to the following: 220 mailgate2.strategy.com M erver (Microsoft xchange nternet Mail ervice ) ready etting up arrowcast erver for transmission 67

88 An error message means that you could not establish a connection to the specified server. his can be because the server is not available, or because you could not reach the server within the timeout period. 3. o disconnect, type QU and press R. teps to test delivery status notification nce you establish communication to a remote server, you can test to see if this particular server supports the Delivery tatus otification (D) option. 1. After you connect to the server, type: HL your domain and press R. For example: HL microstrategy.com 2. ne of the following support possibilities now exist: he server supports HL and D. he server supports HL, but does not support D. he server does not support HL. o determine support, look at the response to the HL command and look for the D response (it should resemble 250-D ). For example: 250-mailgate2.strategy.com Hello your machine name 250-XXH HL 250-R 250-D 250-Z AUH LG 250 AUH=LG 3. ompare the response you are seeing to the options below: f you received the 250 response to the HL command but do not see a D line, the mail server you connected to does not support delivery status notification. f you received a 500 error, the mail server you connected to does not support the HL (-M) protocol. n this case, use the HL (M) protocol to connect to the mail server. ype: HL your domain and press R to continue. he response should resemble this: 68 hapter 3 onfiguring Machines

89 220 **************************************** HL microstrategy.com 500 ommand unrecognized: "XXXX microstrategy.com" HL microstrategy.com 250 Hello your machine name, pleased to meet you You should see a line that begins with 250. f you see a 5XX or 4XX line, the M protocol has failed or been rejected. teps to send a test message nce you have connected and determined whether or not you can use D or -M, you can send a test message. he steps below are followed by an example showing what to type for each step. ote the following: Any text you type is not displayed on the screen. f you type something incorrectly or the command fails, you see a 5XX line and usually a short description of the problem. f there was a typing mistake, use this information to correct the problem. f there was a failure, it might indicate that arrowcast erver cannot transmit to this e- mail server. Use that information to fix the problem when possible. A 4XX line is a temporary failure. Wait a few minutes, then try again. 1. Use the FRM command to specify who is sending the . he syntax for D-compliant systems is: MAL FRM: <sender address> R=HDR VD=d he syntax for non-d-compliant systems is: MAL FRM: <sender address> where sender address is the sender address (always type the angle brackets around it), and d is the D D (type a single word as the d). 2. Use the R command to specify the recipient addresses. You can repeat this command as many times as the server allows. he limit for most servers is 100 recipients per message. etting up arrowcast erver for transmission 69

90 f this command fails, it means that the last recipient you typed fails to receive the message, but any other recipient that returned a 250 response receives message successfully. his command only fails if all the recipients failed. he syntax for D-compliant systems is: R : <recipient_ _address> FY=dsn_ptions he syntax for non-d-compliant systems is: R : where recipient_ _address is the sender address (always type the angular brackets around it) and dsn_ptions is one of the following strings: U FALUR U, FALUR VR 3. Use the DAA command to send the message text. ype the following: DAA and press R. he response should be a 354 line. ype any message text you want, and end by pressing R, typing a period (.), and pressing R again. 4. Wait for the AK (acknowledgement) of the message. f it was successfully sent, you will receive a 250 line. therwise, use the information to determine the cause of failure. 5. ype quit and press R. his closes the connection. xample n the following example, the text you type is in bold. he R key is represented by <nter>. telnet mailgate2.microstrategy.com 25<nter> 220 mailgate2.strategy.com M erver (Microsoft xchange nternet Mail ervice ) ready HL microstrategy.comp<nter> 250-mailgate2.strategy.com Hello your machine name 250-XXH HL 250-R 250-D 250-Z AUH LG 250 AUH=LG 70 hapter 3 onfiguring Machines

91 MAL FRM: R=HDR VD=My_id<nter> 250 K - mail from R : FY=U<nter> 250 K - Recipient DAA<nter> 354 end data. nd with RLF.RLF end any message here<nter>.<nter> 250 K QU<nter> 221 closing connection etting up arrowcast erver for file transmission arrowcast erver provides a File nformation ransmission Module (File M) that can transmit files to multiple network locations, such as networked computers and remote servers. he File information transmitter enables administrators and users to define and select locations for transmitting service files from arrowcast Administrator and the ubscription ortal. You can define the file delivery locations for users as follows: f you have users who save files on the network, define the file locations that specify the target computers and other properties, such as whether files with the same name are overwritten. f you have users who transmit files directly to network locations, create a device that allows users to fully specify their desired file locations. File information transmitters are automatically configured by arrowcast erver. A central administrator can control file transmissions, define all devices and service recipients, and transmit reports in batches to personalized locations on a scheduled basis. Details about the various set up scenarios for file transmissions are described below. Defining file delivery locations File delivery locations can be defined by the administrator or by the user. he degree of definition and control can vary, depending on what is desired and the roles of the administrator and the different user groups. etting up arrowcast erver for file transmission 71

92 You can also define a delivery location along with a set of delivery options, and save these as an address. For details, see Defining file delivery location and settings: Addresses. Administrator-defined file locations When an administrator defines file delivery locations, users can either select those file locations from a list and provide a file name, or users can have a single location defined for them to deliver all messages to. o provide a list of files locations that users can select from, you define one or more devices to represent defined network locations. elect these devices in the corresponding ubscription ortal delivery service and ensure that the ubscription ortal users have the required privileges. ubscription ortal users can select a file location but not specify any file transmission options. All users in the same project have access to the same file locations. o provide a single file location for each user, define one or more devices to represent network locations, then apply one of these devices to each end user. he users select a device for file transmission and the service is sent to the specified file location with no additional input. his procedure can also be used to set up batch file transmission to a centralized network location. User-provided file paths ubscription ortal users can be allowed to specify or select delivery locations. You define one or more devices to represent network locations and define one or more devices that enable users to type full network paths. o do this, add the macro UserAddress in the device definition in place of the path. For information on macros, see Dynamically generating file or folder names: Macros, below. Users can subscribe to services using the ubscription ortal and send results to a file. You define one or more devices to represent network locations and make these devices available via the ubscription ortal. hese devices can define delivery locations or can define devices that allow user addresses to define delivery locations. ombining administrator-defined and user-provided paths You might want to give some ubscription ortal users the option to select an existing file location or enter their own. Depending on the definition of the device that is chosen, users are provided with different options. f a 72 hapter 3 onfiguring Machines

93 fully-defined path is defined for users, no file path field is provided. f a user-defined file location is allowed, a field is available in which the user can enter a file path. f only one device is provided, no field is provided. You enable the options available to each user by creating devices that provide the desired functionality, and then controlling which devices each user can access.you can also define a different set of devices available to ubscription ortal users. Dynamically generating file or folder names: Macros You can add file and folder name information that is dynamically generated at the time of delivery. For example, a user might want to add the date and time to a folder or to the saved file name, or an administrator might want to deliver files to many users in folders named after each user. o do this, define macros in devices or addresses. xamples of macros include the date, time, user information such as user name, Ds that are unique for each delivery, and application information such as service or arrowcast document name. A user s physical address can provide a relative path; to do this, the address information is used as a macro. ontrolling device default settings You can control how files are saved. For example, you might want to ensure that all files saved to a certain location are saved as read-only files. o do this, define default delivery settings at the device level, which are applied when the device is selected. his allows you to define different sets of defaults that can be applied to different delivery locations. nabling users to define file delivery options You can allow users to define how files are saved. You can also control user access to delivery options. For example, some delivery locations can be defined to allow users to control whether files are read-only, while other delivery locations can require files to be saved as read-only by default. ome users can have the privilege to set delivery options while other users may not have the ability to change any delivery options. o do this, when you define device settings you can determine which ones are exposed to users. You can also define user privileges that allow certain users to have the privilege to define delivery options. etting up arrowcast erver for file transmission 73

94 Defining file delivery location and settings: Addresses Devices allow you to reuse delivery locations and delivery settings across users. n some cases, users might want to define a delivery location and delivery settings that are reusable by them but not by other users. For example, a user might want to define a delivery location for his two Desktop machines and how to save these files, but not make these locations available to other users. his can be accomplished using addresses. Addresses allow users or administrators to define delivery locations and accompanying delivery settings that can be reused across subscriptions for a single user but not across users. A user-defined delivery location always becomes the address for a subscription. ote the following: User-defined relative paths should only be provided when the device providing the corresponding absolute (base) path is selected. User-entered paths can be stored either as addresses or as subscription settings. toring them as addresses allows them to be reused across subscriptions and retrieved easily for viewing and selection. Using addresses to store delivery locations affects the following: For administrator-defined delivery locations that users select in the ubscription ortal, no physical address exists or is needed. For user-defined file paths that users provide in the ubscription ortal, a physical address represents a fully-defined delivery location. For administrator-defined and selected delivery locations and for ubscription ortal users, a physical address can be used in either case. Windows authentication and file transmission he File nformation ransmitter runs under the same Windows account as the Microtrategy xecution ngine service. f the xecution ngine is running under a Windows domain account, the File nformation ransmitter can deliver files to any network machines for which this account has the required permissions. 74 hapter 3 onfiguring Machines

95 ne way to ensure that arrowcast erver can deliver files within your network is to ensure that the xecution ngine is running under a Windows domain account that has permissions on all machines where delivery is required. n this way no other authentication needs to be defined. f a mapped network drive is used to deliver files to networked computers in the Windows file system, the Windows account under which the mapped network drive is created must be the same as the administrative account for arrowcast erver. etting up arrowcast erver for printing arrowcast erver provides a rint nformation ransmission Module (rint M) that can send multiple files to networked printer locations. he rint information transmitter enables administrators and users to define, select, and schedule batch printing requests from arrowcast Administrator and the ubscription ortal. You can define the printer location for users as follows: f you have users who print information on shared printers, define printer locations that specify the target printers and other options, such as the type of printer. f you have users who print information directly to a single specified printer, create a device that allows users to specify printer location. rint information transmitters are automatically configured by arrowcast erver. An administrator can control file prints, define all devices and service recipients, and print reports in batches to personalized locations on a scheduled basis. Details about the various set up scenarios for print transmissions are described below. Delivery location definition rinter delivery locations can be defined by the administrator or by the user. he degree of definition and control can vary, depending on what is desired and the roles of the administrator and the different user groups. You can also define a delivery location along with a set of delivery options, and save these as an address. For details, see Defining printer delivery location and settings: Addresses. etting up arrowcast erver for printing 75

96 Administrator-defined printer locations When an administrator defines printer delivery locations, users can either select those printer locations from a list, or users can have a single printer location defined for them to deliver all print messages to. o provide a list of printer locations that users can select from, you define one or more devices to represent defined printer locations. elect these devices in the corresponding ubscription ortal delivery service. ubscription ortal users can select a predefined printer but not specify any print options. All users in the same project have access to the same printer locations. o provide a single printer location for each user, define one or more devices to represent network printer locations, then apply one of these devices to each end user. he users select a device for print transmission and the service is sent to the specified printer location with no additional input. his procedure can also be used to set up batch print transmission to a centralized network location. User-provided printer locations ubscription ortal users can be allowed to specify or select printer locations for messages to be delivered to. You define one or more devices to represent printer locations and define one or more devices that enable users to type printer locations. o do this, select the option to enable users to define printer locations to override device-level defaults. Users can subscribe to services using the ubscription ortal and send results to a printer. You define one or more devices to represent printer locations and make these devices available via the ubscription ortal. hese devices can define print locations or can define devices that allow user addresses to define delivery locations. roperty settings for the printer defined by the user are overridden by those of the default printer set by the administrator. t is possible that settings for paper source, print quality, and paper size may not match the capacities of the user s printer, depending on its make and model. esting is recommended if a single device is used for different types of printers. ombining administrator-defined and user-provided paths You might want to give some ubscription ortal users the option to select an existing print location or enter their own. Depending on the definition of the device that is chosen, users are provided with different options. f a fully-defined path is defined for users, no file path field is provided. f a 76 hapter 3 onfiguring Machines

97 user-defined file location is allowed, a field is available in which the user can enter a file path. f only one device is available to users, no field is provided. You enable the options available to each user by creating devices that provide the desired functionality, and then controlling which devices each user can access.you can also define a different set of devices available to ubscription ortal users. ontrolling device default settings You can control how files are printed. For example, you might ensure that all print jobs are collated or printed from a certain printer tray. o do this, define delivery settings at the device level, which are applied when the device is selected. his allows you to define different sets of defaults that can be applied to different printer locations. ettings for DF documents only take effect if Adobe Acrobat is installed on all execution engine machines. nabling users to define printer locations You can allow users to define where files are printed. f a user-specified printer does not support the printer properties of the device that is used to send the message, unexpected behavior can occur for the following printer properties: rint quality aper source aper size ollate rinter behavior is dictated by the printer capabilities and the printer manufacturers standards. For example, if the device is set to use aper ource: ray 2, but the user-specified printer has only one tray, the printer might default to tray 1 or fail the job, depending on how it is configured. o prevent problems, you can create multiple devices to accommodate the different types of printers used in the organization or have users test their print delivery services. etting up arrowcast erver for printing 77

98 Defining printer delivery location and settings: Addresses Devices allow you to reuse printer locations and delivery settings across users. n some cases, users might want to define a printer location that is reusable by them but not by other users. his can be accomplished using addresses. Addresses allow users or administrators to define printer locations and accompanying delivery settings that can be reused across subscriptions for a single user but not across users. A user-defined delivery location always becomes the address for a subscription. User-defined printer locations, which are equivalent to the physical address, can then be displayed by the ubscription ortal in the same list that provides the list of available addresses. User-defined printer locations can be stored only as addresses. toring them as addresses allows them to be reused across subscriptions and retrieved easily for viewing and selection. Windows authentication and printing he rint M runs under the same Windows account as the Microtrategy xecution ngine service. f the xecution ngine is running under a Windows domain account, the rint M can back up files to any network machines for which this account has the required permissions. ne way to ensure that arrowcast erver can save files to a backup location within your network is to ensure that the xecution ngine is running under a Windows domain account that has permissions on all machines where backup is required. n this way no other authentication needs to be defined. f a mapped network drive is used to back up files to networked computers in the Windows file system, the Windows account under which the mapped network drive is created must be the same as the administrative account for arrowcast erver. etting up arrowcast erver for text (M) transmission hort message service (M) is a text messaging service available on wireless telephones. elephone numbers are used for addressing M messages to the recipients. 78 hapter 3 onfiguring Machines

99 hese messages can be sent from messaging systems such as arrowcast erver to mobile telephones using an M center (M) provided by wireless carriers and M messaging providers. he following diagram shows a typical M architecture including arrowcast erver. arrowcast erver M over / ervice rovider etworks ross-network connections M Messaging rovider M onnections to messaging providers are typically handled over standard protocols such as / and M messaging protocols such as hort Message eer to eer (M) protocol. arrowcast erver implements the M protocol for transmitting M messages to the M. o successfully send M messages, a connection to an M is required. M messaging typically has fees associated with sending messages. hose fees vary by M messaging provider and by the volume of M messages. For details, see the arrowcast erver Application Designer Guide. etting up arrowcast erver for text (M) transmission 79

100 onfiguring the Microtrategy Logging erver Microtrategy arrowcast erver includes a comprehensive logging system that provides the ability to capture and store a wide variety of system-related information. his system collects information such as: tatistical information on transmission success or failure at the recipient level, Administration and service execution related events and error messages, and tatus updates for services, segments and transmissions. An open architecture allows this information to be used for a wide variety of purposes such as logging to flat files, logging to databases, sending messages to the Windows event viewer, displaying in an error display, or integrating with third party applications. he arrowcast erver logging infrastructure includes five types of components: Microtrategy Logging lients (MLs) Microtrategy Logging ervers (MLs) Microtrategy Logging Modules (MLMs), such as the Microtrategy Logging onsumer Microtrategy Database Logger Microtrategy Distributed Logger nformation logging begins with the Microtrategy Logging lients. Microtrategy Logging lients (MLs) are created on every machine in a arrowcast erver system. MLs receive logging messages from the arrowcast erver components, such as distribution managers and relay those messages to the Microtrategy Logging erver (ML). he ML serves as a central point to collect these messages. he ML is usually created on only one machine in the arrowcast erver system (although it might be created on multiple machines for redundancy or implementations that require logging large amounts of information). Logging messages of all types including segment processing status, statistical information, and error notifications pass through the ML. Microtrategy arrowcast erver also includes a buffer port that you can use for sending messages to the buffer. hese messages are viewed by arrowcast Administrator. A Microtrategy Logging Module (MLM) can then subscribe to receive information from the ML and use this information for any purpose such as logging to flat files, logging to databases, sending messages to the Windows event viewer, displaying in an error display, or integrating with third party applications. he Microtrategy Logging Module ervice 80 hapter 3 onfiguring Machines

101 rovider nterface is an open component specification that enables custom MLMs to connect to and receive messages from the Microtrategy Logging erver. You can use Microtrategy Distributed Logger and Microtrategy Database Logger to display the time zone in U by modifying the registry keys. he Microtrategy Database Logger controls the time zone for transmission recording tables in the repository. he Microtrategy Distributed Logger controls the time zone for DLog files and ystem Message Viewer. o learn more about the Microtrategy Logging Module ervice rovider nterface, refer to Microtrategy Logging Module Directory in the online arrowcast erver DK Guide. Microtrategy Logging lient operation he amount and type of log messages a specific Microtrategy Logging lient (ML) submits to the Microtrategy Logging erver can be controlled through registry keys on individual machines in the arrowcast erver system. his can be used to control the number of messages that are generated and the type of information that is provided to the Microtrategy Logging erver. he registry keys to control ML logging are located on each ML machine under My omputer\hky_lal_mah\fwar\ Microtrategy\ Microtrategy Broadcast erver\ 7.0\Distributed Logging ervice\ ML lient ettings\logging Levels By default, the Microtrategy Logging lient has all flags turned on with exception of the LVL_RA_xxxxx and LVL_DBUG flags. ote that the trace and debug logging options generate a very large amount of information and should only be used for debugging purposes with the help of Microtrategy echnical upport. f the Microtrategy Logging lients log trace and debug information (LVL_RA, LVL_RA_XXXX, LVL_DBUG or LVL_A_R), performance degradation and increased U utilization will typically result. f changes are made to any of the registry values for the logging system, the respective Microtrategy logging services must be restarted by using the ervices manager in the ontrol anel. For more information on these logging levels, refer to Logging levels in this chapter. ote that the levels at which the Microtrategy Logging lient logs information are independent of the levels at which the Microtrategy Logging onsumer subscribes to receive information. By default, the onfiguring the Microtrategy Logging erver 81

102 Microtrategy Logging onsumer subscribes to all logging levels. Also note that a Microtrategy Logging lient must be running on each primary distribution manager, backup distribution manager, execution engine, and the arrowcast Administrator machine. he ystem onfiguration Wizard and the tutorial configuration process automatically establish this requirement. Microtrategy Logging erver operation he Microtrategy Logging erver (ML) collects the logged messages from Microtrategy Logging lients and distributes them to any available Microtrategy Logging Modules. he ML does this through a publish and subscribe architecture, in which multiple MLMs can ask for various different types (for example, errors, statistics, or status) and levels (for example, critical, high, medium, or low) of information. For example, MLMs could deliver data to the Windows event viewer, a logging database, a set of flat files, or a display interface. n addition, note that one or more machines can be designated as a Microtrategy Logging erver. he Microtrategy Logging erver can be placed on a separate machine or on a machine with any other arrowcast erver system component, such as an execution engine or distribution manager. n systems with large clusters or heavy logging requirements, such as message-level logging, the ML machines should have two or more processors and at least 128 MB of RAM. U and RAM consumption by the ML is proportional to the number of MLMs connected to the ML. f high availability is a requirement, two or more logging servers can be employed. he ML machines must be specified when the arrowcast erver system is configured. Microtrategy Logging Module operation A Microtrategy Logging Module (MLM) is a component that subscribes to the Microtrategy Logging erver and instructs the ML to notify the MLM of specific types of events. hese events can include various levels of errors, recipient tracking information, segmentation information, and system diagnostic information. Logging modules can process these events in a variety of ways such as: Writing the information to a log file or database ending the information to the Windows event viewer or an error display interface ntegrating with an external application 82 hapter 3 onfiguring Machines

103 Microtrategy arrowcast erver ships with a standard logging module named the Microtrategy Logging onsumer. his standard MLM can output to a cyclic log file (D-ddmmyy.log) or a debug tool such as Monitor.exe or DebugViewer.exe. ther Microtrategy Logging Modules can be created to use this information for application-specific purposes. By default, the Microtrategy Logging onsumer subscribes to every type of message and sends all the received messages to the log files in the directory location where MLogon.exe is located. his location can be changed by creating a Log File ath string key (complete with spaces) in the registry under: Myomputer\HKY_LAL_MAH\FWAR\ Microtrategy\Microtrategy Broadcast erver\ 7.0\Distributed Logging ervice\ Loggingonsumer\Log File ath Registry settings can also be used to control the locations to which the standard Microtrategy Logging onsumer sends logged messages. hree registry keys at the following location can be used to determine whether the standard Microtrategy Logging onsumer sends log messages to file, to event viewer, or to debug viewer. Myomputer\HKY_LAL_MAH\FWAR\ Microtrategy\ Microtrategy Broadcast erver\ 7.0\Distributed Logging ervice\loggingonsumer he registry key UU DBUG instructs the onsumer to send all received messages to the debug viewer on that machine. et this key to 1 to enable or 0 to disable this functionality. he registry key UU FL instructs the onsumer service to send all received messages to the cyclic log files on that machine. et this key to 1 to enable or 0 to disable this functionality. he registry key UU V_VWR instructs the onsumer service to send all received LVL_XXXX_RRRs (and only errors) to the Windows vent Log on that machine. et this key to 1 to enable or 0 to disable this functionality. By default, only UU FL is set to 1; the others are set to 0. For distributed environments, it might be desirable to configure a Microtrategy Logging onsumer that connects to a Microtrategy Logging erver on another machine. Doing so enables recording of logging information remotely, for monitoring and archiving purposes. his can be done by setting the Hostname of ML string at the following location key to the name of the remote machine on which Microtrategy Logging erver is running: onfiguring the Microtrategy Logging erver 83

104 Myomputer\HKY_LAL_MAH\FWAR\ Microtrategy\Microtrategy Broadcast erver\ 7.0\Distributed Logging ervice\loggingonsumer nce this is done, this remote machine must have both the ML and the Microtrategy Logging onsumer running, but only the onsumer is used. ubsequent changes to the / ports used for logging messages are not propagated to this remote machine. hanging the log file naming format he standard format for the log file name is DLog yyyy-mmddhh_mm_ss. X. With the help of Microtrategy Logging onsumer, you can change the file naming format of the log files. o change the file name prefix, date, and time, perform the following steps: 1. Browse to the location: HKY_LAL_MAH\oftware\Microstrategy 8\ Microstrategy Broadcast erver\7.0\ Distributed Logging ervice\logging onsumer\ File ame ptions. 2. hange the value of the File ame Date-ime Format registry key to the required format. 3. hange the value of the File ame refix registry key to the required format. 4. lick K. he Logging onsumer uses the time format as specified by the user on the xecution tab in ystem ettings (see ystem ettings dialog box layout). f you select GM from the ime Zone for ystem nformation drop-down list on the xecution tab in ystem ettings, the log file has the Universal ime oordinates (U) by default. f a different time zone is to be used, you can modify the UseU registry key value to 0. he ystem Message Viewer is also a logging module for the Microtrategy Logging erver. Refer to chapter 23, ystem Message Viewer Dialog Box and Viewing system messages in chapter 4 for more information about using the ystem Message Viewer. he Microtrategy Logging Module interface is described in the online arrowcast erver DK Guide. his interface allows any external application to integrate with Microtrategy arrowcast erver and use the logging information generated by a arrowcast erver system. his external application perform tasks including the following: 84 hapter 3 onfiguring Machines

105 arry out custom filtering and event monitoring. ake action based on events. All logging components create their own registry keys if they do not exist the first time they are run on a particular machine. he only keys that are not created are the keys within My omputer\hky_lal_mah\fwar\ Microtrategy\ Microtrategy Broadcast erver\ 7.0\Distributed Logging ervice\ ML lient ettings\ml ervers\erver 1 hese keys inform the Microtrategy Logging lient where and how to connect to the Microtrategy Logging erver. he folder is typically called erver 1 (as shown), and is created by the ystem onfiguration Wizard and the tutorial configuration process. he values created in this folder will be Hostame, MaxRetryimeut, and erverupplierort. he defaults for these values are localhost, 32, and port f a different MLM connection is desired, these keys can be deleted and a new erver 1 key can be created with the appropriate three keys. Microtrategy Database Logger he Microtrategy Database Logger controls the time zone for transmission recording tables in the repository. n Microtrategy arrowcast erver 8.1.1, all the timestamps match the time zone specified by the user on the xecution tab in ystem ettings (see ystem ettings dialog box layout). o use the Universal ime oordinates (U) as the default value, you can modify the registry key values. f changes are made to any of the registry values for the logging system or the time zone settings on the xecution tab, the required Microtrategy logging services must be restarted by using the ervices Manager from the ontrol anel. For more information on these logging levels, refer to Logging levels in this chapter. o change the registry key value, perform the following steps: 1. Browse to the location: HKY_LAL_MAH\oftware\Microstrategy 8\ Microstrategy Broadcast erver\7.0\ Distributed Logging ervice\db Logger. 2. et the value of the UseU registry key to 1. lick K. onfiguring the Microtrategy Logging erver 85

106 ote the following: f you set the value of the UseU registry key to 0, the user-specified time zone is used. Modifying the registry values incorrectly can cause serious, systemwide problems that might require the re-installation of the operating system. Any edit of the registry is done at the user s own risk. ince these are user-initiated changes they are not covered by any Microtrategy warranty. Users should back up their registry or update an mergency Repair Disk prior to alterations. Microtrategy Distributed Logger he Microtrategy Distributed Logger controls the time zone for DLog files and the ystem Message Viewer. n Microtrategy arrowcast erver 8.1.1, all the timestamps match the time zone specified by the user on the xecution tab in ystem ettings (see ystem ettings dialog box layout). You can modify the registry key values to use the Universal ime oordinates (U) as the default value. You should restart the required Microtrategy logging services by using the ervices Manager from the ontrol anel after modifying the registry values or the time zone settings on the xecution tab. o change the registry key value, perform the following steps: 1. Browse to the location: HKY_LAL_MAH\oftware\Microstrategy 8\ Microstrategy Broadcast erver\7.0\ Distributed Logging ervice\distributed Logger. 2. et the value of the UseU registry key to 1. lick K. ote the following: f you set the value of the UseU registry key to 0, the user- specified time zone is used. Modifying the registry values incorrectly can cause serious, systemwide problems that might require the re-installation of the operating system. Any edit of the registry is done at the user s own risk. ince these are user-initiated changes they are not covered by any Microtrategy warranty. Users should back up their registry or update an mergency Repair Disk prior to alterations. 86 hapter 3 onfiguring Machines

107 Logging levels he Microtrategy Logging lient can log a wide variety of information indicating different levels of errors, statistical information at the service, segment or recipient level, or information from all administration components. n most implementations, only a small amount of the available information is required. he Microtrategy Logging lient logging settings can be used to control how much information each machine in a Microtrategy arrowcast erver system logs. hese settings must be set on each machine in the cluster since the registry settings on each machine only impact the Microtrategy arrowcast erver system components on that machine. he following logging levels can be set to 1 (on) or 0 (off) under Myomputer\HKY_LAL_MAH\FWAR\ Microtrategy\Microtrategy Broadcast erver\ 7.0\Distributed Logging ervice\ ML lient ettings\logging Levels All Level_nfo_xxxx levels are enabled by default. Logging nformation Key ame nformation Description rror Messages: ystem Wide Failure rror Messages: ervice or Machine Failure rror Messages: Recipient Group Failure rror Messages: Recipient Level Failure or emporary Failure nformation Messages: ervice xecution nformation nformation Messages: egment xecution nformation ther Debugging Messages: Recipient Level Level_ritical_rror Level_evere_rror Level_Moderate_rror Level_Minor_rror Level_tat_xecution Level_tat_egment Level_tat_Recipient omplete system failure. ndicates the inability of the arrowcast erver system to function. he failure of a sole running distribution manager (no backup) or loss of connection to the repository could cause this error. High-level system failure. hese errors generally pertain to an entire service. onnection to the ubscription Book Module is lost, there are execution engine or distribution manager failures, or no D is found on a machine. Mid-level system error. hese errors generally pertain to multiple recipients, such as at the segment level. here are information source manager, information transmission module, document formatter module failures. Lowest-level system error. hese errors generally pertain to a single recipient. his indicates that Microtrategy arrowcast erver is unable to send to a recipient or that an information object for a recipient has failed. ervice-level tracking information. egment-level tracking information. Recipient-level tracking information. onfiguring the Microtrategy Logging erver 87

108 Logging nformation Key ame nformation Description ther Debugging Messages: ustomer pecific atch Level_Debug Very low-level diagnostic information used internally to track down issues or diagnose any potential problems. ome components generate vast amounts of information. omponent Level nformation: ther omponents omponent Level nformation: Document Formatting Modules nformation Messages: ystem nformation omponent Level nformation: xecution ngine omponent Level nformation: xecution Recorder omponent Level nformation: nformation ource Modules omponent Level nformation: nformation ransmission Modules omponent Level nformation: ubscription Book Module omponent Level nformation: egment xecutor omponent Level Debugging: ther omponents omponent Level Debugging: Document Formatting Modules omponent Level Debugging: Distribution Manager omponent Level Debugging: xecution ngine omponent Level Debugging: xecution Recorder omponent Level Debugging: nformation ource Modules omponent Level Debugging: nformation ransmission Modules Level_nfo Level_nfo_DFM Level_nfo_DM Level_nfo_ Level_nfo_R Level_nfo_M Level_nfo_M Level_nfo_BM Level_nfo_ Level_race Level_race_DFM Level_race_DM Level_race_ Level_race_R Level_race_M Level_race_M nformation relating to the general operation of Delivery ngine. Any components that do not have their own specific Level_nfo_xxxx level log at this level (for example, the M service). General operational messages from the document formatting module. General operational messages from the distribution manager (for example, system startup/shutdown, highlevel notification of service execution). General operational messages from the execution engine. General operational messages from the execution recorder. General operational messages from the information source module. General operational messages from the information transmission module. General operational messages from the ubscription Book Module. General operational messages from the segment executor. Low-level functional tracing information. Any components that do not have their own specific Level_race_xxxx ill log at this level. Low-level tracing information for the document formatting module. Low-level tracing information for the distribution manager. Low-level tracing information for the execution engine. Low-level tracing information for the execution recorder. Low-level tracing information for the information source module. Low-level tracing information for the information transmission module. 88 hapter 3 onfiguring Machines

109 Logging nformation Key ame nformation Description omponent Level Debugging: ubscription Book Module Level_race_BM Low-level tracing information for the ubscription Book Module. omponent Level Debugging: cheduler omponent Level Debugging: egment xecutor Level_race_H Level_race_ Low-level tracing information for the scheduler. Both the distribution manager and the arrowcast Administrator generate messages at this level. his details schedule construction, parameters passed to the scheduler from the repository as well as general execution flow details of the scheduler. t includes both local and Universal ime oordinates (U) dates and times for most operations. Low-level tracing information for the segment executor. ther Debugging Messages: QL Messages ote Modifying Level_race_QL Low-level QL tracing generated by the arrowcast erver As. the following: he logging services do not log errors themselves as this could result in an infinite loop of attempts to log the inability to log messages. o see logging service error information, the logging services need to be run as applications. Users can edit the startup options for these from the ontrol anel ervices manager or edit the startup options from the Run command using the following commands: for the Logging erver: MLogvc.exe -b -d - for the Logging lient: MLogvc.exe -b -d for the onsumer: MLogon.exe -d Both the Microtrategy Logging erver and Microtrategy Logging lients run as Windows services that are automatically started under the local system account. registry values incorrectly can cause serious, system-wide problems that might require the reinstallation of the operating system. Any edit of the registry is done at your own risk. ince these are user-initiated changes they are not covered by any Microtrategy warranty. You should back up your registry and/or update an emergency repair disk prior to making alterations. onfiguring the Microtrategy Logging erver 89

110 90 hapter 3 onfiguring Machines

111 4 ystems HAR 4 4.Administering Recording transmission information t is useful to be able to determine what services arrowcast erver has delivered, when they were delivered, to whom they were delivered, and what was in the messages. For example, by knowing who received services, it is easy to see how broadly information is being distributed. By knowing whether or not messages were sent successfully, it is possible to determine whether addresses in the ubscription Book are invalid, and if so, how many. imilarly, it is easy to determine what portion of a user population received a service through one medium, such as versus some other medium, such as the ubscription ortal. Microtrategy arrowcast erver provides the ability to record information about transmitted messages. For any given message, this information consists of: What message was sent Who received the message Whether or not the message was sent successfully When the message was sent Why the message was sent How the message was sent his information is written into six tables located in the ubscription Book Repository. You can run QL queries against these tables to retrieve this information, by joining them to the other tables in the ubscription Book Repository and the bject Repository. Because the tables used for transmission recording store the D values for objects, such as services, you should define your system so that the bject Repository and the ubscription Book Repository are in the same location if you intend to use this feature. 91

112 f the subscription D specified in the ubscription Book Repository is greater than 2,147,483,647, the ransmission Recorder does not save any records and an error is displayed. ransmission recording can be turned on through arrowcast Administrator. For steps to turn on the transmission recording, see urn transmission recording on. he state of transmission recording cannot be changed for a service that is already executing. When transmission recording is off (the default setting), no data is written into the tables. However, when transmission recording is on, data is written into the tables in the ubscription Book Repository. he definitions of these tables and the information contained within them is provided as follows. ote the following: All columns have the prefix MR_ to prevent future name conflicts with database reserved words. he columns in bold form the primary key of these tables. able: <prefix>mrlgv (Log ervice) olumn ype ontains VX_D string(32) ervice execution D, a 32-character string representing a globally-unique identifier in hexadecimal format (GUD-string). his uniquely identifies this execution of this service. V_D string(32) ervice D, a GUD-string that uniquely identifies this service within this system. XX_D string xternal execution D, a string that can be specified in the A call to run a service immediately, for the purpose of relating this execution to events in external systems. VX_ timestamp ervice execution timestamp, a date-time value representing the time at which service execution began, expressed in the time zone specified by the user. VXR_ timestamp ervice expiration timestamp, a date-time value representing the time at which this service execution will expire as specified by the user. VML_ timestamp ervice completion timestamp, a date-time value representing the time at which this service execution completed or halted, expressed in the time zone specified by the user. 92 hapter 4 Administering ystems

113 olumn ype ontains VX_A integer ervice execution status, a 4-byte integer indicating the status of the execution of the service. UB_D string(32) ubscription et D, a GUD-string that uniquely identifies the subscription set being used for this service execution. HD_D string(32) chedule D, a GUD-string that uniquely identifies the schedule that caused this service execution, when applicable. VR integer ervice priority, a 4-byte integer indicating the priority of the service. G_U integer egment count, a 4-byte integer indicating the number of segments in this service execution. Y_D string(32) ystem D, a GUD-string that uniquely identifies the system executing the service. DMGR_D string(32) Distribution Manager D, a GUD-string that uniquely identifies the machine within a system that is the rimary Distribution Manager handling this execution of the service. o view the name of the service instead of or in addition to the GUD, you can join this table to the MRBJAM (bject ames) table in the bject Repository, using the following QL statement: select t1.mr_bj_am A RV_AM, t2.* from <prefix>mrbjam t1, <prefix>mrlgv t2 where t1.mr_bj_d = t2.mr_v_d and MR_LAL_D = 'FBBF713711D F48F8FD' he Locale D in the QL statement above represents the ystem Locale D, and has the same value in every system. imilar joins can be performed to return the names of the schedule, subscription set, system, and distribution manager, if desired. he MR_VX_A column typically holds one of five values: 65536: ervice execution initiated. Beginning segmentation : ervice segmentation complete. Beginning segment execution : ervice execution complete : ervice execution cancelled : ervice execution failed. Recording transmission information 93

114 As a result, each service execution generally results in the insertion of three records into the Log ervice table. By filtering on the value in this column in a QL where clause, you can control which type of service execution activity you retrieve by your query. able: <prefix>mrlgmg (Log Message) olumn ype ontains UB_D integer ubscription D, a 4-byte integer that uniquely identifies a subscription within a subscription set. VX_D string(32) ervice execution D, a GUD-string that uniquely identifies this execution of this service. R_Q_GUD string(32) A unique value to distinguish between multiple failed attempts to transmit a message. LAL_D string(32) Locale D, a GUD-string that identifies the locale preference of the recipient of this message. UB_D string(32) ublication D, a GUD-string that identifies which publication was sent to this recipient of the message. RA_ timestamp ransmission timestamp, a date-time value representing the time at which the message was transmitted (or failed), expressed in the time zone specified by the user. UR_D string(32) User D, a GUD-string that identifies the user in the ubscription Book to which the message was sent. ADDR_D string(32) Address D, a GUD-string that identifies the address in the ubscription Book to which the message was sent. DV_D string(32) Device D, a GUD-string that identifies the type of device to which the message was sent. HYAL_AD string hysical Address, a string representing the actual address of the recipient. AU integer tatus, a 4-byte integer indicating the success or failure of the transmission of the message. o view the name of the recipient instead of or in addition to the GUD, you can join this table to the <prefix>mrur (Users) table in the ubscription Book Repository, using the following QL statement: select t1.mr_ur_am A URAM, t2.* from <prefix>mrur t1, <prefix>mrlgmg t2 where t1.mr_ur_d = t2.mr_ur_d 94 hapter 4 Administering ystems

115 imilar queries can be run to return other information about the user, address (by joining to <prefix>mraddr.mr_addr_d) or subscription (by joining to <prefix>mrubr.mr_ub_d. o retrieve the name of the locale, publication or device, join to the <prefix>mrbjam table as above, using QL similar to the following: select t1.mr_bj_am A LAL_AM, t2.* from <prefix>mrbjam t1, <prefix>mrlgmg t2 where t1.mr_bj_d = t2.mr_lal_d and t1.mr_lal_d = 'FBBF713711D F48F8FD' he Locale D constant above represents the ystem Locale D, and has the same value in every system. he MR_AU column typically holds one of three values: 0: he message was successfully transmitted. 1: Message transmission failed. 2: (for M transmission) he delivery window was blocked, so the message has been copied to an internal queue for deferred delivery. o more notification will be issued for this message. able: <prefix>mrlgd olumn ype ontains UB_D integer ubscription D, a 4-byte integer that uniquely identifies a subscription within a subscription set. D_D string(32) Document D, a GUD-string that identifies a document that was sent to the recipient. VX_D string(32) ervice execution D, a GUD-string that uniquely identifies this execution of this service. R_Q_GUD string(32) A unique value to distinguish between multiple failed attempts to transmit a message. A_Y_D integer Action ype D, a 4-byte integer indicating what action took place with the document (failed, succeeded). D_A_ timestamp Document action timestamp, a date-time value representing the time at which the document was generated (or failed), expressed in the time zone specified by the user. D_AM string Document name, a string specifying the name of the document. Recording transmission information 95

116 *All columns have the prefix MR_ to prevent future name conflicts with database reserved words. o view the name of the recipient instead of or in addition to the GUD, you can join this table to the <prefix>mrlgmg (Log Message) table, and then to the <prefix>mrur (Users) table in the ubscription Book Repository, using the following QL statement: select t1.mr_ur_am A URAM, t3.* from <prefix>mrur t1, <prefix>mrlgmg t2, <prefix>mrlgd t3 where t1.mr_ur_d = t2.mr_ur_d and t2.mr_ub_d = t3.mr_ub_d You can run similar queries to return other information about the user, address (by joining to <prefix>mraddr.mr_addr_d) or subscription (by joining to <prefix>mrubr.mr_ub_d. he MR_A_Y_D column typically holds the following value: 1: he document was successfully rendered. Additional values are reserved for future use. able: <prefix>mrlggm ([service execution : subscription : job] level tracking) olumn ame rimary Key Data type urpose GM_D o HAR(32) not null egment execution D, a GUD-string that uniquely identifies this segment of this service. VX_D o HAR(32) not null ervice execution D, a GUD-string that uniquely identifies this execution of this service. 96 hapter 4 Administering ystems

117 able: <prefix>mrlgqrajb ([service execution : subscription : job] level tracking) olumn ame rimary Key Data type urpose UB_D Yes integer(4) not null ubscription D, a 4-byte integer that uniquely identifies a subscription within a subscription set. GM_D Yes HAR(32) not null egment execution D, a GUD-string that uniquely identifies this segment of this service. JB_GUD Yes HAR(32) not null Job GUD, a GUD-string that uniquely identifies a job. able: <prefix>mrlgqrajbf ([job] level tracking) olumn ame rimary Key Data type urpose JB_GUD Yes HAR(32) not null Job GUD, a GUDstring that uniquely identifies a job. JB_D o integer(4) not null Job D, a 4-byte integer that uniquely identifies a job in the -server. _D o HAR(32) not null ession D, a GUD-string that uniquely identifies a session in the - server. RJ_D o HAR(32) not null roject D, a GUDstring that uniquely identifies a project. _D o HAR(32) not null nformation object D, a GUD-string that uniquely identifies this information object in this service. Recording transmission information 97

118 olumn ame rimary Key Data type urpose _D o HAR(32) not null nformation source D, a GUD-string that uniquely identifies the information source. RVR_AM o Varchar(255) erver ame, a 255 character string that uniquely identifies the server name or address of the server. XU_M D o integer(4) not null xecution mode, a 4-byte integer that uniquely identifies the execution mode of a service, which could be ersonalized age xecution () or ersonalized Report xecution (R). AU o integer(4) not null tatus, a 4-byte integer that uniquely identifies the job execution status. o get a report of the users who received the message, the message that they received, and the time when they received the message, you can join the tables <prefix>mrlgmg, <prefix>mrubr, <prefix>mrur, <prefix>mrlgqrajb, <prefix>mrlgqrajbf, _RR_A, <prefix>dmdbjf, and <prefix>mrlggm using the following QL statement: L MR_UR_AM as User, BJ_AM as Report, MR_RA_ as imedelivered from MRLGMG as A, MRUBR as B, MRUR as, MRLGQRAJB as D, MRLGQRAJBF as, _RR_A as F, DMDBJF as G, MRLGGM as H where A.MR_UB_D = B.MR_UB_D 98 hapter 4 Administering ystems

119 and B.MR_UR_D =.MR_UR_D and A.MR_UB_D = D.MR_UB_D and D.MR_JB_GUD =.MR_JB_GUD and.mr_jb_d = F.JBD and.mr D = F.D and F.RRD = G.BJ_D and A.MR_VX_D = H.MR_VX_D and H.MR_GM_D = D.MR_GM_D ending notification for file and print delivery Whenever an service is executed, it is possible to know whether the has been delivered to the specified address, but for file and print delivery services, it is not possible to know when the file has been exported or when the print job is completed. he users of arrowcast erver and Web now have an option of sending an notification after the file or print delivery is complete. his option can be set through the ubscription roperties ditor. he notification is sent after the file or print delivery is complete, and the status of the service and transmission is included in the notification message. he notification includes the following content: ame of content to be delivered Delivery method-file or print Delivery address Delivery date and time ontent delivered ontent details rror messages in case of failure-f the printer is not available or if there is an error writing to the network location. A sample layout of the notification for file delivery is shown as follows: Dear %otification User%, he following file delivery %Delivery tatus%. ervice ame: %ervice ame% xecution Date: %Date% xecution ime: %ime% Delivery address: %Address% %Backup Address% Links to files: hows links to files for file delivery ontent delivered: ames of arrowcast erver documents ending notification for file and print delivery 99

120 ontent details: ame of report/document in the service %rror Messages% A sample layout of the notification for print delivery is shown as follows: Dear %otification User%, he following print delivery %Delivery tatus%. ervice ame: %ervice ame% xecution Date: %Date% xecution ime: %ime% Delivery address: %Address% %Backup Address% Links to files: hows links to files for file delivery ontent delivered: ames of arrowcast erver documents ontent details: ame of report/document in the service %rror Messages% he conditions that result in the failure or success of the service are tabulated as follows. ype cenario tatus File File File File File File File rint All content delivered to primary address. artial content delivered to primary address (partial file or part of the list of files) and backup location is not set. o content delivered to address and backup location is not set. artial content delivered to primary address and remaining delivered to backup location. All content delivered to backup location after delivery failure to primary location. artial content delivered to backup location (partial file or part of the list of files) after delivery failure to primary location. o content delivered to backup location after delivery failure to primary location. All content delivered to primary address ucceeded Failed Failed Failed Failed Failed Failed ucceeded 100 hapter 4 Administering ystems

121 ype cenario tatus rint artial content delivered to address (partial printing or part of the documents list was printed) no backup location is set. Failed rint rint rint rint rint rint o content delivered to address and backup location is not set. o content delivered to primary address and backup location is file. All content delivered to backup location after delivery failure to primary location. artial content is delivered to primary address and remaining is delivered to backup address. artial content delivered to backup location (partial printing or part of the documents list was printed) after delivery failure to primary location. o content delivered to backup location after delivery failure to primary location. Failed Failed Failed Failed Failed Failed pecifying document creation options n arrowcast erver, the following options are available for document creation: reate new documents within arrowcast erver (from arrowcast Administrator, ervice Wizard, or ublication Wizard) Link to existing Microtrategy Desktop documents (Report ervices and HML documents already created in Desktop) he first option allows application designers full control of what they create, which includes all arrowcast erver documents: xcel, HML, laintext, and imported documents. hese documents can later be opened and edited, according to the properties available for each format. he second option allows application designers to link to existing documents in Microtrategy Desktop, which are already fully designed and may include multiple reports as well as page headers and footers and other information. hey are ready to be sent in a service with no additional design. hese documents cannot be opened or edited from within arrowcast erver; you can do this from Desktop. pecifying document creation options 101

122 You can elect for application designers to only have one of the above options available, or to choose. You specify this for all application designers using the arrowcast erver system. Administering multiple systems ne of the powerful features of arrowcast Administrator is its ability to connect to and administer more than one system at a time. his feature allows administrators with the appropriate account permissions to connect to two or more systems, view and manipulate their objects, monitor their execution queues, and control their states all from within one interface. n addition, arrowcast Administrator provides the ability to copy or migrate objects between two systems. he ability to administer multiple systems is useful for: Maintaining separate development, test and production environments, and migrating objects between these Archiving and restoring a distinct version of a system ontrolling and monitoring multiple systems When a system is created with the ystem onfiguration Wizard, it can be set up for service execution, or it can be configured so that it does not have any distribution managers or execution engines, and therefore cannot execute services. his latter option is useful for storing versions of a system, as explained below. Maintaining separate environments Many arrowcast erver installations use more than one environment for operations. At these installations, separate environments are maintained for development and production, and sometimes additional environments are created for testing and other purposes. he objects for a production system are first developed in the development environment. here, they are tested under controlled conditions to ensure correct behavior before they are copied to the production environment. opying the tables used by an bject Repository to create a duplicate, backup system is not recommended. his action can result in two systems that share the same system components and ubscription Book Repository. bject management provides a safer way to back up a system and also gives you greater control over which objects are copied. 102 hapter 4 Administering ystems

123 he ystem onfiguration Wizard can be used to create these systems, or a system administrator can register an existing system to connect to it. nce arrowcast Administrator is connected to two systems, it can be used to view the definitions of objects in either system. his is useful for determining whether an object in a production environment has the same definition as the same object in a development environment. t also provides a way to migrate objects from one environment to another. Migrating objects between systems n Microtrategy arrowcast erver 7.x and later, administrators can manage multiple systems from one console. his new feature allows administrators to move objects between development and production repositories in a manner similar to the way Microtrategy Administrator bject Manager works. he administrator can simply drag and drop objects from a folder in the development system to the corresponding folder in the production system. o copy objects across systems, it is very important that the systems involved have different system Ds. Duplicating a system by creating a backup of an existing database, and creating a new system pointing to this backup is not recommended because even though you may change the name of the new system, the system Ds of these two systems are the same. herefore, you cannot see both the systems at the same time in the arrowcast Administrator console. Also, the pointer to the ubscription Book Repository location is stored in the bject Repository, and when the bject Repository and ubscription Book Repository tables are duplicated, the new bject Repository tables would still point to the old ubscription Book Repository tables. o set up the Microtrategy arrowcast erver - bject Manager it is necessary to have: A computer with Microtrategy arrowcast erver Administrator console. All of the Data ource ames (Ds) used in both the production and development systems. Both the production and development systems registered using the appropriate D. Administering multiple systems 103

124 After both systems are registered, you must open a window for each system in the Microtrategy arrowcast erver Administrator console. he windows can be tiled horizontally or vertically. his setup works as the Microtrategy arrowcast erver - bject Manager. ow, expand the required folders in the development system, and drag and drop the objects to move them from development to production. his opens the onflict Resolution dialog box. his dialog box shows all the dependant objects that exist with the same name in both systems. Accept only those objects that you specifically want to overwrite, and click K. he objects from the development system are successfully moved to the production system. he subscription sets are copied without the actual addresses in them; so you have to add the addresses in the new system that you create. Migrating objects with dependencies he object management capabilities of arrowcast Administrator were designed specifically to support the migration of objects between environments. he user interface makes this process as easy as copying a file from one folder to another in Windows xplorer. However, it is important to recognize that the objects in a system are not the same as files on a disk. For example, some objects depend upon other objects to complete their own definitions. ervices depend upon schedules, publications, and subscription sets. ublications depend upon documents, locales, devices, and so on. Because of these dependencies, copying an object such as a service without also copying the objects upon which it depends would not produce a useful result in the destination or target system the service would not be usable. ote the following: All objects inside the Applications folder can be migrated from one system to another. nly the following objects inside the Administration folder can be migrated: device subfolders and devices, locales, information sources, document formatters, and information transmitters. he system object, the Applications folder, the Administration folder, and other administration objects cannot be migrated. 104 hapter 4 Administering ystems

125 arrowcast Administrator resolves the problem of object dependencies by automatically locating and migrating all of the objects used by an object being migrated. o when a service is migrated from one system to another, any publications, subscription sets, and schedules used by that service are also migrated. And because each of these objects can also have dependencies, arrowcast Administrator ensures that objects used by those objects are migrated as well, until every object ultimately required to modify or execute the service being migrated is also migrated. Repeated object migration he copying of dependent objects can result in the migration of tens or even hundreds of objects when services supporting a large number of devices and a complex set of content are migrated. t might be acceptable for new copies of all of these objects to be created in the target system the first time a service is migrated, but it would certainly not be acceptable for subsequent migrations of that service or other services. therwise, the number of objects in the target system would quickly grow to become unmanageable. More importantly, different copies of the same object, such as an client device, would be treated differently by the system, so users might find themselves needing to create several addresses that all use different copies of the same device to be able to subscribe to different services. his is obviously not desirable. As a result, arrowcast Administrator uses object Ds to uniquely identify each object within a system. When an object is copied from one system to another, it retains this object D. hus, arrowcast Administrator can determine when an object that is being copied or migrated to a target system already exists in that target system. n this way object migration is very different from copying files between disks, because while a copy of a file is a copy, an object copied to a different system is better described as an instance of the same object, merely existing in a different system. he original object and its copy can both be modified and used independently, but whenever one of them is migrated to the other system, arrowcast Administrator determines that the object already exists. his holds true whether an object is explicitly migrated by the user, or implicitly migrated due to a dependency. Migration scenarios nly one object with a given object D can exist in a given system at any time. herefore, arrowcast Administrator gives you the choice of either replacing an object that already exists in the target system, or rejecting the migration and keeping the object that already exists within the target system. However, merely knowing that the object already exists is not Administering multiple systems 105

126 particularly useful in determining which of these two options to take. For this reason, arrowcast Administrator provides additional information in this situation to help you decide which option is the right one. Five scenarios can occur when an object is migrated from one system to another. he most straightforward scenario is the one in which the object does not yet exist in the target system, in which case it is created. All of the other scenarios involve the prior existence of the object in the target system, and are distinguished by whether or not the object in either the source, target, or both has been modified since the last time that same object was migrated between the two systems. reate he object being replicated does not exist in the target system. Accepting this action creates the object in the target system using the definition of the object in the source system. Refresh he object being replicated exists in the target system, and has the same definition as the object in the source system. either object definition has been modified since the object was last migrated from one system to the other. Accepting this action does not cause a material change to the definition of the object in the target system. Update he object exists in the target system, and its definition has not been modified since the object was last migrated from one system to the other. However, the definition of the object in the source system has changed since the object was last migrated. Accepting this action updates the definition of the object in the target system to be the same as the newer definition of the object from the source system. verwrite he object exists in the target system, and the objects in both the source and target systems have been modified since the object was last migrated. Accepting this action causes the definition of the object in the target system to be replaced with the definition of the object from the source system, which loses any changes that were made to the object in the target system since the object was last replicated. Revert he object exists in the target system, and its definition has been modified since the object was first replicated from one system to the other. he object in the source system has not been modified since the object was last migrated. Accepting this action causes the object in the target system to lose the changes that were made to it since the object was last replicated. ome migration scenario examples are shown in the following figure, and are explained below. 106 hapter 4 Administering ystems

127 ystem A (source or test) create or refresh (1 or 5) ystem B (target or production) A B riginal version Modified version revert (3) update (2) A' B' overwrite (4) 1. opy an object from test to production for the first time (creates object B in system B). 2. Upgrade an object in production with its improved definition from the test environment (updates the definition of object B in system B with the definition of object A' from system A). 3. Roll back an object in production to its original definition from the test environment (reverts the modified definition of object B' in system B to its original definition when it was copied from object A from system A). 4. Replace an object in production that was modified with a hot fix, to the definition of an improved object from the test environment (overwrites the modified definition of object B' in system B with the modified definition of object A' from system A). 5. Recopy an object from test to production, to ensure that both objects have the same definition (refreshes object B in system B with the definition of object A from system A, which is identical). Using scenarios to prevent errors he difference between an update and an overwrite can be used to ensure that improvements to objects made in a development environment are migrated to a production environment, but objects that intentionally differ Administering multiple systems 107

128 in the production environment are not accidentally replaced with the corresponding objects from the development environment. For example, a development environment might have an transmitter configured to save all messages to disk rather than transmit them via M. hat same transmitter in the production environment might be configured to only transmit via M, however. o while it might be useful to modify a device in the production system with an improved version of that device from the development system, the transmitter in the production system should not be overwritten. Using the ability of arrowcast Administrator to distinguish between an update scenario (the improved device) and an overwrite scenario (the transmitter) helps prevent user error when deciding which object migrations should be accepted or rejected. he revert scenario can be used to prevent the accidental loss of spot changes made in a production environment, such as hot fixes, by rejecting any migration action of that type. Migration and folder structures A file on a disk is uniquely identified by its name and the directory or folder in which it exists. Because of this, two files with the same name can exist in two different folders. However, it is more desirable to identify objects by D than by name and location when performing object migration. his can create a problem because the location in which dependent objects should be copied becomes ambiguous if dependent objects in the source and target systems are in different locations. hould updated dependent objects be moved to the target folder as in the source system, or should they be kept where they are? ither result can cause confusing and what might appear to be unpredictable behavior for the user performing object migration. Furthermore, folders in a system serve a purpose for the ubscription ortal, just as folders on a disk serve a purpose when they are referenced by a virtual directory. For these reasons, arrowcast Administrator treats the folder in which an object exists the same as it does a dependent object. he folder is migrated just as any other dependent object would be. When a folder is contained within another folder, that parent folder is also treated like a dependent object, and so on up to the Applications and Administration folders in a system. he result is that when objects are migrated from one system to another, the complete folder structure containing those objects and their dependent objects is migrated as well. Because of this, object migration should not be thought of as a way to copy an object from a folder in one system to a folder in another, but rather as a way to copy an object from one system to another, for the purpose of ensuring the consistent behavior 108 hapter 4 Administering ystems

129 of that object between the two systems. For information on best practices associated with folder structures, see roperties not preserved during migration When an object is migrated from one system to another, the following object properties are not preserved (regardless of whether the action being performed is to create, refresh, update, revert, or overwrite the object in the target system): wner he owner of the object in the target system is the same as the current user account, which might not be the same as the owner of the object in the source system. his ensures that the security of the target system is maintained, and that an object is not created there with an owner that does not exist as a recognized account. t also ensures that the individual performing the migration cannot circumvent the security of the target system. reated he created date/time stamp of the object in the target system is not the current date and time. or is it necessarily the same as the reated date from the source object. nstead, it is the same as the Last Modified date/time stamp from the source object. his enables the product to distinguish between Refresh, Update, Revert and verwrite situations during subsequent migrations. Last Modified he last modified date/time stamp of the object in the target system is not the current date and time. t is the same as the Last Modified date/time stamp from the source object. his enables the product to distinguish between Refresh, Update, Revert and verwrite situations during subsequent migrations. Modified by he owner of the object in the target system is the same as the current user account. For steps to copy and restore objects for backup, see opying and Restoring bjects. reating and restoring versions You now know that arrowcast Administrator can be used to copy the definition of an entire system from one environment to another. his capability can be used to store snapshots, or versions of a given system. he easiest way to make a complete copy of the definition of a system (with the exception of the cluster definition) is to create an empty system that has no cluster definition and then copy the contents of the nformation ource Modules, Document Formatters, nformation ransmitters, Devices, Locales, and Applications folders from the original system to this empty system. his copy system then holds a version of the original system. Administering multiple systems 109

130 When a system is created using the ystem onfiguration Wizard, it is automatically populated with dozens of objects including devices, locales, transmitters, document formatters, folders, schedules, xcel files, and many other objects that make your tasks and the ervice Designer s tasks easier. However, if any of these objects are deleted from a given system, they should also be deleted from each empty system used to store a version of that given system. therwise, the version-store system does not provide an accurate representation of the original system due to the existence of these extra objects. Restoring a version is also a simple process. Restoration can be done on an entire system or on individual objects, for example, reverting the definition of an object that was damaged during development back to its original, working definition. When restoring a specific version for an entire system, it is important to remember to clean out the existing objects in the system as the restoration process does not automatically delete objects that did not exist in the stored version. ontrolling and monitoring multiple systems he arrowcast Administrator interface provides the ability for several windows to be open at the same time, each displaying a different view of any one of the systems registered on the machine. his multi-window capability can be used to create a status console, including error display, service queues, scheduled service lists and other useful information by tiling several of these windows on a single screen. ystem control is context sensitive. he system being controlled by the buttons on the toolbar or the menu options depends upon the application window that was most recently selected. his is important to keep in mind when trying to start up or shut down one of several systems. o prevent accidental changes to a system when monitoring, account privileges can be used to control what capabilities the person controlling or monitoring the system has. For example, to prevent modification of application objects, remove the ervice Designer and Application Administrator privileges for the account being used for monitoring. 110 hapter 4 Administering ystems

131 Viewing system messages arrowcast erver provides a way to view system messages, including error messages, execution events, and others. You can save the entire list of messages, configure the settings for logging that include time zone, date format and time format, configure the log file by file size and time, sort the logged messages by time, and log the different items in each message in a format that can be easily read and understood. he ystem Message Viewer dialog box is the tool that monitors the system messages, including errors, statistics, and debugging information, generated by the Delivery ngine during service execution. t connects to the Microtrategy Logging erver, and retrieves from there all messages that match any of the selected message types. hese matching messages are then retained in memory in a message log. he content of the message log is displayed in the ystem Message Viewer. When the content of the message log exceeds the user-specified number of lines, the least-recent lines are overwritten by new messages. his can be used in a variety of ways: As an error-display console for a etwork perations enter As a diagnostic tool for aiding in the development of new services As an observation tool for watching the flow of execution of a service across a clustered system By controlling the types of messages that are shown, you can configure the ystem Message Viewer for each of these purposes. o use the ystem Message Viewer as an error-display console, configure the viewer to only show errors. For an observation tool, enable information-level logging. And for a diagnostic tool, enable debugging messages. t is not recommended to use component-level debugging on a production system unless necessary, as the additional logging reduces the performance of the system. etting the administrative notification t is important for the arrowcast erver administrator to know whether a service and all segments within it ran successfully. Failure at any stage should be cause for alert, depending on the particular service and system. he administrator should be notified in case of failure of a system, a service, an nformation bject, and so on. For example, it would be beneficial if the administrators would receive a series of s regarding service summaries that give them information regarding the overall Viewing system messages 111

132 success or failure of a service, the names of recipients who received its content and those who did not, and the reasons for certain recipients not receiving the data, such as ' returned no data' or ' failed' along with the name or D of the nformation bject. Microtrategy arrowcast erver provides the ability to set and send such notifications to system administrators. Administrators can configure these notifications and choose the delivery address. uning the Delivery ngine uning the Delivery ngine in your arrowcast erver system is important to help you ensure that you get the best possible value from your investment. he various configuration and service settings are given default values that are designed to provide robust, stable system operation with a configuration that meets the minimum system requirements. t is very likely that your system has more memory, disk space, U processing power, and other resources that you want arrowcast erver to use to the fullest potential. uning helps you achieve this potential with your system configuration. he behavior and performance of the Delivery ngine vary widely based on the definitions of the services that are run. For this reason, the default configuration and service settings are typically not the optimal settings for your application. uning helps you optimize these settings so that they are better suited to your application. Before you can begin to tune your arrowcast erver system, you must understand the following concepts and terms. ystem workload capacity: f you take the sum of the workload capacities of all running execution engines in a system, the resulting value is the system workload capacity. his represents the maximum number of segments that the Delivery ngine can be actively processing at any moment in time. xecution cycles: f you divide the number of subscriptions to a service by the segment size for that service and round up to the nearest integer, you get the number of segments for that service. f you then divide this number by the system workload capacity, you arrive at a ratio representing the hypothetical number of service segments that a segment executor on any given execution engine will need to process. his ratio is referred to as the number of execution cycles required to complete the service. n reality, the system does not behave in this manner, but it proves to be a useful metric nonetheless. 112 hapter 4 Administering ystems

133 art of the tuning process involves modifying some variables that are dependent upon other tuning variables or tasks. For this reason, the order in which you perform tuning steps is important. he tuning steps are: 1. Minimize report size 2. Reduce report count 3. ptimize system workload capacity 4. ontrol memory consumption 5. ptimize execution cycles n addition, you can pecify queue sizes for segmentation Minimize report size f it is possible to reduce the size of the reports that you include in service content, such as by eliminating extraneous rows or columns, then this technique can be used to improve service throughput. Reduce report count he more reports arrowcast erver needs to execute, the more work (in particular, XL processing) the segment executors need to perform to complete the execution of a service segment. By reducing the number of reports in a service, you reduce the work that Microtrategy ntelligence erver and the segment executors need to perform. ne way to dramatically reduce report count is to use personalized page execution mode. his can reduce by two orders of magnitude or more the number of reports that the system needs to run to generate personalized content. For more information on personalized page execution, refer to age ersonalization and Dynamic ubscriptions in the arrowcast erver Application Designer Guide. ptimize system workload capacity he workload capacity of each execution engine can be tuned to achieve the highest possible throughput from a system. As a rule of thumb, it is recommended that the maximum number of simultaneously executing segments (the workload capacity) on an execution engine never be configured below the number of processors in the machine. therwise, uning the Delivery ngine 113

134 there is an under utilization of the memory and processor power. nstead, a value between 1.5 and 2 times larger should be chosen. his ensures that all available U power is being tapped while services are executing. he optimal workload capacity for an execution engine is the value at which it achieves the highest segment completion throughput rate. cientific testing can be used to narrow in on the best configuration for each execution engine. ontrol memory consumption As you increase system workload capacity, you also increase the amount of memory consumed by the execution engines during service execution. he fourth step in Delivery ngine tuning is to ensure that memory consumption remains below a safe upper bound. he easiest way to control memory consumption is through segment size. As segment size increases, memory consumption increases as well. As a result, there is an upper boundary on the segment size that you can use for segments, given your workload capacity configuration and service definitions. his varies from one service to the next, and is dependent on the complexity of each service definition. For example, a service with many reports and documents consumes much more memory than a simple service with one report for the same number of subscriptions. he upper boundary for any given service is the safety value below which you can ensure that memory consumption on the machine never exceeds the available physical and virtual RAM. You can measure the total virtual memory consumed on an execution engine machine during service execution by using Microsoft Windows erformance Monitor. By monitoring the total virtual bytes used for an execution engine during service execution, you gain insight into the memory consumption characteristics of each service. You can then use this information as a maximum allowable value for the segment size so that you never risk the overconsumption of memory. ptimize execution cycles nce you have ensured that your actions do not cause excessive memory consumption, you are ready to optimize the segment size for each service. he segment size for a service should be sufficiently small that the number of execution cycles is significantly larger than 1, and potentially closer to 10. f the subscription set for a service has 10,000 recipients, the segment size is 100 and the system workload capacity is 10, then the number of execution cycles can be calculated as follows: 114 hapter 4 Administering ystems

135 (10,000 subscriptions) / 100 (subscriptions / segment) = 100 segments 100 segments / 10 (segments / execution cycle) = 10 execution cycles ote that this calculation is dependent on the workload capacity of the system, and should therefore be performed after system workload capacity has been optimized. Also, you should not use this value if it exceeds the safety value identified during the memory consumption control step (in which case you should use the safety value). For services running reports in personalized report execution mode, tuned segment sizes typically range from 10 to 50 subscriptions per segment. For personalized page execution mode, the band of optimization is very broad; often there is little difference in performance between segment sizes of 20 and 2000 subscriptions. pecify queue sizes for segmentation arrowcast erver allows you to specify how the size of the pending segment queue determines whether the next service in the pending queue is segmented. wo settings control this behavior: At least and At most. Under normal operations, the primary distribution manager begins segmentation for the highest-priority service in the service queue when the following is true: (he service is of higher priority than any services that have been segmented for which segments are still in the segment queue. or he number of segments in the segment queue is below the At least value.) and he number of segments in the segment queue is below the At most value. his behavior offers the following benefits: he system cannot be overloaded with segment data. he at most value ensures, above all else, that the system cannot be overloaded with segment data. his helps to maintain system stability in high-load or transient-load environments. uning the Delivery ngine 115

136 he available hardware is used to maximum benefit. he at least value ensures that the available segment executors on the operational execution engines are kept fully loaded. f the segment execution queue were allowed to go empty before the next service in the service queue were segmented, the segment executors would need to wait for the next service to be segmented each time a service was finished. High-priority services do not need to wait for lower-priority services that are already running. f the segment queue were filled to the at most value with segments from low-priority services whenever such services were present in the service queue, it would not be possible for high-priority services to preempt lower-priority services as they would need to wait until the segment queue size was reduced below the at most level. he two values are described below. At least f the number of segments in the segment queue awaiting execution drops below this number, the primary distribution manager gets the service in the service queue with the highest priority, even if that is the same or lower priority than the service for each segment currently in the segment queue. ncreasing the at least value helps ensure that the execution engines are kept fully utilized in a high-throughput environment by ensuring that the queue is never emptied. Decreasing the at least value helps ensure that the primary distribution manager does not fill up the segment queue unnecessarily with segments waiting to execute. o determine a satisfactory at least value, perform the following calculation: 1. alculate the workload capacity of your system by adding the workload capacities of the operational (that is, running) execution engines. 2. Determine or estimate the fastest time in which a single segment for any given service in your system is executed. You might consider using a two- or three-sigma outlier value rather than the absolute fastest time. 3. Determine or estimate the slowest time in which any given service in your system is segmented. You might consider using a two- or three-sigma outlier value rather than the absolute slowest time. 4. Divide the slowest segmentation time by the fastest segment execution time. Round the result up to the nearest integer, add one, and multiply this value by the system workload capacity. his value represents the optimal value for the at least parameter. his value should be made much smaller than the at most value. 116 hapter 4 Administering ystems

137 An example follows. f it takes as long as 85 seconds to segment a service, the fastest segments execute in 10 seconds, and the workload capacity of a system is 30, we want to ensure that all 30 segment executors are fully loaded during the entire time that the next service is being segmented. his requires 85 seconds / 10 seconds per segment = 8.5 segments per available segment executor to ensure that the workload duration for the segment executors is equal to the workload duration for segmentation. Rounding this value up to 9 ensures that a portion of the segment executors do not run out of segments to execute in the segment queue before segmentation is complete. Adding 1 takes into account the possibility that the segments currently executing when a new service arrives are nearly complete, and therefore consume negligible time. o the minimum optimal value for the at least parameter is (9+1) * 30 = 300 segments. At most f the number of segments in the segment queue awaiting execution exceeds this number, the primary distribution manager will not segment any more incoming services, even if those are higher priority than the services for every segment currently in the queue. Decreasing the at most value helps conserve memory on the primary distribution manager machine. ncreasing the at most value helps ensure that in a high-volume environment with a large number of segments in each service, the primary distribution manager does not wait unnecessarily to segment high-priority services. n general, this parameter should have a value that is much larger than the maximum segments per execution parameter, to ensure that the segment queue can hold the segments for several large services at the same time. Before segmentation is performed on a service, the number of segments in that service is not known. Because of this, the governing setting At most for segment queue sizes to trigger segmentation can be exceeded by a number of segments calculated as: (<maximum number of segments per service> * <maximum concurrent expansions> - 1) Using an at most value that is too large causes unnecessary consumption of memory and reduced primary distribution manager performance as the primary distribution manager needs to maintain a larger segment queue. herefore, this value should only be increased if necessary to ensure that a full queue does not cause high-priority services to wait. f all services are the same priority, this setting need not be set significantly larger than the at least value. uning the Delivery ngine 117

138 Maintaining arrowcast erver systems While arrowcast erver is running, it modifies the system environment over time. his modification originates from the log files, transmission recording records and other operational outputs that arrowcast erver generates when it runs services and administers subscriptions. Maintaining a arrowcast erver system requires that these records and files be periodically cleaned up and archived so that the system does not eventually run out of available disk or table space. Log files Microtrategy arrowcast erver generates log files in several locations. Most of these log files are only populated if errors occur during ubscription ortal use or service execution. As the system administrator, it is your responsibility to monitor these files and truncate them when they grow unnecessarily large. Most of these locations depend upon your installation. Apply the following constants when determining one of these locations: %Application ath% is the folder into which arrowcast erver was installed. ne example is :\rogram Files\Microtrategy\arrowcast erver. %ommon Files ath% is the folder into which the Microtrategy common files were installed. his is typically :\rogram Files\ommon Files\Microtrategy. %Windows ath% is the folder into which the Microsoft Windows or Windows 2000 operating system was installed. his is typically :\W or :\WDW. he list of log file locations is provided here. ote that this does not include log files created or populated during the installation and configuration process: %Application ath%\ubscription ortal\asp\logs: his location stores log files for errors that occur in the ubscription ortal.a pages. %ommon Files ath%\log\: f errors occur in the DB connections that arrowcast erver uses to interact with the bject Repository and ubscription Book Repository, the error information is logged here. %Windows ath%\system32\logfiles\w3v1\: By default, Microsoft nternet nformation erver stores website log files in this location. 118 hapter 4 Administering ystems

139 %Application ath%\delivery ngine\: he Microtrategy Logging onsumer stores log files here when it is configured to do so. nce they exist, these log files do not grow over time. nstead, they are overwritten in a cyclical fashion. Repository databases he repository databases require occasional maintenance. his maintenance includes index regeneration and table space administration. n particular, the contents of the transmission recording tables in the ubscription Book Repository continue to grow for the life of a arrowcast erver system, as long as transmission recording is enabled. Maintenance of the transmission recording tables requires periodic archiving and truncation. Maintenance of the remainder of the repository database tables primarily requires periodic index regeneration. opying Repositories arrowcast erver provides a simple option to make copies of its repositories, which eliminates the complexities related to manually copying repositories. You might make copies of the arrowcast erver repositories for many reasons, including the following: reate a copy of the production environment to test the upgrade to a newer version of the Microtrategy product. opy the development environment to create a test or production environment. opy a repository from one database to another. he opy Repository dialog box allows you to make copies of the bject repository and the ubscription Book repository. For steps to copy the repositories, see onfiguring a arrowcast erver ystem. opying Repositories 119

140 ote the following: t is recommended that administrators perform the copy operation when there is no or low system activity. After a system is copied and turned on, any end ow subscriptions running on a one minute schedule are executed. Because the end ow subscription sets cannot be opened, the administrator cannot view the subscriptions it contains and cannot delete the subscriptions. n the copied system, the administrator should also disable the delivery on those services that are executed on a one minute schedule. ystem copying should be done when users or administrators are not actively using the system. his helps minimize potential inconsistencies introduced by modifications made to the bject Repository and ubscription Book Repository while the copy is being made. t is a good practice to have the system shut down when copying. Using ommand Manager to automate key processes Microtrategy ommand Manager is an application that lets you perform certain administration and application development tasks by using text commands that can be saved as scripts. ommand Manager lets you add, delete, or update enterprise-level data associated with large numbers of users and user groups. Additionally, ommand Manager allows you to manage various configuration settings within the Microtrategy platform. ommand Manager support for Microtrategy ntelligence erver Microtrategy ommand Manager allows you to manage and run scripts that change many of the Microtrategy system settings, objects, and user properties. cripts can change multiple settings all at once without using the Microtrategy Desktop interface. You can create scripts to be run at times when it would not be convenient for you to make the changes. For more information on ommand Manager support for Microtrategy ntelligence erver, refer to the Microtrategy ystem Administration Guide. 120 hapter 4 Administering ystems

141 ommand Manager support for arrowcast erver Microtrategy ommand Manager supports the arrowcast erver system. ommand Manager lets you perform manipulations on the arrowcast erver system, arrowcast ubscription Book and ubscription ets, and triggers arrowcast erver services. Administrator privileges are not required to run a service using ommand Manager. You only need Access and Launch DM permissions to run a service. For more information on assigning DM permissions, see tarting the Delivery ngine. ommand Manager contains sample scripts for arrowcast erver also, which you can customize according to your system requirements and save as script files for later use. ommand Manager scripting is not only convenient for mass operations, but also for event driven execution of services, and as a good alternative to the use of pre-/post-ql in subscription sets. For step-by-step instructions about using ommand Manager, see the ommand Manager online help (press F1 while using ommand Manager graphical interface). Using ommand Manager You can use ommand Manager in the following ways: tart the ommand Manager graphical interface, which you use to view sample script outlines, create, modify, delete, or run scripts (explained below). o access ommand Manager, from the Windows tart menu, point to rograms, Microtrategy roducts, then choose ommand Manager. From the File menu, select onnect or click the onnect icon on the toolbar. o perform a connection to the arrowcast erver metadata, you must specify the data source name, a user name, and a password. You must also specify the database location and a prefix, if any, where a arrowcast erver system resides, to connect to the metadata and manipulate it. he ommand Manager console stores the information of the last five successful arrowcast erver connections for future reference and quick access, so that you do not have to always remember the connectivity parameters to the arrowcast erver ystems. Using ommand Manager to automate key processes 121

142 When connecting to an racle bject repository, the prefix for racle Databases should include the login, for example, DBA.estsys. all the ommand Manager executable including necessary parameters such as the script file to run, from the Windows scheduler, Windows command prompt, or other applications such as system management software. he following section explains the procedure to access the ommand Manager using the Windows command prompt. Using D commands to execute ommand Manager scripts You can use D commands to execute ommand Manager scripts through which you can access arrowcast erver. he syntax of the commands is given as follows: cmdmgr -w DB_D -u Login [-p assword] [-d Database] [-s ystem_refix] [-f nputfile] [-o utputfile] where, parameters enclosed in brackets ("[" & "]") are optional. he parameters are: -w DB_D pecifies the data source name which is used to connect to the application. -u Login dentifies the user name to be associated with the data source name. -p assword (ptional) rovides the password for the username. f omitted, the system assumes a ULL password. -d Database pecifies the database to which you want to connect -s ystem refix pecifies the prefix where a arrowcast erver system resides -f nputfile (ptional) dentifies the name, and the full path if necessary, of the script file (.scp) to be executed. -o utputfile (ptional) Logs results, status messages, and error messages associated with the script. Logging can be accomplished through one of the following options: 122 hapter 4 Administering ystems

143 Use the parameter -o to specify the output file Use the log file specified in the options menu (available only when the option is activated) Use a temporary MDMGR.log file for logging purposes f the first two options are not selected, the application uses the third option as default. tatement syntax for arrowcast erver his section describes some sample scripts for arrowcast erver. tart a arrowcast erver ystem AR YM; top a arrowcast erver ystem YM; reate a ubscription Book User his command creates a new user in the ubscription Book. RA UR login_name [AWRD password H hint] [LAL locale_type] [AV (RU FAL)] [XR (VR [] user_expiration_date)]; Where: login_name is the name of the new user, of type string, between double quotes ("). password is the password for the new user, of type string, between double quotes ("). hint is the hint to be used to display if the password is forgotten, of type string, between double quotes ("). locale_type is the locale to be assigned to the user, of type string, between double quotes ("). user_expiration_date is the date on which the new user expires, in the mm/dd/yyyy format. Alter the properties of a user in the ubscription Book Using ommand Manager to automate key processes 123

144 ALR UR login_name [LG new_login_name] [AWRD password H hint] [LAL locale_type] [AV (RU FAL)] [XR (VR [] user_expiration_date)]; Where: login_name is the name of the user to be modified, of type string, between double quotes ("). new_login_name is the new login name of the user, of type string, between double quotes ("). password is the password for the user, of type string, between double quotes ("). hint is the hint to be used to display if the password is forgotten, of type string, between double quotes ("). locale_type is the locale to be assigned to the user, of type string, between double quotes ("). user_expiration_date is the date on which the new user expires, in the mm/dd/yyyy format. Delete a user from the ubscription Book DL UR login_name; Where, login_name is the login of the user to be deleted, of type string, between double quotes ("). List the properties for a user within the ubscription Book L [ALL] RR FR UR login_name; Where, login_name is the login of the user for whom properties are listed, of type string, between double quotes ("). List ubscription Book Users List all the users from the ubscription Book. L [ALL] UR; reate an address to be added to a ubscription Book User RA ADDR address_name FR UR login_name 124 hapter 4 Administering ystems

145 HYALADDR physical_address ADDRDLAY address_display DLVRYDV device_name [FLDR] device_location_path [ADDRDFAUL (RU FAL)] [AV (RU FAL)] [XR (VR expiration_date)] [DLVRYWDW AR start_time D end_time] [MZ GM timezone_id] [ pin]; Where: address_name is the identifier of the address to be added to the user, of type string, between double quotes ("). login_name is the existing user for which the address is to be added, of type string, between double quotes ("). physical_address is the physical address to be added to the user depending on the delivery method, of type string, between double quotes ("). address_display is the display name associated to the physical address, of type string, between double quotes ("). device_name is the name of the delivery device to be associated with the address, of type string, between double quotes ("). device_location_path is the location path where the device resides, of type string, between double quotes ("). expiration_date is the date when the address expires, in the format mm/dd/yyyy. start_time is the start time (24-hour format) of the delivery window, of type time (hh). end_time is the end time (24-hour format) of the deliver window, of type time (hh). timezone_id is the D for the time zone to be specified, of type integer, according to the following list: 1 = (GM-12:00) niwetok, Kwajalein 2 = (GM-11:00) Midway sland, amoa 3 = (GM-10:00) Hawaii 4 = (GM-09:00) Alaska 5 = (GM-08:00) acific ime (U & anada); ijuana 6 = (GM-07:00) Arizona Using ommand Manager to automate key processes 125

146 7 = (GM-07:00) Mountain ime (U & anada) 8 = (GM-06:00) entral ime (U & anada) 9 = (GM-06:00) Mexico ity, egucigalpa 10 = (GM-06:00) askatchewan 11 = (GM-05:00) Bogota, Lima, Quito 12 = (GM-05:00) astern ime (U & anada) 13 = (GM-05:00) ndiana (ast) 14 = (GM-04:00) Atlantic ime (anada) 15 = (GM-04:00) aracas, La az 16 = (GM-03:30) ewfoundland 17 = (GM-03:00) Brasilia 18 = (GM-03:00) Buenos Aires, Georgetown 19 = (GM-02:00) Mid-Atlantic 20 = (GM-01:00) Azores, ape Verde s. 21 = (GM) asablanca, Monrovia 22 = (GM) Greenwich Mean ime : Dublin, dinburgh, Lisbon, London 23 = (GM+01:00) Amsterdam, openhagen, Madrid, aris, Vilnius 24 = (GM+01:00) Belgrade, arajevo, kopje, ofija, Zagreb 25 = (GM+01:00) Bratislava, Budapest, Ljubljana, rague, Warsaw 26 = (GM+01:00) Brussels, Berlin, Bern, Rome, tockholm, Vienna 27 = (GM+02:00) Athens, stanbul, Minsk 28 = (GM+02:00) Bucharest 29 = (GM+02:00) airo 30 = (GM+02:00) Harare, retoria 31 = (GM+02:00) Helsinki, Riga, allinn 32 = (GM+02:00) srael 33 = (GM+03:00) Baghdad, Kuwait, Riyadh 34 = (GM+03:00) Moscow, t. etersburg, Volgograd 35 = (GM+03:00) airobi 36 = (GM+03:30) ehran 37 = (GM+04:00) Abu Dhabi, Muscat 126 hapter 4 Administering ystems

147 38 = (GM+04:00) Baku, bilisi 39 = (GM+04:30) Kabul 40 = (GM+05:00) katerinburg 41 = (GM+05:00) slamabad, Karachi, ashkent 42 = (GM+05:30) Bombay, alcutta, Madras, ew Delhi 43 = (GM+06:00) Almaty, Dhaka 44 = (GM+06:00) olombo 45 = (GM+07:00) Bangkok, Hanoi, Jakarta 46 = (GM+08:00) Beijing, hongqing, Hong Kong, Urumqi 47 = (GM+08:00) erth 48 = (GM+08:00) ingapore 49 = (GM+08:00) aipei 50 = (GM+09:00) saka, apporo, okyo 51 = (GM+09:00) eoul 52 = (GM+09:00) Yakutsk 53 = (GM+09:30) Adelaide 54 = (GM+09:30) Darwin 55 = (GM+10:00) Brisbane 56 = (GM+10:00) anberra, Melbourne, ydney 57 = (GM+10:00) Guam, ort Moresby 58 = (GM+10:00) Hobart 59 = (GM+10:00) Vladivostok 60 = (GM+11:00) Magadan, olomon s., ew aledonia 61 = (GM+12:00) Auckland, Wellington 62 = (GM+12:00) Fiji, Kamchatka, Marshall s. pin is the pin to be assigned to the address, of type string, between double quotes ("). Alter an address from a ubscription Book User ALR ADDR address_name FR UR login_name [ADDR new_address_name] [HYALADDR physical_address] [ADDRDLAY address_display] [DLVRYDV device_name [FLDR] Using ommand Manager to automate key processes 127

148 device_location_path] [ADDRDFAUL (RU FAL)] [AV (RU FAL)] [XR (VR expiration_date)] [DLVRYWDW AR start_time D end_time] [MZ GM timezone_id] [ pin]; Where: address_name is the identifier of the user's address to be modified, of type string, between double quotes ("). login_name is the existing user for which the address is to be modified, of type string, between double quotes ("). new_address_name is the new identifier of the user's address, of type string, between double quotes ("). physical_address is the physical address to be added to the user depending on the delivery method, of type string, between double quotes ("). address_display is the display name associated to the physical address, of type string, between double quotes ("). device_name is the name of the delivery device to be associated with the address, of type string, between double quotes ("). device_location_path is the location path where the device resides, of type string, between double quotes ("). expiration_date is the date when the address expires, in the format mm/dd/yyyy. start_time is the start time (24-hour format) of the delivery window, of type time (hh). end_time is the end time (24-hour format) of the deliver window, of type time (hh). timezone_id is the id for the time zone to be specified, of type integer. pin is the pin to be assigned to the address, of type string, between double quotes ("). Delete an address from a ubscription Book User DL ADDR address_name FRM UR login_name; Where: address_name is the name of the address to be deleted from a user, of type string, between double quotes ("). login_name is the user from which an address is to be deleted, of type string, between double quotes ("). 128 hapter 4 Administering ystems

149 List the properties for a ubscription Book User Address L [ALL] RR FR ADDR address_name FR UR login_name; Where: address_name is the user's address for which the properties are to be listed, of type string, between double quotes ("). login_name is the user that contains the address, of type string, between double quotes ("). List all the addresses from a ubscription Book User L [ALL] ADDR FR UR login_name; Where, login_name is the user for whom to list addresses, of type string, between double quotes ("). rigger a arrowcast erver ervice RGGR RV service_name [FLDR] location_path [UBR subscription_set1 [, subscription_set2 [, subscription_setn]]]; Where: service_name is the name of the service to be run immediately, of type string, between double quotes ("). location_path is the folder path where the service is located, of type string, between double quotes ("). subscription_setn is the name of the subscription set (or list of subscription set names) to be used with this service, of type string, between double quotes ("). Refreshing imported files o distribute static content or template files to the user, you can import the static content or the templates files to the arrowcast erver system and then build services to deliver the imported files to the user. he imported files are stored in the arrowcast erver repository and are not connected to their source location. As a result, if the content of the source file changes, the imported file stored in the arrowcast erver repository is not updated. You have to manually select each imported file, Refreshing imported files 129

150 browse to its source location and re-import the file. he Refresh mported file feature simplifies this process by allowing you to update imported files. his feature has the following advantages: You can select multiple imported files and perform a mass refresh. All the selected files are updated in the arrowcast erver repository. You can search for imported files in a folder or the entire system and then perform a mass refresh to import the updated files. Before you update the imported files, ensure that you have not changed the path and the file name of the imported files. f you have changed the path or the file name, you have to browse to the updated location or enter the new path to update the imported files. When updating the selected files, the Refresh mported File dialog box displays a progress bar that indicates whether the files are successfully updated or not. t also has the option to view the log file, which stores the following details: date-timestamp when the import process began result of the import process; whether the file was successfully updated or not and the date-timestamp when the process ended A log file is generated each time you update the imported files. You can also access the log file from the following location: \Microtrategy\arrowcast erver\delivery ngine he naming convention for the log file is as follows: Filemportummary "date-time".log f the log file is not created, an error message is displayed and the process of updating the files is not initiated. For steps to import and refresh the files, see reating ublications and ontent ection Documents in the arrowcast erver Application Designer Guide. 130 hapter 4 Administering ystems

151 ystem Administrator nterfaces R F A 131

152 R F A 132 ection ystem Administrator nterfaces

153 5 Accounts Dialog Box HAR 5 5.Add arrowcast erver Administrative he Add arrowcast erver Administrative Accounts dialog box allows you to add new users to the Delivery ngine system. For steps to add and remove accounts, see Managing Administrator Accounts. R F A Accessing the Add arrowcast erver Administrative Accounts dialog box xpand Administration. Right-click Accounts and select ew Account. he Add arrowcast erver Administrative Accounts dialog box opens. rerequisites Before you can add an account, you must know the Windows login of the new user and know what roles the new account will need. For more information, see Microtrategy arrowcast erver architecture. Any account that is granted the ystem Administrator role must have administrator permissions on every machine in the system. therwise, that account cannot correctly modify the system configuration. Add arrowcast erver Administrative Accounts dialog box layout When you first access the Add arrowcast erver Administrative Accounts dialog box, it loads the Windows users from the network. he status of the load is displayed below the users list. You can cancel the load by clicking top. he left side of the dialog box lists all the users in the selected Windows domain. You can select a different domain from the Windows domain drop-down list. 133

154 R F A he right side of the dialog box lists the arrowcast erver users, with their assigned roles. You can use the Add and Remove buttons to add users to the arrowcast erver Administrative Accounts and to remove arrowcast erver users. lick Modify rivileges to access the Assign Administrative rivileges to Account dialog box. For more information, see Assign Administrative rivileges to Account Dialog Box. 134 hapter 5 Add arrowcast erver Administrative Accounts Dialog Box

155 6 Box HAR 6 6.Administrative otification Dialog he Administrative otification dialog box provides additional capabilities for sending notification messages regarding the arrowcast erver system, service, and related events. Administrators can configure these notifications and choose the delivery addresses for the notifications. his feature allows unattended execution and monitoring of the arrowcast erver system. Use the Administrative otification dialog box to configure alerting messages to the arrowcast erver ystem administrator regarding the following: ystem wide failure and machine failure such as, machine or DM/ startup and shutdown. Failure or success of a service with details on service execution summary that include recipient resolution, delivery, segment execution, retries and failover. Failure or success of a particular within a service. For more information, see onfiguring a arrowcast erver ystem. R F A Accessing the Administrative otification dialog box From the ools menu, select et Administrative otification. he Administrative otification dialog box opens. rerequisites he Administrative otification relies on the Microtrategy Logging erver for proper operation. f the Microtrategy Logging erver is not configured properly, or you have not connected to a system from this installation of arrowcast Administrator, you cannot configure the Administrative otification interface. For more information, see the arrowcast erver nstallation and onfiguration Guide. 135

156 Administrative otification dialog box layout R F A n the Administrative otification dialog box, you can configure the messages and specify the notification addresses for the messages. otification types include the following: ystem Wide Failure: ndicates a system-wide inability to operate. ervice or Machine Failure: ndicates the failure of a service or a machine but does not typically indicate failure of the system as a whole. Recipient Group Failure: ndicates the failure of a segment or the transmission to a specific group of recipients, but typically does not indicate a system, service, or machine failure. Recipient Level Failure or emporary Failure: ndicates a temporary failure or a recipient-level permanent failure such as an invalid address. ervice xecution nformation: rovides service execution processrelated information such as service execution start, loading of service definition, start of segmentation, service execution completion, and so on. egment xecution nformation: rovides segment execution process-related information such as segment assignment to an xecution ngine, recipient resolution, segment failover, segment completion, and so on. ystem nformation: rovides general system-wide information such as system startup, system shutdown, distribution manager startup, execution engine failure, system component status, and so on. Recipient Level: rovides recipient level information. elect the check box corresponding to a notification type to define the messages for that notification. he Governing and Filtering button is enabled only when you select a notification type. Governing and Filtering: lick to open the Administrative otification Request dialog box. For details on defining the settings, see Administrative otification Request dialog box. -mail Address(es): pecify the address to which the notification is to be sent. You can specify multiple addresses separated by a semicolon. dit Device: pens the Device ditor dialog box that allows you to specify the device transmission and formatting properties for the (M) information transmitter. For more details on the Device ditor, see Device ditor. 136 hapter 6 Administrative otification Dialog Box

157 Administrative otification Request dialog box he Administrative otification Request dialog box allows you to set the message level system information and filtering details for a notification type. pecify the following information: -mail ubject: By default, this field displays the name of the system and the notification type that you have selected. You can also specify your own subject line in this field. Governing: elect this check box to set the governing details for each message type. You can specify the number of alerts that you want to receive within a specified time. he default value for each message type is set to receiving not more than 10 alerts within an hour. You can choose the governing levels that are appropriate for your system. For example, for any message type, if you specify the number of alerts as 20 and number of hours as two, the first 20 messages in a two-hour window are sent to the administrator. f 20 messages are logged within the first 30 minutes, no further alerts are sent for the remaining two-hour window, but the messages will continue to log. hese messages can be viewed in the DLog file in the location :\rogram Files\Microtrategy\arrowcast erver\delivery ngine. he time slots are calculated based on a moving window from the delivery of the first message. Filtering: elect this check box to refine the message codes for which you want to receive notifications. You can choose to include a set of codes for which you want notification, or specify a set of codes for which you do not want any notification. Do one of the following: hoose from the list of pre-defined codes provided in the dialog box. Add your own codes by giving code name and description in the ode and the Description fields. hen, click Add ode to add code. You can also specify a filtering criterion, which is applied to the list of codes provided in the dialog box, by using Filter list by field. t helps to locate the required codes. You can also choose to include or exclude a set of codes that you selected. R F A Administrative otification dialog box layout 137

158 R F A 138 hapter 6 Administrative otification Dialog Box

159 7 Dialog Box HAR 7 7.Assign Administrative rivileges to Account he Assign Administrative rivileges to Account dialog box allows you to assign or remove privileges to Delivery ngine users or accounts. A privilege, or role, defines which objects the account can create and which operations it can perform. he different Microtrategy arrowcast erver privileges are: ystem Administrator, who manages the entire system Application Administrator, who administers application objects only, even those owned by other users ervice Designer, who administers application objects only and who cannot modify objects owned by other users ubscription Administrator, who can access only the subscription book For more information on the dialog box, see Managing Administrator Accounts. R F A Accessing the Assign Administrative rivileges to Account dialog box xpand Administration, then expand Accounts, and double-click the account name to modify. he Assign Administrative rivileges to Accounts dialog box opens. f you are creating a new account, you can access this dialog box by clicking Modify rivileges on the Add arrowcast erver Administrative Account dialog box. rerequisites Before you can assign privileges, you should: Understand the different roles Have created an account For more information, see Microtrategy arrowcast erver architecture. 139

160 Assign Administrative rivileges to Account dialog box layout R F A A new account is automatically granted the service designer privileges. he left side of the dialog box contains a list of the privileges or roles that have been granted to the account. he right side of the dialog box lists the available privileges or roles. he Add and Remove buttons in the middle of the screen allow you to add the selected role to the user or remove the selected role from the user account. lick K to save your changes. 140 hapter 7 Assign Administrative rivileges to Account Dialog Box

161 8 Box HAR 8 8.onfigure bject Management Dialog he onfigure bject Management dialog box allows you to select options that will be applied when migrating arrowcast erver objects between systems. o invoke an object management operation, drag and drop an object from one system to another. A likely scenario involves development, testing, and production systems. All object types can be migrated, except for the system object, distribution managers, and execution engines. For more information, see onfiguring a arrowcast erver ystem. R F A Accessing the onfigure bject Management dialog box From the ools menu, select onfigure bject Management. he onfigure bject Management dialog box opens. rerequisites You should understand the following: he types of object management operations that can be performed Which system is the source and which is the target Which object or objects you want to migrate How object dependencies work within an bject Repository For more information, see Administering multiple systems. onfigure bject Management dialog box layout he onfigure bject Management ptions dialog box includes two decision tables in which you specify the rules you want to use for object management. he first table has four columns. he first column lists the available types of operation. For each, make the appropriate selection from the remaining columns. ource object refers to the object being migrated. ource 141

162 R F A repository or system is the place the object is coming from. arget object refers to the object being created or updated. arget repository or system is the destination of the object. For the reate type, Always is the only option since the source object will be new to the target system. By default, all new objects are migrated and modify the target system. Any time an object is written from the source repository into the target repository, the create and modification times of the object in the target repository are set equal to the modification time of the source object. For other types of operations, you can choose one of the following options: Always modify the target: hanges are made automatically ever modify the target: he target system s version of the object will not be modified. rompt during the migration: (selected by default) When you migrate an object that already exists in the target system, the onflict Resolution Dialog Box opens so that you can decide whether to make the change or not. f you select the Always or ever option, you are not prompted. he changes either happen automatically or not, with no notification. he rules for determining the type of operation for an object are described below. n all cases except reate, comparing the creation and modification times determines the state of an object. verything is relative to moving an object from the source to the target repository. reate: he object being replicated does not exist in the target system. Accepting this action creates the object in the target system using the definition of the object in the source system Refresh: he object being replicated exists in the target system, and has the same definition as the object in the source system. either object definition has been modified since the object was last migrated from one system to the other. Accepting this action does not cause a material change to the definition of the object in the target system. Update: he object exists in the target system, and its definition has not been modified since the object was last migrated from one system to the other. However, the definition of the object in the source system has changed since the object was last migrated. Accepting this action updates the definition of the object in the target system to be the same as the newer definition of the object from the source system. 142 hapter 8 onfigure bject Management Dialog Box

163 verwrite: he object exists in the target system, and the objects in both the source and target systems have been modified since the object was last migrated. Accepting this action causes the definition of the object in the target system to be replaced with the definition of the object from the source system, which loses any changes that were made to the object in the target system since the object was last replicated. Revert: he object exists in the target system, and its definition has been modified since the object was first replicated from one system to the other. he object in the source system has not been modified since the object was last migrated. Accepting this action causes the object in the target system to lose the changes that were made to it since the object was last replicated. he second table on this dialog box provides additional choices for certain types of conflicts: ame in use: Another object (or folder) is already using the name in the target repository s folder where the object is being saved/updated. Folder mismatch: he source and target object s containing folder has changed. elect whether these conflicts should be resolved automatically during object migration or whether you should be prompted during the migration to make a decision yourself. R F A onfigure bject Management dialog box layout 143

164 R F A 144 hapter 8 onfigure bject Management Dialog Box

165 9 Dialog Box HAR 9 9.onflict Resolution he onflict Resolution dialog box allows you to resolve conflicts that occur when you copy one or more objects from one system repository to another. R F A Accessing the onflict Resolution dialog box he onflict Resolution dialog box opens when you copy one or more objects from one system repository (the source repository) to another system repository (the target repository) and there is a conflict between one of the objects being copied and an object that already exists in the target repository for which the user has selected prompt in the onfigure bject Management dialog box. his dialog box only opens when, in the onfigure bject Management dialog box, you select the rompt During opy option for an object s ype of peration or onflict when copying it from the source to the target. For more information, see onfigure bject Management Dialog Box. rerequisites You should understand the following: he types of object management operations that can be performed Which system is the source and which is the target How you plan to resolve any conflicts that arise For more information, see Administering multiple systems. onflict Resolution dialog box layout he onflict Resolution dialog box includes a table in which you indicate whether to accept the indicated change to the target system or to reject the indicated change and keep the object in the target system as it currently exists. ix columns appear in this table. 145

166 R F A he first column, Action, lists the available types of operation, as described below. reate: he source object does not exist in the target repository. All objects that do not exist in the target repository are automatically created. A new object can be created using the same name as an existing object. n this case, when a name conflict occurs, you are prompted to accept the change. his means the new object is renamed and created, preserving all potential object dependencies. Refresh: he object being replicated exists in the target system, and has the same definition as the object in the source system. either object definition has been modified since the object was last migrated from one system to the other. Accepting this action does not cause a material change to the definition of the object in the target system. Update: he object exists in the target system, and its definition has not been modified since the object was last migrated from one system to the other. However, the definition of the object in the source system has changed since the object was last migrated. Accepting this action updates the definition of the object in the target system to be the same as the newer definition of the object from the source system. verwrite: he object exists in the target system, and the objects in both the source and target systems have been modified since the object was last migrated. Accepting this action causes the definition of the object in the target system to be replaced with the definition of the object from the source system, which loses any changes that were made to the object in the target system since the object was last replicated. Revert: he object exists in the target system, and its definition has been modified since the object was first replicated from one system to the other. he object in the source system has not been modified since the object was last migrated. Accepting this action causes the object in the target system to lose the changes that were made to it since the object was last replicated. he second column, ype, lists the type of object affected by the conflict. he third column, ame, lists the name of the object affected by the conflict. n both cases, the objects indicated are in the target system. he fourth column, hange details, provides the details on the potential change to the target system due to copying an object or objects. xamples of these changes include renaming an object because a different object already exists in the target system with the same name or moving an object from one folder to another because the location of the object in the source 146 hapter 9 onflict Resolution Dialog Box

167 system has changed. When an object is renamed, the original name is retained and a number in brackets is added to the end. For example, if an object is named roject 1, it is renamed roject 1 [1]. he fifth and sixth columns, Accept and Reject, allow you to choose either to accept or reject the change indicated in the fourth column. o select one action for all the objects, click the column header. For example, to accept all the changes indicated in the fourth column for all the objects listed, click the header Accept. lick K to resolve the conflict according to your selections or click ancel to close the onflict Resolution dialog box without copying any of the objects listed. R F A onflict Resolution dialog box layout 147

168 R F A 148 hapter 9 onflict Resolution Dialog Box

169 10 10.Device ditor HAR 10 he Device ditor is a tabbed dialog box that allows you to create a new device for a specific information transmission module. You can specify device transmission and formatting properties. t also allows you to modify an existing device. For more information about the steps to create new devices, see onfiguring nformation ransmitters. R F A Accessing the Device ditor xpand Administration, then right-click the Devices. elect ew, then Device. he elect nformation ransmitter dialog box opens. Doubleclick the appropriate M type. he Device ditor opens. r, you can double-click an existing device in the Devices folder. rerequisites Before you create a device, you must create an information transmission module and appropriate document formatting modules. For steps to create these modules, see Working with Document Formatters and onfiguring nformation ransmitters. Device ditor layout Before you access the Device ditor, you must select an information transmitter to use. After you select the information transmitter, the Device ditor opens with the ransmission tab displayed. he other tabs in the editor vary depending upon what document formatters the selected information transmitter supports. For example, the -mail (M) module that is used for the e- mail (M) information transmitter supports plain text, xcel, and HML document formats. he M ransmitter supports only plain text document formats, and therefore so does the M (M) information transmitter. 149

170 -mail (M) device R F A For a device associated with the -mail (M) information transmitter, the Device ditor displays the following tabs: ransmission tab laintext tab xcel tab HML tab DF tab File device For a device associated with the File information transmitter, the Device ditor displays the following tabs: ransmission tab laintext tab xcel tab HML tab DF tab rint device For a device associated with the rint information transmitter, the Device ditor displays the following tabs: ransmission tab laintext tab HML tab DF tab M (M) device For a device associated with the M (M) information transmitter, the Device ditor displays the following tabs: ransmission tab laintext tab 150 hapter 10 Device ditor

171 Web (ortal) device For a device associated with the Web (ortal) information transmitter, the Device ditor displays the following tabs: ransmission tab laintext tab xcel tab HML tab DF tab Wireless (M) R F A ransmission tab laintext tab xcel tab HML tab DF tab elect nformation ransmitter dialog box his dialog box lists the information transmitters available to the arrowcast erver system. Double-click the information transmitter to use. he Device ditor opens with the ransmission tab displayed. ransmission tab he ransmission tab appears for all devices, regardless of the information transmitter it is used for. ts contents are provided by the information transmission module. -mail (M) ransmission tab he -mail (M) module used for the -mail (M) information transmitter includes the following tabs: Message Format MM ptions if MM transmission is chosen Delivery ptions Device ditor layout 151

172 R F A Message Format You can choose between UUncoded and MM. UUncoded accepts only one plain text body in U-A, no HML body, and any number of attachments. very field in the message (recipient display names, subject, and so on) should also be in U-A. he attachments are encoded using the UX-to-UX method, which is supported by most clients and other third-party software. his message format is suggested for any client or gateway that does not support MM. Multipart MM allows many message bodies and multiple character sets. haracter sets other than U-A can be used. Multi-part, related, and alternative message bodies and text headers are also allowed. MM ptions his tab is available only if MM transmission is selected on the Message Format tab. You can select whether to use quoted-printable or base64 encoding for each of the following publication sections: laintext and HML Body ext Attachment Binary Attachment You can also select 7 bit A encoding for laintext and HML Body publication section. Base64 encoding is a process by which every three bytes of data are changed into four six-bit values. hese values are then mapped to a 64- entry lookup table in which the selected data represents A codes that are generally printable. Base64 uses the following alphabet: [A-Z][a-z][0-9] +, /. his results in all of the binary data being encoded into printable characters that can be transmitted over the nternet without fear of bit loss. Base64 encoding is strongly recommended for any binary, image, or multibyte character set data. Quoted-printable encoding preserves most printable characters and only encodes non-printable or special characters. You can read the encoded text, unlike base64 encoding, but it does not preserve space. Use quotedprintable only for text files and HML or plain text message bodies, not for binary data. ome devices do not support the use of character sets other than U-A for certain portions of multi-part MM s. hese portions include the subject line, the names of attached files, and the address display names. 152 hapter 10 Device ditor

173 elect Use U-A for ubject, Attachment ames, and Display ames (ender, Reply-o, and Address) to ensure that such devices can process s correctly. f the Use U-A for ubject, Attachment ames, and Display ames (ender, Reply-o, and Address) check box is selected, the application designer must ensure that the names of any objects being sent as attachments to this device are no more than eight characters in length and must use only standard A characters. he subject must also contain only A characters. f any of these conditions are not met, the message is not sent. f the Use U-A for ubject, Attachment ames, and Display ames (ender, Reply-o, and Address) check box is not selected, select the Do not put quotes around non U-A Display ames check box if the client displays an extra set of double quotes around the display names. his is to avoid encoding a set of quotes along with the display names, which is superfluous when the client adds an extra set of quotes around the decoded string. his check box should only be selected for Microsoft utlook 98 and Microsoft utlook You can select the mbed Flash ontent check box to support Flash content in the body of the . However, this check box can remain cleared if you want to deliver the Flash content as an attachment (.mht). he mbed Flash ontent check box is cleared by default. o support this Flash content, the following conditions must be satisfied: You should have Flash layer 9 installed on your computer. lder versions of Flash are not supported. f you do not have Flash layer 9, you can download it from he clients must have ActiveX enabled for delivery of Flash content in the body of an . ActiveX is not necessary when delivering Flash files as attachments to s. You can also select whether to mbed HML Attachments into the message body. f HML attachments are not embedded, they are sent as unrelated attachments. f you opt to embed HML attachments, you can also choose to mbed All Attachments. mbed All Attachments should be chosen for Microsoft utlook 98 and Microsoft utlook clients. R F A Device ditor layout 153

174 elect the Remove ontent-location MM header check box to prevent broken links to attachments in s forwarded using Microsoft utlook Web Access. his check box is available only for arrowcast erver version and later. R F A Delivery ptions o use a smart host, enter the mart Host Address and ort umber. he smart host is a machine that receives all outgoing messages and is responsible for delivering them to the final destination. his feature is useful if you have a powerful server to use for all outgoing messages, since the communication between arrowcast erver and the smart host is faster than that between arrowcast erver and the mail host of each recipient. elect the option to Use mart Host Always to use only the smart host to deliver the message. therwise, the message is sent directly, and the smart host is used only if the direct connection fails. File ransmission tab he File module used for the File information transmitter includes the following tabs: General properties Advanced properties General properties he General roperties tab allows you specify the file location, either a full path, partial path, or macros, using the following objects: File Location allows you to enter a full or partial path for delivery of files. he File information transmitter allows write access to anywhere on the arrowcast erver local drive. o prevent this, make sure that all File information transmitter devices are using relative paths (for example, \\server\share\%%hysicaladdress%%) instead of absolute paths (for example, %%hysicaladdress%%). f using absolute paths, it is recommended that the reate required folders and verwrite files with same name options are disabled and the Append timestamp to file name option is enabled in the device's Advanced roperties. nsert Macro allows you to see a list of variables that can be used to personalize each transmission. lick and choose from the following: %%Userame%% %%hysicaladdress%% 154 hapter 10 Device ditor

175 %%Date%% %%ime%% File roperties specifies the attribute of the file for transmission. heck one of the following options: Read only Archive ompress Advanced properties he Advanced roperties tab offers options for system and backup file location. You can select the following advanced file system settings: reate required folders creates folders if the specified file path is not present. his is selected by default. verwrite files with the same name determines whether the information transmitter overwrites existing files with the same name. his is selected by default. You must also clear the Append timestamp to file name check box, otherwise a new file is created each time the service is executed. Append timestamp to file name adds the date and time of the file creation to the end of the file name. his is selected by default. Append to file (text documents only) determines whether the information transmitter appends the contents of the new file to the existing file each time the service is executed. For example, if you have a service that contains a text document and it has delivery to a file with the Append to file check box selected, a text file is created when the service is executed for the first time. After that, whenever the service is executed, the contents of the new document are appended to the existing file. You can select the Append to file check box only if you clear the verwrite files with the same name check box. You must also clear the Append timestamp to file name check box, otherwise a new file is created each time the service is executed. umber of retries allows you to specify how many times file transmission will be attempted if a temporary failure occurs. ime between retries allows you to specify how much time is allowed between a failed delivery attempt and a retry. Delivery timeout allows you to specify how much time is allowed before the transmission times out. R F A Device ditor layout 155

176 R F A he device level settings can override the general settings defined at the transmitter level. For example, if the transmitter requires you to equip files with the read-only property, but a device has the verwrite files with the same name check box selected, the files will be overwritten, despite the transmitter settings. You can also specify the following information with respect to a backup file location: ave messages to backup file location if delivery fails allows you to provide a location for a backup file if delivery to the original file location fails. Backup File Location allows you to enter the path and file name for delivering files if delivery to the original file location fails. ote that the path and file name cannot exceed 150 characters. f you clear the verwrite files with the same name, Append timestamp to file name, and Append to file check boxes but you select the ave messages to backup file location if delivery fails check box, and specify a location for the backup files, the files are stored in the backup file location when the service is executed. rint ransmission tab he rint module used for the rint information transmitter includes the following tabs: General roperties Advanced roperties General roperties he General roperties tab allows you to specify standard printer settings for printer location and printer properties. n the rinter Location section, you can specify the default printer location by selecting it or entering it in the box. You can add a new printer to the list of available printers and then select it by clicking Add rinter. You can also allow for user addresses that contain printer locations to override your printer specification by selecting the check box. n the rinter roperties section, you can specify the properties for the default print device, including the number of copies, scale, print quality, paper source, paper size, and whether printed copies are collated. o use the standard printer defaults, click Load printer defaults. 156 hapter 10 Device ditor

177 When a user enters a new printer address, usually on the Web or through the ubscription ortal, the property settings of the new printer are overridden by those of the default printer set by the administrator. t is possible that settings for paper source, print quality, and paper size may or may not match the capacities of the user s printer, depending on its make and model. You can create different print devices for each of the printer models. However, testing is highly recommended if a single device is used for different types of printers. You can specify the orientation of HML documents by selecting the appropriate option: ortrait prints vertically on the page. Landscape prints horizontally on the page. For DF documents, you can specify the following options: ostcript Level indicates the version of ostcript to use on this printer, Level 1, 2, or 3. hrink to fit specifies that the content being printed should be resized, if needed, to fit on the paper used by this printer. Reverse pages instructs the printer to print from back to front instead of front to back (the default is front to back). rint range indicates which pages to print, if multiple pages are in the print request. dd or even pages identifies whether you want to print all pages (even and odd) or just odd or just even pages. he DF properties mentioned take effect only if Adobe Acrobat 6.0 rofessional is installed on all execution engine machines. R F A Advanced roperties he Advanced roperties tab offers options for backup delivery, governing, and application priority. You can elect to print or save documents to a backup location if the primary printer fails. elect the check box, then choose from the following options: rint files to the following backup printer allows you to specify a backup printer location. ave files to the following backup file location allows you to specify a backup file location. Device ditor layout 157

178 R F A You can specify the following governing settings: umber of retries indicates how many times the printer attempts to print if the print request fails. ime between retries (seconds) indicates the number of seconds between each retry attempt. Delivery time out (minutes) indicates the number of minutes before the delivery times out. File Location specifies a location where documents are saved temporarily during execution. By default, the application s runtime path is used. You can specify which application has priority if another application or interactive user is using Adobe while arrowcast erver is trying to print DF documents. hoose from the following: ther applications and interactive users (DF documents are saved to the backup file location, if specified above): his allows other applications or users to continue working while the arrowcast erver document is saved to a backup file location. f no backup file location is defined, an error is logged. arrowcast erver (this ends other Adobe applications automatically): his allows the arrowcast erver DF document to print, while ending all other Adobe processes. M (M) ransmission tab he M (M) ransmitter used for the M (M) information transmitter includes the maximum message size transmitter configuration option. Maximum message size he maximum message size for M devices is an integer value between 1 and 160 characters. f a message sent exceeds the maximum message size, the message is truncated to the maximum message size. Web (ortal) ransmission tab o transmission settings are required for the Web (ortal) M. Wireless (M) ransmission tab he Wireless (M) ransmission tab uses the same module and therefore has the same features as the -mail (M) ransmission tab. 158 hapter 10 Device ditor

179 laintext tab he laintext tab allows you to select whether the selected device supports plain text content. elect the check box to support plain text document format for the device. Formatting Module: elect a document formatter from the available plain text document formatters. his tab includes the following tabs: Grid Formatting: Allows you to choose whether to pad grid cells, how to pad them, whether to separate columns, and the characters to use as separators. ell adding: Allows you to select the characters with which to pad cells. his is a process by which the lengths of the strings in a column are made equal in length through the use of tab-aligning characters and white-space characters. tring ubstitution: Allows you to enter text to be converted to other characters. R F A xcel tab he xcel tab allows you to select whether this device supports xcel content. f you choose to support xcel documents, you can select a document formatter from the drop-down list of available xcel document formatters. o properties need to be configured for this type of document formatter. HML tab he HML tab allows you to select whether this device supports HML content. f you choose to support HML document, you can select a document formatter from the drop-down list of available HML document formatters. You also have the option to support images. DF tab he DF tab allows you to select whether this device supports the transmission of DF documents. nly the DF document formatter is available. You can select the check box to use this document formatter. o properties need to be configured for this document formatter. Device ditor layout 159

180 R F A 160 hapter 10 Device ditor

181 11 Box HAR Distribution Manager onfiguration Dialog he Distribution Manager onfiguration dialog box allows you to create a new distribution manager (DM). You can also change an existing DM state (running or stopped). For more information on Distribution Manager, see Managing Distribution Managers. R F A Accessing the Distribution Manager onfiguration dialog box xpand Administration, then right-click Distribution Managers. elect ew, then Distribution Manager. he ew Distribution Manager onfiguration dialog box opens. r, double-click an existing DM to access the Distribution Manager onfiguration dialog box, which is the same as the other interface except you cannot change the selected machine. rerequisites You should: Know the name of the machine you wish to use as a distribution manager Understand the concept of a distribution manager Understand how primary and backup distribution managers work together, if you have the nterprise dition of Microtrategy arrowcast erver For more information, see the following chapters: Microtrategy arrowcast erver architecture onfiguring Machines 161

182 Distribution Manager onfiguration dialog box layout R F A he Distribution Manager onfiguration dialog box contains a browse button that allows you to select a machine to use as the distribution manager (DM) when you create a new DM. f you are changing the status of an existing DM, this browse button is grayed out, but the name of the machine is still readable. You can view the Rank of the DM, but you cannot change it. ne of the two status buttons, Run or top, is selected. hange the status by clicking the other button. When you have made your changes, click K to save them or ancel to exit without saving your changes. 162 hapter 11 Distribution Manager onfiguration Dialog Box

183 12 xcel Dialog Box HAR Document Formatter - he Document Formatter - xcel dialog box is a single point of contact for document formatters based on the xcel document formatting module (DFM). t defines the formatting properties of an xcel document formatter. hese settings are applied to a document during service execution. For more information, see Working with Document Formatters. R F A Accessing the Document Formatter - xcel dialog box xpand Administration, then expand Document Formatters. Doubleclick xcel. he Document Formatter - xcel dialog box opens. rerequisite You should know the drive and path that you want to use to store temporary files, which are created and deleted by the xcel document formatter during service execution. Document Formatter - xcel dialog box layout While different DFMs can be used, only the xcel DFM has properties that must be set. he Document Formatter - xcel dialog box has two areas: General roperties and rror Handling. he General roperties area contains the Working Directory. his location is used for the temporary creation of files, so it should reside on a drive or partition that is separate from the operating system and program files. he default location is %Application ath%\delivery ngine\emp, where %Application ath% is the folder in which arrowcast erver is installed. For example, :\rogram Files\Microtrategy\arrowcast erver. lick the browse 163

184 R F A button to point to the required folder. A message appears below the Working Directory box giving you information about your directory selection, such as whether it is valid. he General roperties category also has a check box to indicate that Microsoft xcel clients should recalculate all formula values when xcel workbooks generated by arrowcast erver are opened. he rror Handling area allows you to set how the DFM deals with errors: Fail the document: f an error occurs the xcel document is not sent. runcate the Document lement (if it is a grid): As much of the document element as possible is sent. his setting is applied only if the document element is a grid. Replace with the following string: f possible, the text you enter replaces the flawed document element. elect one of the following, which applies if the number of cell formats in the document exceeds the maximum possible number of cell formats in xcel: Fail the document: f the maximum is exceeded the document is not sent. gnore the additional cell formats: f the maximum is exceeded the extra cell formats are ignored and the document is sent anyway. 164 hapter 12 Document Formatter - xcel Dialog Box

185 13 roperties Dialog Box HAR dit Available User he dit Available User roperties dialog box allows you to add and remove user properties and related property options to be used in service content. R F A Accessing the dit Available User roperties dialog box From the ools menu, select dit Available User roperties. he dit Available User roperties dialog box opens. rerequisites Before you edit user properties, you should understand how user properties are used in information objects. For more information, see Microtrategy arrowcast erver architecture. dit Available User roperties dialog box layout he available user properties are listed in the User roperties section on the left. You can add and remove properties by clicking the Add and Remove buttons below this section. he available user property options are listed in the User roperty ptions (optional) section on the right. You can add and remove options by clicking the Add and Remove buttons below this section. o specify options for a particular property, select the property from the list on the left. he available options are displayed on the right. You can also add options, if required. For example, the itle property contains Mr., Mrs., and Ms. as options. You may wish to add Dr. as another option. lick K when you finish editing the user properties. 165

186 R F A 166 hapter 13 dit Available User roperties Dialog Box

187 14 Box HAR xecution ngine onfiguration Dialog he xecution ngine onfiguration dialog box allows you to create a new execution engine (). t also allows you to: dle an execution engine Run an execution engine pecify the number of segments that can run on an execution engine simultaneously top an execution engine For more information, see Managing xecution ngines. R F A Accessing the xecution ngine onfiguration dialog box xpand Administration, then right-click xecution ngines. elect ew, then xecution ngine. he xecution ngine onfiguration dialog box opens. r, double-click an existing to access the xecution ngine onfiguration dialog box, which is the same as the other interface except you cannot change the selected machine. rerequisites You should: Know the name of the machine you wish to use as an execution engine Understand the concept of an execution engine Understand how primary and backup execution engines work together, if you have the nterprise dition of Microtrategy arrowcast erver 167

188 xecution ngine onfiguration dialog box layout R F A he xecution ngine onfiguration dialog box contains a browse button that allows you to select a machine to use as the execution engine, when you create a new one. f you are changing the status of an existing execution engine, this browse button is grayed out, but the name of the machine is still readable. You can change the Maximum number of simultaneously executing segments. ne of the three status buttons, Run, dle, or top, is selected. hange the status by clicking the appropriate button. When you have made your changes, click K to save your changes. 168 hapter 14 xecution ngine onfiguration Dialog Box

189 15 Wizard HAR nformation ource he nformation ource Wizard lets you define and modify an information source using a Microtrategy nformation ource Module (M). An information source lets you configure the connection to a specific project on the selected Microtrategy ntelligence erver. You can use the nformation ource Wizard to define the configuration settings and to select the project from which you want to retrieve reports. For steps to create an information source, see onfiguring nformation ource Modules. You can create your own, customized information sources that can be used with services. For steps to write a M component, implement the appropriate interfaces with their definitions and parameters, and register a customized information source with arrowcast erver, see the online Microtrategy Developer Library (MDL). R F A Accessing the nformation ource wizard xpand Administration, and then expand nformation ource Modules. Right-click a Microtrategy nformation ource Module. elect ew, then nformation ource. he ew nformation ource dialog box opens. nter the name of the information source and click Define to define the information source. he nformation ource Wizard opens. o modify an existing information source that uses the Microtrategy nformation ource Module, double-click the existing information source. rerequisites Before you create an information source, you should understand how information sources work with information source modules, understand the concepts of security prompts and authentication objects, and register a corresponding information source module. For information on security, see nformation source ecurity in the arrowcast erver Application Designer Guide. 169

190 nformation ource Wizard layout R F A he nformation ource Wizard contains the following pages: nformation ource dialog box Welcome ntelligence erver Microtrategy ntelligence erver roperties dialog box roject dialog box Advanced roperties dialog box Default Language Default Authentication ecurity and Dynamic ubscription upport Default ecurity rompt Resolution dialog box User and ubscription roperties Address roperties ersonalization ummary ave nformation ource dialog box lick ext to go to the next page of the wizard. lick Back to return to the previous page. lick ancel at any time to exit the wizard without saving any changes. nformation ource dialog box his dialog box allows you to enter a ame and a Description for the new information source. he refresh options lets you to refresh an information source when a service is run or a new instance of the information source module is created, instead of reusing an existing instance. his feature is used to tune performance and ensure reliability. For example, even if a custom information source module leaks memory, this feature ensures that the total system memory consumption does not exceed the physical limits. hoose from the following options: ever Refresh the information source Refresh mmediately 170 hapter 15 nformation ource Wizard

191 Refresh after every, and then set the number of information objects (jobs) to run before refreshing the information source. lick Define to continue creating the information source. After you have defined the information source, you are returned to the nformation ource dialog box. lick K to save the new information source. he ave nformation ource dialog box opens. Welcome his page provides a brief overview of the process to create an information source. R F A ntelligence erver his page prompts you for the ntelligence erver Machine ame and ort number of the computer running Microtrategy ntelligence erver. You have to also specify the administrative Login D and assword of the Microtrategy ntelligence erver that you select. his account is used by all users when working with this information source. he users can browse data and create objects on the Microtrategy ntelligence erver appropriate to the ervice Designer and ubscription Administrator roles. he users who administer the arrowcast system need to have the privileges of a arrowcast ystem Administrator group to log on to the Microtrategy ntelligence erver. he arrowcast ystem Administrator group is a part of the ystem Monitors group. his group is defined in Microtrategy Desktop. lick Advanced roperties to access the Microtrategy ntelligence erver roperties dialog box. Microtrategy ntelligence erver roperties dialog box he Microtrategy ntelligence erver roperties dialog box opens when you click Advanced roperties on the ntelligence erver page. his dialog box consists of the following tabs: xecution and Governing rimary erver Backup erver nformation ource Wizard layout 171

192 xecution and Governing R F A You can specify the following information: Request timeout (seconds): Allows you to control the duration for which the Delivery ngine waits for a response from the ntelligence erver. f report generation against the data warehouse is slow, you can adjust this value according to the expected report generation time. nsure that the request timeout limit is greater than the expected run time for the report/document (service) submitted through arrowcast erver. his setting couples with the Maximum number of reconnection attempts setting to limit false failure identifications. Maximum number of reconnection attempts: pecifies the number of times that the Delivery ngine attempts to connect to the ntelligence erver. Maximum number of executing information objects: Allows you to govern the workload that each Delivery ngine places on the ntelligence erver. his ensures that the ntelligence erver is not overloaded for the system resources available to it. Generate DF in arrowcast erver machine: Allows you to shift the processing load and the resource load associated with the DF generation from the ntelligence erver to the arrowcast erver machine or vice versa. hifting the load from the ntelligence erver to arrowcast erver machine is useful when you have an xecution ngine with either less load or more capacity than the ntelligence erver, or when you have multiple high capacity xecution ngine machines which are all using the same ntelligence erver. imilarly, if you have an xecution ngine machine with less capacity than the ntelligence erver you can shift the processing load and resource load associated with the generation of the DF from the arrowcast erver machine to the ntelligence erver. elect this check box to generate DF files in the arrowcast erver machine. Maximum memory consumption for DF file generation (kilobytes): Allows you to specify a memory limit for DF generation if the DF generation takes place on the arrowcast erver machine. f the DF generation takes place on the ntelligence erver, the memory governing settings for DF generation that are specified on the ntelligence erver are considered. 172 hapter 15 nformation ource Wizard

193 f the DF generation requires more memory than that is available for the operation to succeed, partial DF results are returned. he DF generation engine can return partial results due to insufficient memory regardless of whether DF generation takes place in the ntelligence erver or the arrowcast erver machine. f partial DF results are returned, the setting defined in the rror handling tab within the Advanced roperties dialog box of the Desktop Document elector, determines whether the partial DF is transmitted or not. Generate xcel in arrowcast erver machine: Allows you to shift the processing load and the resource load that is associated with the generation of the xcel file from the ntelligence erver to the arrowcast erver machine or vice versa. hifting the load from ntelligence erver to the arrowcast erver machine is useful when you have an xecution ngine with either less load or more capacity than the ntelligence erver, or when you have multiple high capacity xecution ngine machines which are all using the same ntelligence erver. imilarly, if you have an xecution ngine machine with less capacity than the ntelligence erver you can shift the processing load and resource load associated with the generation of the xcel file from the arrowcast erver machine to the ntelligence erver. elect this check box to generate the xcel files in the arrowcast erver machine. Maximum memory consumption for xcel file generation (kilobytes): Allows you to specify a memory limit for xcel file generation if the xcel file generation takes place on the arrowcast erver machine. f the xcel file generation takes place on the ntelligence erver, the memory governing settings for xcel file generation that are specified on the ntelligence erver are considered. f the xcel file generation requires more memory than is available for the operation to succeed, partial results are returned. he xcel file generation engine can return partial results due to insufficient memory regardless of whether the xcel file generation takes place in the ntelligence erver or the arrowcast erver machine. f partial results are returned, the setting defined in the rror handling tab within the Advanced roperties dialog box of the Desktop Document elector determines whether the partial xcel file is transmitted or not. R F A rimary erver he rimary erver tab allows you to view the clustering information and set the Load Balance Factor for the rimary ntelligence erver. You can specify the following information: nformation ource Wizard layout 173

194 R F A Machine name and ort number: Displays the Machine name and ort number of the rimary ntelligence erver. You cannot make any changes to these server details. Use ntelligence erver cluster, if available: elect the check box to display the rimary luster table for specifying the clustering details of the rimary ntelligence erver. his setting is also applicable to the Backup erver to allow the Backup luster table to be displayed in the Backup rver tab. Refresh: lick Refresh to view the information displayed in the rimary luster table. he Refresh button refreshes the list of nodes. he default value of the load balancing factor for all new nodes is set to 1, and the value of the port number is received from the cluster. You cannot make any changes to the erver name and the ort number. You can only specify the Load Balance Factor for each server as follows: Default value = 1 Minimum value = -1 Maximum value = lick how rojects to view a list of the projects loaded on each server. When clicked, the name of this button changes to Hide rojects. lick Hide rojects to hide all the projects. Backup erver he Backup ntelligence erver tab allows you to select an optional secondary server to use during failover. f the rimary ntelligence erver becomes unavailable or unusable, the Microtrategy nformation ource attempts to switch to the Backup ntelligence erver. You can specify the following information: Backup ntelligence erver: elect the Backup ntelligence erver check box. Browse a Machine name, and type the ort number for the Backup ntelligence erver. he Backup luster table for specifying the clustering details for the Backup erver is displayed. he table contains the erver name, ort number, and Load Balance Factor of the backup intelligence servers. Refresh: lick Refresh to refresh the list of nodes displayed in the Backup luster table. he default value of the load balancing factor for all the new nodes is set to 1, and the value of the port number is received from the cluster. 174 hapter 15 nformation ource Wizard

195 You cannot make any changes to the erver name and the ort number. You can only specify the Load Balance Factor for each server as follows: Default value = 1 Minimum value = -1 Maximum value = lick how rojects to view a list of the projects loaded on each server. When clicked, the name of this button changes to Hide rojects. lick Hide rojects to hide all the projects. roject dialog box From the drop-down list of available rojects on the selected server, choose the project to use as your information source. lick Advanced roperties to open the Advanced roperties dialog box. R F A Advanced roperties dialog box n the roject page, click Advanced roperties. he Advanced roperties dialog box opens. his dialog box consists of the General tab. General he Authentication Method for Web ubscriptions check box lets you apply user-level authentication for reports and documents. his is used by subscriptions made through Microtrategy Web when Microsoft Windows security is used. When reports and documents are delivered through Microtrategy Web, the method by which Web users are authenticated depends on whether Microtrategy Web is using Microsoft Windows security. f Windows security is not used, users are authenticated using user-level authentication for both reports and documents. f Windows security is used in Microtrategy Web, by default users are authenticated using information source-level authentication for both reports and documents. he check box provided in this dialog box enables user-level authentication for reports and documents even when Windows security is used in Microtrategy Web. For information on Bulk xporting, see the Microtrategy Advanced Reporting Guide. nformation ource Wizard layout 175

196 Default Language R F A his page lets you select a default Language to use by locales for this information source. A drop-down list of languages is provided. his language is used at run time if the information source used by a particular document does not have a language selected in the Locale ditor for that document s locale. t is also used to execute segmentation and subscription information objects. Default Authentication his page lets you specify a default Microtrategy Login D and assword to use as an authentication object for this information source. he authentication object provides the information source with the identity of an end user and determines the access privileges that end user has for the information source. t might limit access to objects such as reports, data, or both. he default authentication object is used to run reports for any subscriber that does not have his own authentication. f you specify a user-level authentication object, it is used at design time. t is also used, if specified, at run time for personalized report execution. However, the default authentication object is used at run time for personalized page execution. he default authentication allows the arrowcast erver to connect to the ntelligence erver and retrieve personalized content for many subscriptions at once by executing a single report. hus, the arrowcast erver does not need to execute a duplicate report for each subscriber with the same personalization, which saves time and system resources. Although both the administrative account and the default authentication object contain a user login and password for the same Microtrategy ntelligence erver, they serve different purposes and do not have the same account for production implementations. he administrative account has administrative privileges, and is used by arrowcast erver to find and create objects. he default authentication object defines the identity (access privileges such as access to reports and data) for users who are not specifically given their own authentication. hus, this account is often a restrictive account to limit the access of generic users. ecurity and Dynamic ubscription upport his page lets you select whether to use a security object and whether this information source must support dynamic subscriptions. 176 hapter 15 nformation ource Wizard

197 A Microtrategy security object is an answer to a specific prompt object. his answer constrains the data that an end user can see and receive, by answering the same prompt object when it appears on a report. f you choose to use a security object, you must elect an attribute-element prompt object. his prompt object is used when the ubscription Administrator defines security objects for end users. lick ext to access the Default ecurity page. f the information source should support dynamic subscriptions, select the his information source supports dynamic subscription check box. lick ext to access the User and ubscription roperties page. f security objects are not used for this information source, click Finish to complete the information source definition and return to the nformation ource dialog box. he chosen prompt object must be part of an information object report for security objects to be applied to that report. Also, a question object that makes use of the chosen prompt object must be applied to each such information object. R F A Default ecurity he Default ecurity page is available only if you chose to use a security object on the ecurity and Dynamic ubscription upport page. his page allows you to define the default security object by answering the security prompt set up in the previous page. lick Define ecurity bject to open the rompt Resolution dialog box. After you select the default security object, you are returned to the Default ecurity page. lick Finish to complete the information source definition and return to the nformation ource dialog box. rompt Resolution dialog box his dialog box opens when you click Define ecurity bject on the Default ecurity page. his dialog box is a browser allowing you to select an attribute element. his attribute element answers the security prompt you set up, and is used as the default if a security object is not selected by the user or ubscription Administrator. lick Finish to return to the Default ecurity page. nformation ource Wizard layout 177

198 User and ubscription roperties R F A he User and ubscription roperties page allows you to select how information for user properties should be retrieved by the information source. You can configure the following properties: ubscription D Address D User D Locale D For each property, you can select various sources for data. he set of available sources for data are the following (one or more of these is available for each property, depending on the applicability): Browse for Attribute Forms Apply a onstant Retrieve from ubscription Book ach source has a check box associated with it. elect the appropriate check box to select the source, then add data to it, if possible. You are not provided with all of these sources for all the properties listed. For example, the ubscription D property has only one source available, Browse for Attribute Forms. Adding data to selected sources For each source, the procedure to add data is different. Best practices Determine the attribute form (D, Last ame, First ame, mail, Display Address, Abbreviation, Long Description, Device, and so on) to be added to the subscription properties. electing the appropriate attribute form ensures that the subscriptions are delivered only to the target subscribers. For example, you may want to deliver a subscription to users with corporate addresses or to those using mobile devices. Browse for Attribute Forms 1. elect the check box associated with Browse for Attribute Forms by clicking it. 2. A Microtrategy attribute browser window opens on the left-hand side. his window allows you to browse the Microtrategy Desktop interface for attributes. 178 hapter 15 nformation ource Wizard

199 3. elect the attribute that you wish to add to the source and doubleclick it to drill down to its attribute forms. 4. elect any attribute form that you want to use, and the Add button (located in the center of the window) is enabled. lick Add to add the selected attribute form to the selected property source. 5. Repeat the procedure to add other attribute forms. Apply a onstant 1. elect the check box associated with Apply a onstant by clicking it. 2. Depending on the type of property selected, a different window opens on the left side. his window allows you to either enter a constant value or choose from a list of options available. erform the desired action, which enables the Add button. lick Add to add your selection to the source. R F A Retrieve from ubscription Book 1. elect the check box associated with Retrieve from ubscription Book by clicking it. 2. o data needs to be added to this source. When selected, this disables any window on the left-hand side. o use the Retrieve From ubscription Book source for any property, the ubscription D used for this information source must match the subscription Ds in the ubscription Book. For more information, see the arrowcast erver Application Designer Guide. Address roperties he Address roperties page allows you to select how information for address properties should be retrieved by the information source. You can configure the following properties: Address Display hysical Address Device ransmission roperties ime Zone Delivery Window nformation ource Wizard layout 179

200 R F A For each property, you can select various sources for data. he set of available sources for data are the following (one or more of these sources are available for each property depending on the applicability): Browse for Attribute Forms Apply a onstant Retrieve from ubscription Book ach source has a check box associated with it. elect the appropriate check box to select the source, then add data to it, if possible. You are not provided with all of these sources for all of the properties listed on this page. Adding data to selected sources For each source, the procedure to add data is different. For information on best practices to be followed while selecting an attribute form, see Best practices. Browse for Attribute Forms 1. elect the check box associated with Browse for Attribute Forms by clicking it. 2. A Microtrategy attribute browser window opens on the left-hand side. his window allows you to browse the Microtrategy Desktop for attributes. 3. elect the attribute that you wish to add to the source and doubleclick it to drill down to its attribute forms. 4. elect any attribute form that you want to use, and the Add button (located in the center of the window) is enabled. lick Add to add the selected attribute form to the selected property source. 5. Repeat the procedure to add other attribute forms. Apply a onstant 1. elect the check box associated with Apply a onstant by clicking it. 2. Depending on the type of property selected, a different window opens on the left side. his window allows you to either enter a constant value or choose from a list of options available. erform the desired action, which enables the Add button. lick Add to add your selection to the source. 180 hapter 15 nformation ource Wizard

201 Retrieve from ubscription Book 1. elect the check box associated with Retrieve from ubscription Book by clicking it. 2. o data needs to be added to this source. When selected, this disables any window on the left-hand side. ersonalization he ersonalization page allows you to select how information for personalization properties should be retrieved by the information source. You can configure the following properties: ecurity his node applies to both security and authentication. You should choose attribute forms for both type of personalization in the same node. reference For each property, you can select various sources for data. he set of available sources for data are the following (one or more of these sources are available for each property depending on the applicability): Browse for Attribute Forms Apply a onstant Retrieve from ubscription Book ach source has a check box associated with it. elect the appropriate check box to select the source, then add data to it, if possible. You are not provided with all of these sources for all of the properties listed on this page. R F A Adding data to selected sources For each source, the procedure to add data is different. For information on best practices to be followed while selecting an attribute form, see Best practices. Browse for Attribute Forms 1. elect the check box associated with Browse for Attribute Forms by clicking it. 2. A Microtrategy attribute browser window opens on the left-hand side. his window allows you to browse the Microtrategy Desktop for attributes. nformation ource Wizard layout 181

202 R F A 3. elect the attribute that you wish to add to the source and doubleclick it to drill down to its attribute forms. 4. elect any attribute form that you want to use, and the Add button (located in the center of the window) is enabled. lick Add to add the selected attribute form to the selected property source. 5. Repeat the procedure to add other attribute forms. Apply a onstant 1. elect the check box associated with Apply a onstant by clicking it. 2. Depending on the type of property selected, a different window opens on the left side. his window allows you to either enter a constant value or choose from a list of options available. erform the desired action, which enables the Add button. lick Add to add your selection to the source. Retrieve from ubscription Book 1. elect the check box associated with Retrieve from ubscription Book by clicking it. 2. o data needs to be added to this source. When selected, this disables any window on the left-hand side. ummary his page displays a summary of information about the information source that you are defining. lick Finish to complete the definition and save the new information source. ave nformation ource dialog box his dialog box allows you to save the new information source. You can change the bject ame, or change the directory to save it in by navigating through the folders in the Look in field. lick ave to save the new object. 182 hapter 15 nformation ource Wizard

203 16 Dialog et HAR nformation ransmission Module he nformation ransmission Module dialog set is a single point of contact for an information transmission module (M). t defines the static characteristics of the M, such as device properties, locale properties, and subscription properties. he M dialog set also lets you specify a set of rules for publications that are sent through the M. For example, you can set a rule to restrict the type of documents that are send through the M. For steps to create an nformation ransmitter, see onfiguring nformation ransmitters. You do not see an interface named nformation ransmission Module dialog set; it is a term for a series of dialog boxes that allow you to perform an action. R F A Accessing the nformation ransmission Module dialog set xpand Administration. Right-click nformation ransmitters, select ew, and then select nformation ransmitter. he Register nformation ransmitter dialog box opens. rerequisite Before using the nformation ransmission Module dialog set, you should understand what an M does and how Ms, information transmitters, and devices work together. For more information about Ms, see nformation transmission modules (Ms) and information transmitters (s). nformation ransmission Module dialog set layout he nformation ransmission Module dialog set contains the following dialog boxes: Register nformation ransmitter dialog box -mail (M) 183

204 R F A Wireless (M) M (M) Web (ortal) lick ancel at any time to exit the dialog set without saving any changes. Register nformation ransmitter dialog box his dialog box lists the information transmission modules available to the arrowcast erver system. elect the Module to add to the system from the drop-down list and click K. he ave As dialog box opens. File and rint information transmitters are automatically configured by arrowcast erver. -mail (M) he nformation ransmitter dialog box for the -mail (M) information transmitter displays one tab, the ender tab. o access additional tabs, select the how Advanced roperties check box. he additional tabs are: Reply-o Message utput Delivery tatus otification Recipient Field ender he Display ame is the name of the sender that is displayed with an e- mail address. he -mail Address is the address of the sender in the jdoe@[domain] format. For example, if the domain is typed as microstrategy.com, the address appears as jdoe@microstrategy.com in the messages generated and sent by arrowcast erver. Reply-o he Display ame is the name of the sender that is displayed with the reply address. he -mail Address is the address used as the reply-to address, in the jdoe@microstrategy.com format. hese fields are optional. 184 hapter 16 nformation ransmission Module Dialog et

205 Message utput he Message utput tab contains the following options to send the arrowcast erver message: end to Recipient via M: ends the message to the recipients through the sender s M server. ave to File: aves the message to a file without sending the message. Do Both (end to Recipient and ave to File): ends the arrowcast erver message to the recipients and also saves the message to a file. You should choose the ave to File or Do Both option only for testing purposes. You must manually delete any files created after using this option. ave to folder: f you choose either the ave to File or Do Both option, the message files generated by arrowcast erver are saved in the specified folder location. You should specify a folder that is valid on each execution engine in your system. R F A Delivery tatus otification Delivery tatus otification (D) is a imple Mail ransfer rotocol (M) service extension. Using the M protocol, you can track whether the is delivered to the recipient or not. he D setting of the recipient mail servers should be enabled to support this notification feature. he options to receive notice of the delivery status are as follows: Do ot Request any otification: Does not send a delivery notification. Request a otification on Failure nly: ends a notification to the specified -mail Address if the message is not delivered to the recipient. Request a otification on Failure and uccess: ends a notification to the specified -mail Address, indicating whether a message was successfully delivered or not. -mail Address: f you choose either the Request a otification on Failure nly or Request a otification on Failure and uccess option, you must enter the address to send the notification. nformation ransmission Module dialog set layout 185

206 R F A ote the following: f the receiving M server completely rejects the message, an delivery notification is not generated. nstead, the execution engine is immediately notified. nly some receiving M servers support delivery notification. ther M servers do not send delivery notification messages, regardless of the Delivery tatus otification setting. Recipient Field he Recipient Field tab contains the following options to display the location of the recipient addresses in messages: Recipient addresses should appear in the o field Recipient addresses should appear in the field Recipient addresses should not appear in the o or fields (use B delivery) Wireless (M) he nformation ransmitter dialog box for the Wireless (M) information transmitter displays one tab, the ender tab. o access additional tabs, select the how Advanced roperties check box. he additional tabs are: Reply-o Message utput Delivery tatus otification Recipient Field ender he Display ame is the name of the sender that is displayed with an e- mail address. he -mail Address is the address of the sender in the jdoe@[domain] format. For example, if the domain is typed as microstrategy.com, the address appears as jdoe@microstrategy.com in the messages generated and sent by arrowcast erver. 186 hapter 16 nformation ransmission Module Dialog et

207 Reply-o he Display ame is the name that is displayed with the reply address. he -mail Address is the address used as the reply-to address, in the format. hese fields are optional. Message utput he Message utput tab contains the following options to send the arrowcast erver message: end to Recipient via M: ends the message to the recipients through the sender s M server. ave to File: aves the message to a file without sending the message. Do Both (end to Recipient and ave to File): ends the arrowcast erver message to the recipients and also saves the message to a file. You should choose the ave to File or Do Both option only for testing purposes. You must manually delete any files created after using this option. ave to folder: f you choose either the ave to File or Do Both option, the message files generated by the arrowcast erver are saved in the specified folder location. You should specify a folder that is valid on each execution engine in your system. R F A Delivery tatus otification Delivery tatus otification (D) is a imple Mail ransfer rotocol (M) service extension. Using the M protocol, you can track whether the is delivered to the recipient or not. he D setting of the recipient mail servers should be enabled to support this notification feature. he options to receive notice of the delivery status are as follows: Do ot Request any otification: Does not send a delivery notification. Request a otification on Failure nly: ends a notification to the specified -mail Address if the message is not delivered to the recipient. nformation ransmission Module dialog set layout 187

208 R F A Request a otification on Failure and uccess: ends a notification to the specified -mail Address, indicating whether a message was successfully delivered or not. -mail Address: f you choose either the Request a otification on Failure nly or Request a otification on Failure and uccess option, you must enter the address to send the notification. ote the following: f the receiving M server completely rejects the message, an delivery notification is not generated. nstead, the execution engine is immediately notified. nly some receiving M servers support delivery notification. ther M servers do not send delivery notification messages, regardless of the Delivery tatus otification setting. Recipient Field he Recipient Field tab contains the following options to display the location of the recipient addresses in messages: Recipient addresses should appear in the o field Recipient addresses should appear in the field Recipient addresses should not appear in the o or fields (use B delivery) M (M) he nformation ransmitter dialog box for the M (M) information transmitter displays fields for hort Message ervice enter (M) onnection and Default Return Address. A est M onnection button is also included in the dialog box to validate your connection settings from the M. M onnection M onnection includes the M Address, M ort, Login ame/d, assword, and ystem ype fields. pecify the information needed for connecting to an M in these fields. nly the assword and ystem ype fields can be left empty. he ystem ype box is optional when connecting to an M as it depends on the M account details. 188 hapter 16 nformation ransmission Module Dialog et

209 he M (M) information transmitter is not functional at run time without a M account. You can contact a M ervice rovider to obtain the M account. Default Return Address Default Return Address contains the Return Address,, and fields. he Return Address field is for the return address (or source address) that is used when sending M messages to an M. he (ype of umber) and (umbering lan ndicator) fields define the and values for the return address and also for all destination addresses to which the M information transmitter sends M messages. Multiple M (M) information transmitters must be made to facilitate sending M messages to destination addresses with different and values. You can also modify the information in the Default Return Address fields (Return Address,, and ) at run time through the use of a control document in the service s publication. You must set the and values properly for each destination address. therwise, the message will not be sent successfully. he M does not send any notification if these values are incorrect when the message is sent to it. R F A est M onnection his button allows you to establish a connection and then disconnect from the M using the parameters specified in M onnection and Default Return Address. Web (ortal) he nformation ransmitter dialog box for the Web (ortal) information transmitter contains the following options: et onnection to urrent BR dit XL et onnection to urrent BR his button allows you to use the current ubscription Book Repository as the document cache repository. his button is enabled if you do not have a connection or if your connection points to someplace other than the current ubscription Book Repository. therwise, the button is disabled. nformation ransmission Module dialog set layout 189

210 dit XL his button allows you to edit the XL that is used to convert attachments to links at the end of the document body. his text is shown in the box below the button. R F A 190 hapter 16 nformation ransmission Module Dialog et

211 17 17.Locale ditor HAR 17 he Locale ditor allows you to specify options that control how data is displayed for users, and how data is gathered, rendered, and transmitted to recipients. Due to the modular architecture of the Delivery ngine, each document formatter, information source, and information transmitter must be set up for the locale. Multiple locales can be used in the same arrowcast erver system. For steps to create a locale, see reating Locales. o understand why different locales must be set up, see Locales and internationalization. R F A Accessing the Locale ditor xpand Administration. Right-click Locales, select ew, and then select Locale. he Locale ditor opens. r, double-click an existing locale. Locale ditor layout he Locale ditor lists the information sources, document formatters, and information transmitters available in the arrowcast erver system on the left. t displays the ame, ype, and configuration tatus of each component. elect a component to view its properties on the right. he properties change depending on which component is selected. For example, the M information transmitter allows you to select the character set to use, while information sources built in the Microtrategy nformation ource Module allow you to set the language.you can edit the properties and save the changes. ote that not all components have configuration options. he menu bar displays standard Windows options, such as, File, View, and Help. he toolbar provides options to open another locale, and save the current locale and exit the editor. 191

212 R F A 192 hapter 17 Locale ditor

213 18 mport Dialog Box HAR pen Device File for he pen Device File for mport dialog box allows you to import devices from an external file. his enables you to update the standard set of devices provided with arrowcast erver. For steps to import devices from a device library, see onfiguring nformation ransmitters. R F A Accessing the pen Device File for mport dialog box pen the Administration folder, then right-click the Devices folder. elect mport Devices. he pen Device File for mport dialog box opens. rerequisite You should understand the concept of a device and know which devices to import. For more information, see Microtrategy arrowcast erver architecture. pen Device File for mport dialog box layout he pen Device File for mport dialog box lists all the device files that are available to import. elect the required file and click K. You are prompted with a set of objects, depending on your object management settings. You can make the appropriate choices from the set of objects and click K. he information transmitters are also imported for these devices if they are not available. As a result, if you have existing information transmitters, you should configure object management to not update, overwrite, or revert existing information transmitters during import. However, you need to configure object management to create, refresh, or update any existing devices and folders. his ensure that any settings in the existing information transmitters are preserved when all new devices, device folders, and the most recent device settings are imported. 193

214 R F A For more information on object management, see Administering multiple systems. For information on object management and conflict resolution interfaces, see onfigure bject Management Dialog Box and onflict Resolution Dialog Box. 194 hapter 18 pen Device File for mport Dialog Box

215 19 Formatter Dialog Box HAR Register Document he Register Document Formatter dialog box allows you to add a new document formatter to the arrowcast erver system. For steps to create a new document formatter, see Working with Document Formatters. R F A Accessing the Register Document Formatter dialog box pen the Administration folder, then right-click the Document Formatters folder. elect ew, then Document Formatter. he Register Document Formatter dialog box opens. rerequisite You should understand how document formatters work with other arrowcast erver components. For more information about document formatters, see Document formatting modules and document formatters. Register Document Formatter dialog box layout his dialog box lists the document formatting modules available to the arrowcast erver system. elect a document formatter from the Module drop-down list and click K. he ave As dialog box opens. his dialog box allows you to save the new document formatter. You can change the bject ame or change the directory to save it in by navigating through the folders in the Look in field. lick ave to save the new object. 195

216 R F A 196 hapter 19 Register Document Formatter Dialog Box

217 20 Box HAR Register nformation ource Module Dialog he Register nformation ource Module dialog box allows you to add a new information source module (M) to the arrowcast erver system. For steps to register an M, see onfiguring nformation ource Modules. R F A Accessing the Register nformation ource Module dialog box pen the Administration folder, then right-click the nformation ource Modules folder. elect ew, then nformation ource Module. he Register nformation ource Module dialog box opens. rerequisite You should understand how information source modules work with other Delivery ngine modules. For more information about information source modules, see nformation source modules and information sources. Register nformation ource Module dialog box layout his dialog box lists the information source modules available to the arrowcast erver system. elect an information source from the Module drop-down list and click K. he ave As dialog box opens. his dialog box allows you to save the new information source. You can change the bject ame or change the directory to save it in by navigating through the folders in the Look in field. lick ave to save the new object. 197

218 R F A 198 hapter 20 Register nformation ource Module Dialog Box

219 21 Box HAR Register ubscription Book Module Dialog he Register ubscription Book Module dialog box adds a new ubscription Book Module (BM) to the arrowcast erver system. For steps to add a new BM, see Register a new ubscription Book Module. R F A Accessing the Register ubscription Book Module dialog box xpand Administration, then right-click the ubscription Book Module folder. elect ew, then ubscription Book Module. he Register ubscription Book Module dialog box opens. rerequisites You should understand the role of the BM in the arrowcast erver system. For more information about BM, see ubscription Book. Register ubscription Book Module dialog box layout his dialog box lists the subscription book modules available to the arrowcast erver system. elect the Module from the drop-down list and click K. he ave As dialog box opens. his dialog box allows you to save the new document formatter. You can change the bject ame, or change the directory to save it in by navigating through the folders in the Look in field. lick ave to save the new object. Your subscription book is displayed in the ubscription Book Module folder. 199

220 R F A 200 hapter 21 Register ubscription Book Module Dialog Box

221 22 Dialog Box HAR Repository opy he Repository opy dialog box allows you to copy repositories from the source directory to the target directory. You can use the options available in the Repository opy dialog box to copy only the bject Repository or the ubscription Book Repository or both. For more information, see opying Repositories. For steps to copy repositories, see onfiguring a arrowcast erver ystem. R F A Accessing the Repository opy dialog box n arrowcast Administrator, from the ools menu, select opy Repository. he Repository opy dialog box opens. Repository opy dialog box layout he Repository opy dialog box includes the following: opy bject Repository: Allows you to copy the bject Repository from the source directory. f you select this option, the following check boxes are available: opy ubscription Book Repository used by the source: Allows you to copy the ubscription Book Repository used by the source. Link the target ubscription Book Repository to the target bject Repository: Maintains a link between the target ubscription Book Repository and the target bject Repository. opy ubscription Book Repository: Allows you to copy only the ubscription Book Repository (users and addresses only) without maintaining a link with the original bject Repository. 201

222 bject Repository page R F A n the Repository opy - bject Repository page, specify the following information for the source and target directories of the bject Repository: Data ource ame Database ype Login assword Database refix ystem ame You can leave the information in the refix blank if there is no prefix assigned to the bject Repository. ubscription Book Repository page n the Repository opy - ubscription Book Repository page, specify the following information for the source and target directories of the ubscription Book Repository: Data ource ame Database ype Login assword Database refix You can leave the information in the refix blank if there is no prefix assigned to the ubscription Book Repository. his dialog box also provides the following copy options which allow users and addresses to be copied by default: User preferences Authentication and security ubscriptions 202 hapter 22 Repository opy Dialog Box

223 ummary page he Repository opy - ummary page allows you to review the information that you have specified for the bject Repository and the ubscription Book Repository. t also displays the path of the log file that is created during the copying process. After you review the information in the ummary page, click Finish to proceed with copying the repositories. A folder showing the objects being copied is displayed. he next screen displays the high level steps you must complete to have the copied system working, and provides a link to the Help page. he information regarding objects copied from source to target and the time taken for the copying process is logged can be viewed in the log file. R F A ummary page 203

224 R F A 204 hapter 22 Repository opy Dialog Box

225 23 Viewer Dialog Box HAR ystem Message he ystem Message Viewer dialog box is a display window for observing and analyzing error messages, execution events, and other system messages generated by Microtrategy arrowcast erver. he ystem Message Viewer allows you to: dit and save the logging information, and control what type of information is shown View error messages generated during service executions, along with the time stamp expressed in U or as specified by the user on the xecution tab in ystem ettings ave the entire list of messages in the monitor earch for a particular error string in the logging information View log, trace and debug messages generated during service executions et logging levels for system messages and logging format for each message pecify how many lines of message text are stored in memory lear the message display opy recent messages to the clipboard, so that they can be pasted into another application For steps to set the logging format for system messages, see elect the logging format for system messages. R F A Accessing the ystem Message Viewer dialog box n arrowcast Administrator, from the ools menu, select View ystem Messages. he ystem Message Viewer dialog box opens. 205

226 rerequisites R F A he ystem Message Viewer depends on the Microtrategy Logging erver for proper operation. f the Microtrategy Logging erver is not configured properly, or you have not connected to a system from this installation of arrowcast Administrator, you cannot view messages in the ystem Message Viewer. For more information, see the arrowcast erver nstallation and onfiguration Guide. ystem Message Viewer dialog box layout he ystem Message Viewer dialog box includes a menu bar, toolbar, and an area for displaying messages. he File menu includes the ave Log option that allows you to save all the messages in the system monitor. electing the ave Log option opens the ave As dialog box that contains the standard Windows file options. You can save the messages in a text file, and specify a file name and location. he dit menu includes the following options: opy: opies the selected text to the clipboard. lear display: lears the display area of the ystem Message Viewer. Find: Allows you to search for a string in the message. You can also perform a repeat search of the string, make the search case-sensitive, and search in the upward or downward direction. he ptions menu includes the following options: et Message ypes: pens the elect Message ypes dialog box, in which you can specify the types and levels of system messages you want to view. lick Advanced to view the complete set of message types. et Governing ettings: pens the Log governing dialog box, in which you can specify the maximum number of messages to store in memory for display, the maximum number and size of log files, and the maximum number of days for retaining the log files. Logging Format: pens the Log Formats dialog box that allows you to set the date and time formats of the log messages. Filter ditor: pens the Log filtering dialog box that allows you to view messages based on the filtering criteria of the time and services that you select. 206 hapter 23 ystem Message Viewer Dialog Box

227 he toolbar includes the following buttons: opy lear display et Message ypes et Governing ettings Autocroll oggle Filter ditor Help elect Message ypes dialog box R F A n the elect Message ypes dialog box, you can specify the types and levels of system messages you want to view, by setting the desired logging levels. electing the box for a given message type causes new messages of that type to be shown in the ystem Message Viewer display. Message types include the following: rror Messages ystem Wide Failure: ndicates a system-wide inability to operate. ervice or Machine Failure: ndicates the failure of a service or a machine, but does not typically indicate a system failure. Recipient Group Failure: ndicates the failure of a segment or the transmission to a specific group of recipients, but does not typically indicate a system, service, or machine failure. Recipient Level Failure or emporary Failure: ndicates a temporary failure or a recipient-level permanent failure such as an invalid address. nformation Messages ervice xecution nformation: rovides service execution process-related information such as service execution start, loading of service definition, start of segmentation, service execution completion, and so on. egment xecution nformation: rovides segment execution process-related information such as segment assignment to an xecution ngine, recipient resolution, segment failover, segment completion, and so on. ystem Message Viewer dialog box layout 207

228 R F A ystem nformation: rovides general system-wide information such as system startup, system shutdown, distribution manager startup, execution engine failure, system component status, and so on. omponent Level nformation: rovides component-level information such as component creation and termination and process steps at a functional level. his information is available for the following modules: nformation ource Modules nformation ransmission Modules Document Formatting Modules ubscription Book Module egment xecutor xecution ngine xecution Recorder ther omponents omponent Level Debugging: rovides low-level component information such as the entry and exit of specific functions, and operations within functions. his information is available for the following modules: nformation ource Modules nformation ransmission Modules Document Formatting Modules ubscription Book Module egment xecutor xecution ngine xecution Recorder Distribution Manager cheduler ther omponents ther Debugging Messages Recipient Level: rovides recipient-level debugging information such as publication selection, information object execution, document formatting, transmission completion, and so on. QL Messages: rovides QL messages for debugging database problems. 208 hapter 23 ystem Message Viewer Dialog Box

229 ustomer pecific atch: his level is reserved for use by customer-specific certified patches and is only used to help troubleshoot problems in these releases. For messages to be displayed in this dialog box, the log levels must be specified on all client machines.nly messages logged by the clients are displayed in this dialog box. hanging these settings does not cause the previously generated messages that were not visible to become visible. Log governing dialog box he Log governing dialog box allows you to configure the settings that control the management of log files and the number of messages displayed in the Message Viewer. tart a new log file every day: reates a new log file everyday irrespective of whether the size limit is reached or not. Maximum number of messages in ystem Message Viewer: Allows you to specify the maximum number of messages that the ystem Message Viewer stores in memory. he default value of this setting is You can specify a minimum value of 100 and a maximum value of f the number of messages that are stored in the ystem Message Viewer reaches the specified maximum limit, the oldest messages are removed from the Viewer's memory. Maximum size of log files (in KB): Allows you to specify the maximum size of log files that can be stored in the computer s hard disk. he default value of this setting is 200 KB. he file size should be a minimum of 100 KB and can extend up to KB. A new file is created when the log file size reaches the specified maximum limit. Maximum number of days for retaining log files: Allows you to specify the maximum number of days for which the log files are retained in the computer s hard disk. he default value of this setting is 7 days. he minimum value that you can specify is 1 day, and the maximum value that you can specify is 99 days. When the number of days for retaining the log files exceeds the maximum number of days specified, the logs for the oldest day are removed. For example, if the value of this setting is 7 days, then on the eighth day, the files that were logged on the first day are removed. R F A ystem Message Viewer dialog box layout 209

230 R F A Maximum number of log files: Allows you to specify the maximum number of log files that can be stored in the computer s hard disk. he default value of this setting is 10. You can specify a minimum value of 1 and a maximum value of When the number of log files exceeds the maximum number specified, the oldest log file is removed. Location of log files: allows you to browse and select the location to store the log files. he Maximum number of days for retaining log files and Maximum number of log files options are mutually exclusive. Log formats dialog box n the Log formats dialog box, you can specify the time zone, time formatting and date formatting for the messages. Date format string: Allows you to enter the date format and try the example of the date format for the message string. ime format string: Allows you to enter the time format and try the example of the time format for the message string. reate tab delimited logging: ets the logging display format of the logs. electing this check box causes different log items on each line to be tab delimited and are easily understood by log viewers. f this check box is not selected, the default logging format is retained. Log filtering dialog box n the Log filtering dialog box, you can view the messages added to the monitor after opening the system monitor, based on the time and service filtering criteria. he ime Filter allows you enter the date and time in the format that you specified in the Log Formats dialog box. electing the Display only messages selected from check box displays messages that fall between two specified dates and time. he ervices Filter allows you to select a service name from the list of services. You can select all the services by selecting the elect All ervices check box. 210 hapter 23 ystem Message Viewer Dialog Box

231 24 Dialog Box HAR ystem ettings he ystem ettings dialog box allows you to control global distribution manager settings, segmentation, and transmission recording. Use this dialog box to set execution limits to govern memory and U consumption. You can also change the display locale and specify document creation properties. For steps to apply governing settings, see Apply system governing settings. R F A Accessing the ystem ettings dialog box n arrowcast Administrator, from the ystem menu, select the system you want to change, then select et Governing ettings. he ystem ettings dialog box opens. rerequisite You should understand the concept about startup settings, execution settings, locales, and transmission recording. For more information, see Microtrategy arrowcast erver architecture and Administering ystems. ystem ettings dialog box layout he ystem ettings dialog box contains the following tabs: Distribution Manager tab xecution tab onsole tab Recording tab Document reation tab 211

232 Distribution Manager tab R F A n the Distribution Manager tab, you can change the following startup settings: tatus communication port number: he port used to communicate with other Delivery ngine machines on the network. umber of startup negotiation attempts: he number of times the distribution manager (DM) tries to locate other DMs to establish the primary DM during startup. imeout for negotiation ping: he amount of time that the DM waits for a reply from other DMs before assuming that other DMs are not active. xecution tab n the xecution tab, you can change the following service execution parameters: Maximum segments per execution: Limits the maximum number of segments that the distribution manager allows a service to have. Maximum failover count: ontrols the maximum number of times that the distribution manager causes a segment to be re-executed on a new execution engine. Maximum concurrent executing services: Limits the maximum number of services that can reside in the execution queue at the same time. his setting can be used to ensure that the system is not overloaded by execution requests. Maximum concurrent expansions: Limits the largest number of services that the primary distribution manager tries to segment simultaneously at any one time. egmentation is performed by the ubscription Book Module (BM). As this segment number increases, the number of BM processes running on the distribution manager increases as well. A larger number of services causes more memory to be consumed, and uses more of the available U power in a multi- U environment. egment queue sizes to trigger segmentation: nables you to control the number of services that are segmented so that the memory consumption on the distribution manager is kept as low as possible. he queue also ensures that segment execution for a service is not unnecessarily delayed while waiting for the segmentation to occur. You can set the following values for the segment queue: 212 hapter 24 ystem ettings Dialog Box

233 At least: he At least value puts a lower bound on the size of the segment execution queue. When the number of segments in this queue drops below this value, the highest priority service that has not yet been segmented is segmented, and its segments are inserted into the segment execution queue, even though it might be lower priority than every other executing service. uning the At least value ensures that your system is never waiting for a service to segment when it has a full pipeline. At most: he At most value puts an upper bound on the size of the segment execution queue. ven if a higher priority service enters the service execution queue, it is not segmented until the size of the segment queue drops below the At most value. uning the At most value ensures that your system never consumes more memory than is available to the distribution manager. ime Zone for ystem nformation: nables you to select a time zone from the drop-down list. R F A onsole tab elect the language for displaying the object names and description in arrowcast Administrator from the elect the Display Locale drop-down list. f an object does not have a name in the chosen locale, its name in the system locale is shown. Recording tab n the Recording tab, you can specify whether transmission recording is active or not. hanges to this setting only take effect for service executions that began after the change was made. ervices already executing while transmission recording was off do not start recording when this feature is turned on. Document reation tab n the Document reation tab, you can select from the following options: Always create new arrowcast erver documents: When a new document is created in arrowcast erver and more than one format is available (HML, ext, xcel, mported), you select the format, then the appropriate arrowcast erver document editor opens. f only one format is available, the appropriate document editor opens. ystem ettings dialog box layout 213

234 R F A Always link to documents created in Microtrategy Desktop: When a new document is created in arrowcast erver to link to an existing document in Microtrategy Desktop and more than one Microtrategy information source is available, you select the information source, then the Desktop Document elector dialog box opens. f only one information source is available, the Desktop Document elector dialog box opens. Always prompt: When a new document is created in arrowcast erver, do one of the following: hoose to create a new arrowcast erver document and select the document format. hoose to link to an existing Microtrategy Web or Report ervices document and select the information source. his is selected by default. 214 hapter 24 ystem ettings Dialog Box

235 ystem Administrator How Do...? H W D 215

236 H W D 216 ection ystem Administrator How Do...?

237 25 Accounts HAR Managing Administrator his chapter describes procedures to manage arrowcast Administrator accounts. For more information on arrowcast Administrator accounts, see Administrative accounts. Add a login D to the local administrators group for Windows Workstation he steps in this procedure are performed using Microsoft s Administrative ools. Microsoft s Administrative ools are a third party software, so the steps may be different than described in the procedure. For more information on using Microsoft s Administrative ools, see the latest Microsoft documentation. H W D teps 1. From the tart menu, select rograms, Administrative ools, User Manager for Domains. he User Manager dialog box opens. 2. n the Groups section, double-click Administrators. he Local Group roperties dialog box opens. 3. lick Add. he Add Users and Groups dialog box opens. 4. n the List ames From box, choose the domain for the login D you wish to add. 5. n the ames box, select one or more login Ds you wish to add and click Add. he selected login Ds should appear in the Add ames list of the dialog box. 6. lick K. You are returned to the Local Group roperties dialog box. 7. lick K. You are returned to the User Manager dialog box. 8. n the User menu, choose xit. 217

238 For more information on managing local groups with the User Manager dialog box, press F1 once the dialog box opens. he Microsoft s User Manager Help opens. Add a login D to the local administrators group for Windows 2000 H W D he steps in this procedure are performed using Microsoft s Administrative ools. Microsoft s Administrative ools are a third party software, so the steps may be different than described in the procedure. For more information on using Microsoft s Administrative ools, see the latest Microsoft documentation. teps 1. From the tart menu, select rograms, Administrative ools, omputer Management. he omputer Management dialog box opens. 2. pen the Local Users and Groups folder and select the Groups folder. 3. Double-click Administrators. he Administrators roperties dialog box opens. 4. elect the administrator group to which you are adding a login D and click Add. 5. n the Look in list, select the domain. 6. n the ame list, select a login D and click Add. he login D appears in the bottom pane. 7. lick K. You are returned to the Administrators roperties dialog box. 8. lick K. You are returned to the omputer Management dialog box. 9. lose the omputer Management dialog box. 218 hapter 25 Managing Administrator Accounts

239 ote the following: f you do not initially see Administrative ools, from the tart menu choose ettings, ontrol anel, double-click Administrative ools. Double-click omputer Management. For more information on managing local groups, press F1 once the omputer Management dialog box opens. Add an account teps 1. xpand the Administration folder and right-click the Accounts folder. elect ew Account. he Add arrowcast erver Administrative Accounts dialog box opens. 2. elect one of the following options to add a new account. f f you know the user name to be added, select the nter Windows User ame option, and then type the Domain\User ame in the Windows Users box. o search a user, select the Browse Windows Domain option, then select the domain for the new account from the Windows domain drop-down list, and then select the name of new user from the Users list. arrowcast erver cannot connect to the specified Windows domain or cannot verify the existence of the specified user in a trusted domain, you are asked if you want to create an unverified administrative account. 3. lick Add to move the user to the arrowcast erver Administrative Accounts list. 4. o assign or change the privileges of the user, click Modify rivileges. For instructions on changing the user role, see Assign privileges to an account. 5. lick K to save the new account. he new user account appears in the Accounts folder. H W D Add an account 219

240 Assign privileges to an account teps H W D 1. o assign privileges to an account, perform one of the following: f this is a new account, from the Add arrowcast erver Administrative Accounts dialog box, click Modify rivileges. he Assign Administrative rivileges to Account dialog box opens. f this is an existing account, expand the Administration folder and then expand the Accounts folder. Double-click the account to update. he Assign Administrative rivileges to Account dialog box opens. 2. elect a role from the Available rivileges list, and then click Add. he role you selected appears in the Granted rivileges list on the left. 3. lick K to save the settings and close the dialog box. ote the following: Any account that is granted the ystem Administrator role must have administrator permissions on every computer in the system. therwise, that account cannot correctly modify the system configuration. f you change the role of a user while he is logged on to the system, the changes do not take effect until he logs out and logs on again. Remove an account When teps an account is deleted, all the objects it owns no longer belong to an account. nly users with administrative access can manipulate the objects that belonged to the account. For a service designer account, only an application administrator can manage the objects. For a system administrator or subscription administrator, another user with the same role can control the objects. 1. xpand the Administration folder, then expand the Accounts folder. Right-click the account to be deleted and select Delete. he onfirm bject Delete dialog box opens. 220 hapter 25 Managing Administrator Accounts

241 2. lick Yes to delete the account. Remove privileges from an account teps 1. o remove privileges to an account, perform one of the following: f this is a new account, from the Add arrowcast erver Administrative Accounts dialog box, click Modify rivileges. he Assign Administrative rivileges to Account dialog box opens. f this is an existing account, expand the Administration folder and then expand the Accounts folder. Double-click the account to update. he Assign Administrative rivileges to Account dialog box opens. 2. elect the role in the Granted rivileges list, and then click Remove. he selected role is removed from the Granted rivileges list and appears in the Available rivileges list. 3. lick K to save the settings and close the dialog box. H W D Remove privileges from an account 221

242 H W D 222 hapter 25 Managing Administrator Accounts

243 26 Restoring bjects HAR opying and his chapter describes procedures to copy objects for backup and restore objects from a backup system using arrowcast erver. For information on migrating and restoring systems, see Administering multiple systems. opy objects to another system for backup/restore purposes teps H W D 1. reate a new arrowcast erver system in a database suitable for archiving your system. 2. pen both systems in arrowcast Administrator and move the desired objects to the new backup system. 3. Unregister the backup system from arrowcast Administrator to avoid accidentally modifying any of the objects in it. Restore all objects from a backup system teps 1. pen both systems in arrowcast Administrator. 2. Drag all application objects to move the contents of the Applications folder from the backup system to the desired target system. 3. Drag all system objects to move the contents of the nformation ource Modules, Document Formatters, nformation ransmitters, Devices, and Locales folders from the backup system to the target system. 223

244 4. Disconnect the backup system from arrowcast Administrator to avoid accidentally modifying any of the objects in it. Restore a single object from a backup system teps H W D 1. pen both systems in arrowcast Administrator. 2. Move the required object from the backup system to the target system. f the object already exists in the target system, the onflict Resolution dialog box opens. elect the Accept option for the object and then click K. For more information on the onflict Resolution dialog box, see onflict Resolution Dialog Box. 3. Disconnect the backup system from arrowcast Administrator to avoid accidentally modifying any of the objects in it. Revert the objects in one environment to the older object definitions from another environment teps 1. pen both systems in arrowcast Administrator. 2. onfigure object management settings so that newer objects in the target system will revert to the older object definitions in the source system. 3. Drag all application objects to move the contents of the Applications folder from the source system to the target system. 4. Drag all system objects to move the contents of the nformation ource Modules, Document Formatters, nformation ransmitters, Devices, and Locales folders from the source system to the target system. 5. Disconnect the source system from arrowcast Administrator to avoid accidentally modifying any of the objects in it. 224 hapter 26 opying and Restoring bjects

245 Update the objects in one environment with the new object definitions from another environment teps 1. pen both systems in arrowcast Administrator. 2. onfigure object management settings so that older objects in the target system are updated with newer object definitions from the source system. 3. Move all objects from the source system to the target system. 4. Disconnect the source system from arrowcast Administrator to avoid accidentally modifying any of the objects in it. H W D Update the objects in one environment with the new object definitions from another environment 225

246 H W D 226 hapter 26 opying and Restoring bjects

247 27 Managers HAR Managing Distribution his chapter describes procedures to add, delete, and manage a distribution manager. he distribution manager is a software component that controls system operations. For more information on distribution managers and their functions, see Distribution managers. Add a distribution manager You must have administrative privileges on a computer to add it as a distribution manager. H W D teps 1. Right-click the Distribution Managers folder in the Folder List panel. hoose ew, then select Distribution Manager. 2. ype the name of the computer or click Browse. A Browse for omputer dialog box opens. Locate the computer and click K. 3. lick K to add the new distribution manager. Delete a distribution manager You must stop the Distribution Manager before deleting it. For instructions, see. teps 1. Right-click the distribution manager to be deleted and then select Delete. 2. n the onfirm bject Delete dialog box, click Yes. 227

248 Run a distribution manager teps 1. Double-click the distribution manager to run. he Distribution Manager dialog box opens. 2. elect Run and then click K. top a distribution manager H W D teps 1. Double-click the distribution manager to stop. he Distribution Manager dialog box opens. 2. elect top and then click K. 228 hapter 27 Managing Distribution Managers

249 28 Document Formatters HAR Working with his chapter describes procedures to work with document formatters. A document formatter is an administration object that stores configuration and other information for using a document formatting module. For a detailed explanation on document formatters and their types, see Document formatting modules and document formatters. Delete a document formatter teps H W D 1. Right-click the document formatter to be removed and select Delete from the menu that appears. 2. elect Yes to confirm deletion. f Register a document formatter a document formatter is used by a device, it cannot be removed. teps 1. Right-click the Document Formatters folder, then select ew, then Document Formatter from the menu that appears. he Register Document Formatter dialog box opens. 2. From the Module list box, select a document formatter. lick K. he ave As dialog box opens. 3. nter a ame for the new document formatter and click ave. 229

250 4. You must set the properties before you can use a new xcel DFM. he other document formatters do not have properties that can be manipulated. For instructions on configuring an xcel document formatter, see the et the properties of an xcel document formatter topic. et the properties of an xcel document formatter teps H W D 1. Double-click the xcel document formatter. he Document Formatter - xcel dialog box opens. 2. lick Browse and locate the folder in which you would like execution engines to store temporary files when creating xcel documents. lick K and the path is entered into the Working directory box. 3. elect one of the following rror Handling options: Fail the document, which means that if an error occurs, the xcel document will not be sent. runcate the Document lement, which means that as much of the document element as possible will be sent. his setting is applied only if the document element is a grid. Replace with the following string, which means that, if possible, the text you enter will replace the flawed document. 4. elect one of the following, which applies if the number of cell formats in the document exceeds the maximum possible number of cell formats in xcel: Fail the document, which means that if the maximum is exceeded the document is not sent. gnore the additional cell formats, which means that if the maximum is exceeded the extra cell formats are ignored and the document is sent anyway. 5. lick K to save the changes. 230 hapter 28 Working with Document Formatters

251 29 ngines HAR Managing xecution his chapter describes procedures to add and manage execution engines. An execution engine is a software component that controls service segments processing. For a detailed explanation on execution engines and the functions of a segment executor, see xecution engines. Add an execution engine You must have administrative privileges on a machine to add it as an execution engine. H W D teps 1. Right-click the xecution ngines folder in the Folder List panel. hoose ew, then select xecution ngine. 2. nter the name of the machine or click Browse. A Browse for omputer dialog box opens. Find the machine and click K. 3. hange the Maximum number of simultaneously executing segments, if desired. 4. lick K to add the new execution engine. Delete an execution engine You must stop the execution engine before deleting it. For instructions to stop the execution engine, see top an execution engine. teps 1. xpand the Administration folder, and then expand the xecution ngines folder. Right-click the execution engine to be deleted and then select Delete. 231

252 2. elect Yes to confirm the deletion. dle an execution engine teps 1. xpand the Administration folder, and then expand the xecution ngines folder. Double-click the required execution engine. he xecution ngine dialog box opens. 2. elect dle and then click K. H W D Run an execution engine teps 1. xpand the Administration folder, and then expand the xecution ngines folder. Double-click the required execution engine. he xecution ngine dialog box opens. 2. elect Run and then click K. top an execution engine teps 1. xpand the Administration folder, and then expand the xecution ngines folder. Double-click the required execution engine. he xecution ngine dialog box opens. 2. elect top and then click K. 232 hapter 29 Managing xecution ngines

253 30 ransmitters HAR onfiguring nformation his chapter describes procedures to manage and configure information transmitters such as File, rint, mail (M), M, and Web devices. For more information on information transmitters, see nformation transmission modules (Ms) and information transmitters (s). Allow users to specify file paths where their files should be saved You must register a File nformation ransmission Module before you can create a File device. For information on registering your device, see Register an information transmitter. H W D teps 1. xpand the Administration folder, then right-click the Devices folder. o create a new File device, click ew and then Device. For more information on creating a File device, see reate a File device. o open an existing File device, double-click the device from the Devices folder. 2. n the General properties tab, in the File location box, type a file location or browse to select a file location. You can also click nsert Macro and select hysical Address to insert a macro for the file path. his macro enables users to enter full network paths themselves. 3. lick K to save the device. he ave Device dialog box opens. 4. For a new device, choose the folder in which to save the object. ype a name for the device and click ave. r leave the existing name and folder settings as they are. 233

254 Allow users to specify printer locations where their services should be printed You teps must register a rint nformation ransmission Module before you can create this device. For information on registering your device, see Register an information transmitter. H W D 1. xpand the Administration folder, then right-click the Devices folder. o create a new rint device, click ew and then Device. For more information on creating a rint device, see reate a rint device. o open an existing rint device, double-click the device from the Devices folder. 2. n the General roperties tab, in the rinter Location section, select a printer location from the list or type a new printer location.lick Add rinter to add a new printer to the list of available printers. 3. elect the Allow print locations defined in user addresses to override the above print location check box. 4. lick K to save the device. arrowcast erver validates the printer location automatically. he ave Device dialog box opens. 5. For a new device, choose the folder in which to save the object. nter a name for the device and click ave. r leave the existing name and folder settings as they are. reate a File device You teps must register a File nformation ransmission Module before you can create this device. For information on registering your device, see Register an information transmitter. 1. xpand the Administration folder, then right-click the Devices folder. 234 hapter 30 onfiguring nformation ransmitters

255 2. elect ew and then Device. he elect nformation ransmitter dialog box opens. 3. Double-click File. he Device ditor opens with the ransmission tab displayed. his tab allows you to specify the parameters your device uses when sending information. 4. n the General properties tab, specify the file location for this device: File Location allows you to enter a full or partial path for delivery of files. nsert Macro allows you to see a list of variables that can be used to personalize each transmission. elect the appropriate macro. 5. n the Advanced properties tab in the Advanced File ystem ptions section, specify the following options: reate required folders creates folders if the specified file path is not present. his is selected by default. verwrite files with same name determines whether the information transmitter overwrites existing files with the same name. his is selected by default. Append timestamp to file name adds the date and time of the file creation to the end of the file name. his is selected by default. Append to file (text documents only) determines whether the information transmitter appends the contents of the new file to the existing file each time the service is executed. For example, if you have a service that contains a text document and it has delivery to file with the Append to file check box selected, a text file is created when the service is executed for the first time. After that, whenever the service is executed, the contents of the new document are appended to the existing file. You can select the Append to file check box only if you clear the verwrite files with same name check box.you must also clear the Append timestamp to file name check box, otherwise a new file is created each time the service is executed. umber of retries allows you to specify how many times file transmission will be attempted if a temporary failure occurs. ime between retries (milliseconds) allows you to specify how much time is allowed between a failed delivery attempt and a retry. Delivery timeout (milliseconds) allows you to specify how much time is allowed before the transmission times out. 6. n the Advanced properties tab in the Backup File Location section, specify the following options: H W D reate a File device 235

256 H W D ave messages to backup file location if delivery fails enables you to provide a location for a backup file if delivery to the original file location fails. Backup File Location allows you to enter the path and file name for delivering files if delivery to the original file location fails. 7. omplete the properties for laintext by following the instructions in the et up plain text properties for a device procedure. 8. omplete the properties for xcel by following the instructions in the et up xcel properties for a device procedure. 9. omplete the properties for HML by following the instructions in the et up HML properties for a device procedure. 10. omplete the properties for DF by following the instructions in the et up DF properties for a device procedure. 11. omplete the properties for all the tabs and click K to create the new device. he ave Device dialog box opens. 12. hoose the folder in which to save the object. ype a name for the new device and click ave. reate an -mail (M) or Wireless (M) device You teps must register an M information transmission module and at least one document formatter before you can create this device. For information on registering your device, see Register an information transmitter. 1. xpand the Administration folder, then right-click the Devices folder. 2. elect ew and then Device. he elect nformation ransmitter dialog box opens. 3. Double-click M. he Device ditor opens with the ransmission tab displayed. his tab allows you to specify the parameters your device uses when sending information. 4. n the Message Format tab, select whether to use UUncoded or MM. 236 hapter 30 onfiguring nformation ransmitters

257 5. he MM ptions tab is displayed only if MM is selected on the Message Format tab. omplete the following information: mbed laintext and HML Body ncoding: elect whether to use base64, 7 bit A, or quoted-printable. ext Attachment ncoding: elect whether to use base64 or quoted-printable. Binary Attachment ncoding: elect whether to use base64 or quoted-printable. Use U A for ubject and Attachment ames: elect whether this device supports only U A for the subject and attachment names. Do not put quotes around non U-A display names: his option should only be enabled for Microsoft utlook 98 and Microsoft utlook clients. mbed HML Attachment: elect whether to embed HML attachments into the message body or send them as unrelated attachments. mbed All Attachments: his option is available only if mbed HML Attachment is chosen. elect whether to embed all attachments, if at least one attachment is embedded. All Attachments should be chosen for Microsoft utlook 98 and Microsoft utlook clients. Remove ontent-location Mime Header: elect this check box to prevent broken links to attachments in s forwarded using Microsoft utlook Web Access. his check box is available only for Microtrategy arrowcast erver version and later. 6. n the Delivery ptions tab, enter a mart Host Address, a ort umber for the mart Host, and whether to use mart Host Always. 7. omplete the properties for laintext by following the instructions in the et up plain text properties for a device procedure. 8. omplete the properties for xcel by following the instructions in the et up xcel properties for a device procedure. 9. omplete the properties for HML by following the instructions in the et up HML properties for a device procedure. 10. omplete the properties for DF by following the instructions in the et up DF properties for a device procedure. H W D reate an -mail (M) or Wireless (M) device 237

258 11. omplete the properties for all the tabs and click K to create the new device. he ave Device dialog box opens. 12. hoose the folder in which to save the object. ype a name for the new device and click ave. reate an M (M) device You must register an M information transmitter before you create this device. For information on registering your device, see Register an information transmitter. H W D teps 1. xpand the Administration folder, then right-click the Devices folder. 2. elect ew and then Device. he elect nformation ransmitter dialog box opens. 3. Double-click M ransmitter (M). he Device ditor opens with the ransmission tab displayed. his tab allows you to specify the parameters your device uses when sending information. 4. ype the number of characters to specify the Maximum Message ize. Messages exceeding the maximum message size are truncated. 5. omplete the properties for laintext by following the instructions in the et up plain text properties for a device topic. 6. omplete the properties for all the tabs and click K to create the new device. he ave Device dialog box opens. 7. hoose the folder in which to save the object. ype a name for the new device and click ave. 238 hapter 30 onfiguring nformation ransmitters

259 reate a rint device You teps must register a rint nformation ransmission Module before you can create this device. For information on registering your device, see Register an information transmitter. 1. xpand the Administration folder, then right-click the Devices folder. 2. elect ew and then Device. he elect nformation ransmitter dialog box opens. 3. Double-click rint. he Device ditor opens with the ransmission tab displayed. his tab allows you to specify the parameters your device uses when sending information. 4. n the General roperties tab, specify standard printer settings for printer location and printer properties: n the rinter Location section, enter or select the printer location from the existing list.you can also click Add rinter to add a new printer to the list of available printers.hen select the Allow print locations defined in user addresses to override the above print location check box. n the rinter roperties section, specify default printer properties including the number of copies, scale, print quality, paper source, paper size, and whether printed copies are collated. o use the standard printer defaults, click Load printer defaults. n the HML Documents section, select the appropriate option to specify the orientation of HML documents. n the DF Documents section, specify the following options as appropriate: ostcript Level indicates the version of ostcript to use on this printer, Level 1, 2, or 3. hrink to fit specifies that the content being printed should be resized, if needed, to fit on the paper used by this printer. Reverse pages instructs the printer to print from back to front instead of front to back (default). rint range indicates which pages to print, if multiple pages are in the print request. H W D reate a rint device 239

260 H W D dd or even pages identifies whether you want to print all pages (even AD odd) or just odd or just even pages. 5. n the Advanced roperties tab, specify the following options: pecify whether to print or save documents to a backup location if the primary printer fails. elect the check box, then choose from the following options: rint files to the following backup printer allows you to specify a backup printer location. ave files to the following backup file location allows you to specify a backup file location. pecify the following governing settings: umber of retries indicates how many times the printer attempts to print if the print request fails. ime between retries (seconds) indicates the number of seconds between each retry attempt. Delivery time out (minutes) indicates the number of minutes before the delivery times out. File Location specifies a location where documents are saved temporarily during execution. By default, the run-time path of the application is used. pecify the Application riority options: ther application and interactive users (DF documents are saved to the backup file location, if specified above) allows arrowcast erver to save the DF document to a backup file location while the other applications continue working. f no backup file location is defined, an error is logged. arrowcast erver (this ends other Adobe applications automatically) allows arrowcast erver to end other Adobe applications and print the DF document. 6. omplete the properties for laintext by following the instructions in the et up plain text properties for a device procedure. 7. omplete the properties for HML by following the instructions in the et up HML properties for a device procedure. 8. omplete the properties for DF by following the instructions in the et up DF properties for a device procedure. 9. omplete the properties for all the tabs and click K to create the new device. he ave Device dialog box opens. 240 hapter 30 onfiguring nformation ransmitters

261 10. hoose the folder in which to save the object. ype a name for the new device and click ave. reate a Web (ortal) device You teps must register a ortal information transmitter before you create this device. For information on registering your device, see Register an information transmitter. 1. xpand the Administration folder, then right-click the Devices folder. 2. elect ew and then Device. he elect nformation ransmitter dialog box opens. 3. Double-click ortal M. he Device ditor opens with the ransmission tab displayed. o transmission settings are required for a ortal M device. 4. omplete the properties for laintext by following the instructions in the et up plain text properties for a device procedure. 5. omplete the properties for xcel by following the instructions in the et up xcel properties for a device procedure. 6. omplete the properties for HML by following the instructions in the et up HML properties for a device procedure. 7. omplete the properties for all the tabs and click K to create the new device. he ave Device dialog box opens. 8. hoose the folder in which to save the object. ype a name for the new device and click ave. H W D Delete a device teps 1. Right-click the device to be deleted and then click Delete. 2. n the onfirm bject Delete dialog box, click Yes. reate a Web (ortal) device 241

262 f the selected device is being used by a publication or an address, it cannot be deleted. lick K for a list of objects that depend on this device. Delete an information transmitter his process deletes the information transmitter for a given information transmission module (M). he M remains in the event you want to create the transmitter again. teps H W D 1. Right-click the device to be deleted and then click Delete. 2. n the onfirm bject Delete dialog box, click Yes. f the Delete option is not available on the menu, the selected information transmitter cannot be removed, because a device or publication is defined for it. mport devices from a device library teps 1. xpand the Administration folder. 2. Right-click the Devices folder and click mport Devices. he pen Device File for mport dialog box opens. 3. elect the required device file distinguished with the.dvc extension and click K. 4. Depending on the object management settings, you are prompted with a set of objects. Accept or reject the change details for the objects and click K to import the devices. 242 hapter 30 onfiguring nformation ransmitters

263 Register an information transmitter teps 1. Right-click the nformation ransmitter folder. lick ew and then nformation ransmitter. he Register nformation ransmitter dialog box opens. 2. From the Module drop-down list, select an information transmission module (M). lick K. he ave As dialog box opens. 3. ype a ame for the new information transmitter and click ave. 4. You must set the properties before you can use the new information transmitter. For instructions, see the following topics: et the properties of an -mail (M) information transmitter et the properties of an M (M) information transmitter et the properties of a Web (ortal) information transmitter rint documents on printers within my network H W D teps 1. Register a rint nformation ransmission Module. For more information on registering your device, see Register an information transmitter. 2. xpand the Administration folder, then right-click the Devices folder. o create a new rint device, select ew and then Device. For more information on creating a rint device, see reate a rint device. o open an existing device, double-click a rint device from the Devices folder. 3. n the General roperties tab, in the rinter Location section, enter or select the printer location from the existing list to specify the default printer location. You can also click Add printer to add a new printer to the list of available printers. 4. lick K to save the device. arrowcast erver validates the printer location automatically. he ave Device dialog box opens. Register an information transmitter 243

264 5. For a new device, choose the folder in which to save the object.ype a name for the device and click ave. r leave the existing name and folder settings as they are. et the properties of an -mail (M) information transmitter teps H W D 1. Double-click the -mail (M) information transmitter to be modified. he nformation ransmitter dialog box opens. 2. n the ender tab, enter the name of the sender in the Display ame box. nter the -mail Address of the sender in the format jdoe@microstrategy.com 3. o access more tabs, select how Advanced roperties. 4. n the Reply-o tab, enter the Display ame that is shown on the reply to line of an . ype the corresponding -mail Address in the format jdoe@microstrategy.com 5. n the Message utput tab, the following options allow you to send the message: end to Recipient via M ave to File Do Both, which sends the narrowcast message to the recipients and also sends it to a file. You You should only choose ave to File or Do Both for testing purposes. You must manually delete any files created by this feature. ave to Folder, saves the message files generated by arrowcast erver to the folder you specify here, if you choose either ave to File or Do Both. must specify a folder that is valid on each execution engine in your system. 6. n the Delivery tatus otification tab, you have the following options on how to receive notice of the delivery status: 244 hapter 30 onfiguring nformation ransmitters

265 ote Do ot Request any otification. o delivery notification will be sent. Request a otification on Failure nly. A notification is sent to the -mail Address entered below only if the narrowcast message cannot be sent. Request a otification on Failure and uccess. A notification is sent to the -mail Address entered below, indicating whether a message was successfully delivered. the following: f notification is requested, you must enter the -mail Address to which to send the notification. nly some receiving M servers support delivery notification. thers never send delivery notification messages, regardless of the Delivery tatus otification setting. 7. n the Recipient Field tab, you have the following options for defining the default recipient field: Recipient addresses should appear in the o field. Unless overwritten by the subscription-level properties, the recipients using a device from this transmitter will be shown in the o field. Recipient addresses should appear in the field. Unless overwritten by the subscription-level properties, the recipients using a device from this transmitter will be shown in the field. Recipient address should not appear in the o or fields (use B Delivery). Unless overwritten by the subscription-level properties, the recipients using a device from this transmitter will not be shown in the o or field. hese 8. lick K. settings can be overwritten at the subscription level by editing the subscription properties. H W D et the properties of an -mail (M) information transmitter 245

266 et the properties of an M (M) information transmitter You teps must establish an account with an M ervice rovider prior to configuring a functioning M (M) information transmitter. H W D 1. Double-click the M (M) information transmitter to be modified. he nformation ransmitter dialog box opens. 2. n the hort Message ervice enter onnection section, enter the M account connectivity information in the appropriate boxes corresponding to the M Address, M ort, Login ame/d, assword, ystem ype, and rotocol Version. 3. n the Default Return Address section, enter the corresponding Return Address, umbering lan ndicator (), and ype f umber () values. he and values are used for the destination address and values as well. 4. lick est M onnection to validate your M M settings. You should receive a success message confirming that you were able to connect to and disconnect from the specified M, or an appropriate error message. 5. lick K. et the properties of a Web (ortal) information transmitter teps 1. Double-click the Web (ortal) information transmitter to be modified. he nformation ransmitter dialog box opens. 2. lick et onnection to urrent BR to use the current ubscription Book Repository as the document cache repository. 246 hapter 30 onfiguring nformation ransmitters

267 3. lick dit XL to edit the XL in the text box that will be used to convert attachments to links at the end of the document body. 4. lick K. et up xcel properties for a device teps 1. lick the xcel tab of the Device ditor. 2. elect whether to Use this Document Formatter for the device. f you choose to use it, then select the Formatting Module from the dropdown list. et up HML properties for a device teps H W D 1. lick the HML tab of the Device ditor. 2. elect whether to Use this Document Formatter for the device. f you choose to use it, then select the Formatting Module from the dropdown list. 3. elect whether to upport mages. f images are not supported and an HML document includes images as information object results, the HML document formatting module will generate run-time errors. hese errors are managed by the document error-handling rules. et up DF properties for a device teps 1. lick the DF tab of the Device ditor. 2. elect whether to Use this Document Formatter for the device. f you choose to use it, then select the Formatting Module from the dropdown list. et up xcel properties for a device 247

268 et up plain text properties for a device teps H W D 1. lick the laintext tab of the Device ditor. 2. elect whether to Use this Document Formatter for the device. f you choose to use it, select the Formatting Module from the list. 3. n the Grid Formatting tab, select one of the following options: Do ot ad Grid ells ad for Fixed-Width Font ad for roportional Font 4. f you want to use a character such as a tab between columns, type that character in the eparate olumns with box. 5. he tring ubstitution tab allows you to substitute the characters you enter in the From column with those you enter in the o column. 6. o create a string substitution, complete the following steps: lick the erform tring ubstitution tab. lick Add. lick in the From column and type the characters to be replaced. lick in the o column and type the characters with which to replace them. 7. f ad for roportional Font is selected on the Grid Formatting tab, the roportional Font tab is available.haracter widths defined in this tab determine how padding is calculated in grid cells. For each width value, only one padding character can be chosen. Find the haracter to set the width of. et the Width of the character, in pixels. elect the Double-byte haracter Width. he table defines the widths of characters with codes in the range between 0 and 255; this setting defines the widths of characters with codes above that range. 8. f ad for Fixed-Width Font or ad for roportional Font is selected on the Grid Formatting tab, the ell adding tab is available. elect a padding haracter or characters from the drop-down list. he remaining columns of the grid are filled in automatically. 248 hapter 30 onfiguring nformation ransmitters

269 31 Modules HAR onfiguring nformation ource his chapter describes procedures to manage and configure information source modules (M) and information sources. For more information, see nformation source modules and information sources. reate a Microtrategy nformation ource You must register an information source module before you can create an information source. For more information, see Register an information source module. H W D teps 1. xpand the Administration folder, then expand the nformation ource Modules folder. Right-click a Microtrategy information source module. elect ew, then nformation ource. he nformation ource dialog box opens. 2. ype a ame and a Description for the new information source. 3. elect a refresh option from the following: f ever Refresh: Reuses the existing information source instance. Refresh mmediately: Reloads the information source module immediately. Refresh after every: Reloads the information source module after executing the number of jobs specified. you set the number of jobs to zero in the Refresh after every option, the information source is used by only one segment before it is reloaded. 4. lick Define to access the nformation ource Wizard. he Welcome page opens. 5. Review the steps to create an information source, then click ext. he ntelligence erver page opens. 249

270 H W D 6. nter the ntelligence erver Machine ame or click the browse button to locate the computer. he name of the computer you specify must be running the Microtrategy ntelligence erver. f your system is clustered, and if the ntelligence erver computer and the arrowcast erver computer that contains the M are in different domains, you may encounter connectivity issues. For details to resolve this issue, see the roubleshooting chapter. 7. nter the ort number of the ntelligence erver computer. 8. nter your Login D and assword. his information is validated when the you click ext, and an error message is displayed if arrowcast erver is unable to connect to the ntelligence erver. 9. o set the ntelligence erver clustering details, complete the following steps: lick Advanced roperties. he Microtrategy ntelligence erver roperties dialog box opens. n the xecution and Governing tab, set the following: Adjust the Request imeout (seconds), if necessary. Adjust the Maximum number of reconnection attempts, if necessary. Adjust the Maximum number of executing information objects, if necessary. elect the Generate DF in arrowcast erver machine check box to generate DF files in the arrowcast erver computer. pecify the Maximum memory consumption for DF file generation (kilobytes). elect the Generate xcel in arrowcast erver machine check box to generate xcel files in the arrowcast erver computer. pecify the Maximum memory consumption for xcel file generation (kilobytes). n the rimary erver tab, review the Machine name and ort number of the rimary ntelligence erver and set the Load Balance Factor for the rimary ntelligence erver. n the Backup erver tab, select an optional secondary server to use during failover and set the Load Balance Factor for the Backup ntelligence erver. lick K to return to the ntelligence erver page. 250 hapter 31 onfiguring nformation ource Modules

271 10. lick ext. he roject page opens. 11. From the roject drop-down list of available projects on the selected server, select the roject to use as your information source. 12. lick Advanced roperties. he Advanced dialog box opens. n the General tab, set the following: o apply user-level authentication for reports for Web subscriptions, select the check box. lick K to return to the roject page. 13. lick ext. he Default Language page opens. 14. From the drop-down lists, select the default Language to use when running reports with this information source. lick ext. he Default Authentication page opens. 15. nter the Login D and assword to be used as the default authentication object, which is used to check user access privileges and run reports for this information source. lick ext. he ecurity and Dynamic ubscription upport page opens. 16. o use an optional security object, complete the following steps: elect the check box under ecurity. lick elect to open the ecurity bject Browser dialog box and select the appropriate security prompt. lick K to return to the ecurity and Dynamic ubscription upport page. 17. o configure this information source to support dynamic subscriptions, select the check box under Dynamic ubscription. lick ext. 18. f security was selected in step 16, the Default ecurity page opens. 19. lick Define Default ecurity. he rompt Resolution dialog box opens. 20. elect the attribute element to use as the default security object and click Finish. You are returned to the ecurity and Dynamic ubscription upport page. 21. f you selected dynamic subscription support in step 17, steps apply. For more information on using the pages covered in these steps, see chapter 15, nformation ource Wizard layout. therwise, go to step lick ext. he User and ubscription roperties page opens. H W D reate a Microtrategy nformation ource 251

272 H W D 23. Make the appropriate selections for retrieving user properties and click ext. he Address roperties page opens. For information on best practice to be followed while selecting an attribute form, see Best practices. 24. Make the appropriate selections for retrieving address properties and click ext. he ersonalization page opens. 25. Make the appropriate selections for retrieving personalization properties and click ext. 26. n the ummary page, review the information to ensure that no changes are needed. You can click Back to return to previous pages if necessary. 27. lick Finish. You are returned to the nformation ource dialog box. 28. lick K. he ave dialog box opens with the object name entered previously. You can change the name. lick K. Delete an information source teps 1. Right-click the information source to be deleted and then select Delete. 2. n the onfirm bject Delete dialog box, click Yes. f the selected information source is being used by an object, it cannot be deleted. Delete an information source module teps 1. Right-click the information source module to be deleted and then select Delete. 2. n the onfirm bject Delete dialog box, click Yes. f an information source has been defined for the selected information source module, it cannot be deleted. 252 hapter 31 onfiguring nformation ource Modules

273 Register an information source module teps 1. Right-click the nformation ource Modules folder. elect ew, then nformation ource Module. he Register nformation ource Module dialog box opens. 2. elect an information source module (M) from the Module list box. 3. lick K. he ave As dialog box opens. 4. nter a ame for the new M. 5. lick K to save the new M. H W D Register an information source module 253

274 H W D 254 hapter 31 onfiguring nformation ource Modules

275 32 32.reating Locales HAR 32 reate a locale A locale enables a arrowcast erver system to support a diverse, multinational user population. arrowcast erver includes eleven locales representing different languages and formats, plus the system locale. You can modify these locales and create new ones as needed using arrowcast Administrator. For a detailed explanation on how these locales impact the behavior of a arrowcast system, see Locales and internationalization. teps H W D 1. xpand the Administration folder, then right-click the Locales folder. elect ew then Locale. he Locale ditor opens. 2. lick a property to view its details. 3. ot all objects have properties that must be configured. et the properties for each that does. 4. For the -mail (M) information transmitter, select the haracter et from the drop-down list. 5. For the Web (ortal) information transmitter, select the Locale from the drop-down list. 6. et the required properties and click ave and lose. he ave Locale dialog box opens. 7. ype a ame for the new locale and click ave. ote that for Microsoft xcel documents to display numerals correctly, you need to do the following: Double-click the locale name under the Administration folder. he Locale ditor opens. n the Locale ditor, set the information source to this locale under Locale roperties for the elected omponent. 255

276 Make sure that the Regional ptions on the user s account that runs the xecution ngine () service also has the same locale selected. Make sure that the client computer that receives and views the xcel document has the same locale setting as well. Delete a locale teps H W 1. Right-click the locale to be deleted and then select Delete. 2. n the onfirm bject Delete dialog box, click Yes. D 256 hapter 32 reating Locales

277 33 ystem HAR onfiguring a arrowcast erver his chapter describes procedures to manage and configure a arrowcast erver system. Microtrategy arrowcast erver is an information delivery platform designed for proactive transmission of information in the form of personalized messages. For a detailed explanation of the arrowcast erver system, see About the arrowcast erver system. Apply system governing settings teps H W D 1. From the ystem menu, select your system, then select et Governing ettings. he ystem ettings dialog box opens. 2. n the Distribution Manager tab, you can change the following startup settings: tatus communication port number, which is the port used to communicate with other Delivery ngine computers on the network umber of startup negotiation attempts, which is the number of times during the startup sequence that the distribution manager (DM) tries to locate other DMs to establish the primary DM imeout for negotiation ping, which is the amount of time that the DM waits for a reply from other DMs before failing the message 3. n the xecution tab, you can change these service execution parameters: Maximum segments per execution, which limits the number of segments that the distribution manager allows a service to have Maximum failover count, which controls the number of times that the distribution manager causes a segment to be re-executed on a new execution engine 257

278 H W D Maximum concurrent executing services, which limits the number of services that can reside in the execution queue at the same time; used to ensure that the system is not overloaded by execution requests Maximum concurrent expansions, which is the largest number of services for which the distribution manager performs segmentation at any one time egment queue sizes to trigger segmentation, which controls when services are segmented based upon the current size of the segment queue; can be used to ensure that the system is not overloaded by execution requests ime Zone for ystem nformation, which enables you to select a time zone from the drop-down list 4. n the onsole tab, select the locale to use for display. 5. n the Recording tab, specify whether or not transmission recording is active. 6. n the Document reation tab, specify whether to create new arrowcast erver documents, link to existing Microtrategy Desktop documents, or prompt for either (selected by default). 7. lick K to save the new settings. lear the ystem Message Viewer teps 1. From the ools menu, select View ystem Messages. he ystem Message Viewer dialog box opens. 2. From the dit menu, select lear Display. he messages are cleared from the display. onnect to a system teps 1. From the ystem menu, select onfigure ew ystem. he ystem onfiguration Wizard opens. 258 hapter 33 onfiguring a arrowcast erver ystem

279 2. onfigure the new system according to the instructions in the Microtrategy arrowcast erver nstallation and onfiguration Guide. You might connect to a system to provide a backup system or to develop applications offline. n this case, you do not need to configure any computers to be used in the system. opy system messages to the clipboard teps 1. From the ools menu, select View ystem Messages. he ystem Message Viewer dialog box opens. 2. n the display area, use the scroll bar to locate the messages you want to copy. 3. lick and drag the mouse from one end of the text to the other to highlight the text you want to copy. 4. From the dit menu, select opy to copy the selected text to the clipboard. he text is ready to be pasted into other applications such as otepad. H W D opy object repository You can choose to copy only the bject Repository or the ubscription Book Repository, or both. he following steps describe the procedure to copy only the object repository. teps 1. From the ools menu, select opy Repository. he Repository opy dialog box opens. 2. elect opy bject Repository. 3. lear the opy ubscription Book Repository used by the source and Link the target ubscription Book Repository to the target bject Repository check boxes. 4. lick ext. he Repository opy-bject Repository dialog box opens. opy system messages to the clipboard 259

280 5. Fill in the information for the source and target repositories and click ext. he Repository opy-ummary dialog box opens. his dialog box displays details of the source and target folders for the bject Repository. t also displays information regarding the log file and its location. 6. lick Finish to start copying the bject Repository. opy subscription book repository You can choose to copy only the bject Repository or the ubscription Book Repository, or both. he following steps describe the procedure to copy only the subscription book repository. H W D teps 1. From the ools menu, choose opy Repository. he opy Repository dialog box opens. 2. elect opy ubscription Book Repository and click ext. he Repository opy-ubscription Book Repository dialog box opens. 3. Fill in the information for the source and target repositories. 4. elect the check boxes in the opy ptions section if you want to copy the users, addresses, and subscriptions to the target repository. 5. lick ext. he Repository opy-ummary dialog box opens. his dialog box displays the summary of the information you have specified so far. t also displays information regarding the log file and its location. 6. lick Finish to start copying ubscription Book Repository. opy object repository and subscription book repository You can choose to copy only the bject Repository or the ubscription Book Repository, or both. he following steps describe the procedure to copy the object repository and subscription book repository. teps 1. From the ools menu, choose opy Repository. he Repository opy dialog box opens. 260 hapter 33 onfiguring a arrowcast erver ystem

281 2. elect opy bject Repository. he opy ubscription Book Repository used by the source and Link the target ubscription Book Repository to the target bject Repository check boxes are enabled and selected by default. 3. lick ext. he Repository opy-bject Repository dialog box opens. 4. Fill in the information for the source and target repositories and click ext. he Repository opy-ubscription Book Repository dialog box opens. 5. Fill in the information for the target repository. 6. elect the check boxes in the opy ptions section if you want to copy the users, addresses, and subscriptions to the target repository. 7. lick ext. he Repository opy-ummary dialog box opens. his dialog box displays details of the source and target folders for bject Repository and ubscription Book Repository. t also displays information regarding the log file and its location. 8. lick Finish to start copying the bject Repository and ubscription Book Repository. H W D Destroy a system You must destroy a system when you no longer need the application objects stored in the system, or the system configuration itself. Destroying a system allows you to free the computers used by a system so that they can be used by other systems. his functionality destroys the system s bject Repository, which contains all system information (such as configuration, governing settings, and all applications), and removes system components from all computers being used by the system. teps 1. From the ystem menu, select your system. 2. elect Destroy ystem. 3. lick Yes to confirm. Destroy a system 261

282 Find a string in the system message teps H W D 1. From the ools menu, select View ystem Messages. he ystem Message Viewer dialog box opens. 2. From the dit menu, select Find. he Find dialog box opens. 3. nter the string that you want to find in the Find what text box, and click Find ext to search for the string. 4. lick Find All to locate all references of the string in the ystem Message Viewer. 5. elect the Match case check box to perform a case-sensitive search. 6. elect the Up or Down options to search for the string in the upward or downward direction in the ystem Message Viewer. 7. lick ancel to close the Find dialog box, and return to the ystem Message Viewer. Filter the system messages teps 1. From the ools menu, select View ystem Messages. he ystem Message Viewer dialog box opens. 2. From the ptions menu, select Filter ditor. he Log filtering dialog box opens. 3. o view the messages that fall between two given dates and time, select the Display only messages selected from check box, and enter the date and time in the specified format. 4. o view the messages of selected services, select the service from the ervice Filter section. 5. o view the messages of all the services in the list, select the elect All ervices check box. 6. lick K to close the Log filtering dialog box and return to the ystem Message Viewer. 262 hapter 33 onfiguring a arrowcast erver ystem

283 Migrate an object from one system (repository) to another teps 1. pen arrowcast Administrator and register the two systems. 2. With both systems open in the arrowcast Administrator, go to the source system. 3. lick and drag the object you want to migrate to the target system. electing the target folder is not important since the folder location of the source system is recreated. 4. f the onflict Resolution dialog box opens, make the required selections and click K. When an object is moved from one system to another, the folder location of the source system is recreated. n addition, all dependent objects used by the object are copied. For example, if a service is copied, any documents, schedules, or subscription sets used by the service are also copied. H W D Modify the Microtrategy Logging erver configuration teps 1. From the ystem menu, select the system you wish to modify and then select dit ystem onfiguration. 2. lick lustering at the top of the window to go to the lustering section. he verview section opens. Read the options carefully. 3. lick ext. Depending on the available options and what you wish to do, choose one of the following: o configure the Microtrategy Logging erver for an unclustered system, choose elect and configure a single machine for arrowcast erver. o configure the Microtrategy Logging erver for a clustered system, choose elect and configure multiple machines for a clustered arrowcast erver system. Migrate an object from one system (repository) to another 263

284 4. From the Review Advanced ettings page, click Modify to edit the Microtrategy Logging erver configuration. Modify transmission properties regarding address display teps H W D 1. n the tatic ubscription et ditor, select a subscription from the ubscriptions in the subscription set table, then select dit from the dit menu. he ubscription roperties editor opens. 2. lick the ransmission tab. 3. n the ransmission roperties section, select the appropriate properties. 4. For the transmitter, select o:, :, or B:. here are no subscription-level properties for the M (M) M or the Web (ortal) M. 5. lick K to save your changes and return to the tatic ubscription et ditor. Register a new ubscription Book Module hanging teps the ubscription Book Module on an existing system causes all existing subscription sets to be invalid and all defined end users and addresses to be inaccessible. 1. xpand the Administration folder. 2. Right-click the ubscription Book Module folder, select ew, then ubscription Book Module. he ubscription Book Module dialog box opens. 3. elect a module from the top-down list and click K. he ave As dialog box opens. 264 hapter 33 onfiguring a arrowcast erver ystem

285 4. n the bject ame box, enter a new name for your subscription book and click ave. Your subscription book appears in the ubscription Book Module folder. Remove all system components from a computer Use this procedure when you want to switch a computer from one system to another system without destroying the first system. teps 1. n the arrowcast Administrator, stop the system if it is running. 2. From the ystem menu, select your system, then select dit ystem onfiguration. 3. lick lustering in the section header. he verview page opens. Read the instructions carefully and then click ext. 4. elect Remove all machines from the arrowcast erver ystem and then click ext. 5. From the ummary page, verify the removal of the system components and close the ystem onfiguration Wizard. H W D Resolve conflicts related to object management he teps onflict Resolution dialog box only opens when you copy one or more objects from one system repository (the source) to another system repository (the target), and there is a conflict. onflicts can occur when an object in the target repository has the same name as the object being copied from the source repository, or when the object in the target repository is newer than the object being copied from the source repository. For more information, see the following topics: Administering multiple systems onflict Resolution dialog box layout onflict Resolution Dialog Box 1. n the onflict Resolution dialog box, make the required selection for each conflict listed. For each conflict, note the information in each column: Remove all system components from a computer 265

286 H W D olumn 1, Action, lists the available types of operation: reate, Refresh, Update, verwrite, and Revert. olumn 2, ype, lists the type of object affected by the conflict (in the target system). olumn 3, ame, lists the name of the object affected by the conflict (in the target system). olumn 4, hange Details, provides the details on the potential change to the target system due to copying an object or objects. olumns 5 and 6, Accept and Reject, allow you to choose either to accept or reject the change indicated in olumn lick in either the Accept or Reject column for each conflict, or click the column header to select the same action for all the conflicts. 3. lick K to resolve the conflict and complete the object migration. ave the system messages teps 1. From the ools menu, select View ystem Messages. he ystem Message Viewer dialog box opens. 2. From the File menu, select ave Log. he ave As dialog box opens in which you can specify the file name, and the location in which you want to save the log file as a text file. ecure the bject Repository arrowcast erver supports multiple database logins to bject Repositories. With this feature, you can grant some users select, insert, update, and delete permissions to your repository tables so that they can read, modify, and delete objects while you prevent those users from accidentally dropping your repository tables.he ystem onfiguration Wizard can be used to secure your object repository in this manner. teps 1. reate your bject Repository with the ystem onfiguration Wizard, using an administrative database login. 266 hapter 33 onfiguring a arrowcast erver ystem

287 2. Have all arrowcast Administrator users (including yourself) use a different database login and password to register the system. Because arrowcast Administrator users do not connect to the database as the owner of the bject Repository tables, they cannot drop these tables. ecure the ubscription Book Repository arrowcast erver supports multiple database logins to ubscription Book Repositories. With this feature, you can grant some users select, insert, update, and delete permissions to your repository tables so that they can read, modify, and delete objects while you prevent those users from accidentally dropping your repository tables. he ystem onfiguration Wizard can be used to secure your ubscription Book Repository in this manner. teps 1. While creating a new system with the ystem onfiguration Wizard, create your bject Repository using an administrative database login. 2. When you complete creating your system, expand the Administration folder and then double-click ubscription Book Module. he ystem onfiguration Wizard opens. 3. Reconnect to the ubscription Book Repository that you created using a different database login and password. Because arrowcast Administrator users do not connect to the database as the owner of the ubscription Book Repository tables, they cannot drop these tables. H W D elect the logging format for system messages teps 1. From the ools menu, select View ystem Messages. he ystem Message Viewer dialog box opens. 2. From the ptions menu, select Logging Format. he Log Formats dialog box opens. 3. nter an appropriate date format and time format. ecure the ubscription Book Repository 267

288 4. elect the reate tab delimited log check box if you want different items on each line to be tab delimited. 5. lick K to save your changes and return to the ystem Message Viewer. end notification for file and print delivery teps H W D 1. n the tatic ubscription et ditor, select a subscription in the ubscription et box, then from the dit menu, select dit. 2. lick the otification tab. his tab is available only if you select File or rint as the delivery method in the ervice Wizard, and the User roperties ditor. 3. elect the -mail option to send a notification through after the service is delivered. 4. lick K to save your changes and return to the tatic ubscription et ditor. et the administrative notification teps 1. From the ools menu, select et Administrative otification. he Administrative otification dialog box opens. 2. elect the check box corresponding to the message type for which you want to define the notification settings. he Governing and Filtering button is enabled. 3. lick Governing and Filtering to open the Administrative otification Request dialog box. elect the Governing check box and specify the governing details. elect the Filtering check box and specify the filtering information. o include a set of codes for which you want notification elect nclude only from the drop-down list. 268 hapter 33 onfiguring a arrowcast erver ystem

289 elect a code from the list box on the left and click >> to move it to the list box on the right. o specify a set of codes for which you do not want any notification elect xclude from the drop-down list. elect a code from the list box on the left and click >> to move it to the list box on the right. o add a new code, enter the code and description in the text boxes and click Add ode. o filter only the required codes from the available list of codes, specify the filtering criteria in the text field and click Filter list by. lick K to close the Administrative otification Request dialog box and save your settings. 4. pecify the address to which the notification is to be sent in the mail Address[es] text box. 5. lick dit Device, if you want to specify the device transmission and formatting properties for the -mail (M) information transmitter. 6. lick K to save the administrative notification settings and close the Administrative otification dialog box. H W D et governing for system messages teps 1. From the ools menu, select View ystem Messages. he ystem Message Viewer dialog box opens. 2. From the ptions menu in the ystem Message Viewer, select et Governing ettings. he Log governing dialog box opens. 3. elect the tart a new log file every day check box to create a new log file everyday irrespective of whether size limit is reached or not. 4. pecify the maximum number of messages that you want the ystem Message Viewer to retain in memory. he default value for this settings is pecify the maximum size of log files that can be stored in the memory. he default value of this setting is 5000 KB. A new file is created when the limit that you have specified is reached. et governing for system messages 269

290 6. pecify the maximum number of days for which the log files are retained in the memory. he default value of this setting is 7 days. 7. pecify the maximum number of log files that can be stored in the memory. he default value of this setting is lick the browse button to specify a location of log files. 9. lick K to save your changes and return to the ystem Message Viewer. he more lines you store, the more memory the ystem Message Viewer consumes on your computer. H W D et message types for system messages teps 1. From the ools menu, select View ystem Messages. he ystem Message Viewer dialog box opens. 2. From the ptions menu in the ystem Message Viewer, select et Message ypes. he elect Message ypes dialog box opens. 3. elect the appropriate check boxes to select the message types you want to view. 4. lick Advanced and select the appropriate check boxes to view information, trace and debug messages. 5. lick lose to save your changes and return to the ystem Message Viewer. During service execution, many trace and debug messages can be produced for each recipient. You should not enable these on a production system. pecify document creation options teps 1. From the ystem menu, select the system, then select et Governing ettings. he ystem ettings dialog box opens. 2. elect the Document reation tab. 270 hapter 33 onfiguring a arrowcast erver ystem

291 3. elect one of the following options: Always create new arrowcast erver documents. his only allows system users to create new documents within arrowcast erver. Always link to documents created in Microtrategy Desktop. his only allows users to link to existing Desktop documents. Always prompt. his enables users to choose between creating a new arrowcast erver document or linking to an existing Web or Desktop document. 4. lick K to save your setting and close the dialog box. pecify the rules for object management teps 1. From the ools menu, select onfigure bject Management. he onfigure bject Management dialog box opens. 2. Make the required selection for each type of operation, other than reate, in the first table. 3. Make the required selections to resolve name and folder conflicts in the second table. 4. lick ave & lose to set the rules and return to the arrowcast Administrator. o select a specific action for all types of operations, click the column header. For example, to be prompted for each type of operation during object migration, click rompt During opy. he option is selected for each type of operation. H W D tart the arrowcast erver system teps From the ystem menu, select your system name, then select tart ystem. pecify the rules for object management 271

292 top the arrowcast erver system arrowcast erver system may need to be stopped for one of the following reasons: Updating registry Resolving a database deadlock that occurs during service segmentation erforming scheduled maintenance witching systems teps H W D From the ystem menu, select your system name, then select top ystem. urn transmission recording on teps 1. From the ystem menu, select the system and then select et Governing ettings. he ystem ettings dialog box opens. 2. lick the Recording tab and click tart. 3. lick K to enable transmission recording for all subsequent service executions. urn transmission recording off teps 1. From the ystem menu, select the system and then select et Governing ettings. he ystem ettings dialog box opens. 2. lick the Recording tab and click top. 3. lick K to disable transmission recording for all subsequent service executions. 272 hapter 33 onfiguring a arrowcast erver ystem

293 View system messages teps From the ools menu, select View ystem Messages. he ystem Message Viewer dialog box opens. As new messages are generated, they appear in the display area of this dialog box. H W D View system messages 273

294 H W D 274 hapter 33 onfiguring a arrowcast erver ystem

295 V ystem Administrator Appendixes V A D X 275

296 A D X 276 Appendixes

297 ADX A A.xecutable Files A he following executable files are installed with Microtrategy arrowcast erver: DMRM.exe: ystem component MAsyhr.exe: ystem component MAdnoti.exe: xecutable for Administrative otification MD.exe: xecutable for the xecution ngine service MDM.exe: xecutable for the Distribution Manager service MDhecker.exe: ystem component MFLM.exe: xecutable for File nformation ransmission Module MDFWR.exe: system component MrntR.exe: xecutable for rint nformation ransmission Module MM.exe: Run-time (service execution) executable for the Microtrategy information source module Mys.exe: Run-time (service execution) executable for the ystem information source module Mubs.exe: Run-time (service execution) executable for the ubscription nformation information source module MUsrD.exe: Run-time (service execution) executable for the User nformation information source module MLogon.exe: xecutable for the Microtrategy Logging onsumer service MLogvc.exe: xecutable for both Microtrategy Logging erver and Microtrategy Logging lient services MMemUsg.exe: xecutable for the Microtrategy ystem Monitor service MBMR.exe: Run-time (service execution) executable for the ubscription Book Module A D X 277

298 M.exe: xecutable for the segment executor, part of the execution engine MMv.exe: xecutable for the Microtrategy M ervice Mnfg.exe: ystem component Mracer.exe: ystem component MUpgrad.exe: Upgrade application for Broadcaster 6.x systems MXMLxp.exe: bject Repository export utility MXMLmp.exe: bject Repository import utility MRAD.exe: arrowcast Administrator application erviceloader.exe: system component Userxportool.exe: Utility for exporting Microtrategy ntelligence erver users to a flat file in V format A D X 278 Appendix A xecutable Files

299 ADX B B.Language upport B arrowcast erver allows you to use different character sets when generating messages, but to use a specific character set, the machine where the execution engine is running must support that specific language. When trying to send an M service that uses a locale that is not supported by the execution engine machine, the service fails, and the error description is similar to the following: MRncodabletring::onvertWideharoMultibyte_oharset - rror 87. he code page XX is not present in your system. where the code page number is the Microsoft Windows code page. f you see this error when running a service, install the language support for the language you want to use. he easiest way to add support for a language is to open Microsoft nternet xplorer, and open a Web page that uses the same language that you want. he browser displays the nternet xplorer nstall on Demand dialog box. lick Download to download and install it. nce the language support is installed, try to run the service again. When arrowcast erver generates an message, if a document or message field contains an invalid character for the character set it is trying to use, the service fails. he error description is similar to the following: MRncodabletring::onvertWideharoMultibyte_oharset - he text "<text> can not be converted to Windows code page xx" where <text> is the original text (in Unicode), and code page xx is the code page arrowcast erver is trying to use to encode the text. o fix this error, make sure the code page is the one you really want to use for that particular text, and that there are no invalid characters for that character set in the text. he character sets that support any character are Unicode, UF-7 and UF-8. Make sure your device supports these character sets before using them. A D X 279

300 ode page numbers and their descriptions are listed below. ode age umber Description 874 hai 932 Japanese (Kanji & J) 936 hinese simplified 949 Korean 950 hinese raditional 1250 entral uropean 1252 Western & U-A 1253 Greek 1254 urkish 1255 Hebrew A D X 1256 Arabic 1257 Baltic 1251 yrillic UF UF Appendix B Language upport

301 ADX.arrowcast erver rror odes his appendix lists Microtrategy arrowcast erver error codes and messages, which are written to the Delivery ngine log files. he list of error codes is for the core arrowcast erver components, such as, Distribution Manager, xecution ngine, egment xecutor, nformation ource Module and nformation ransmission Module. t lists all message levels, except for messages logged at the race or Debug levels. Distribution Manager Message rror ode 0x he following table lists the error messages logged by the Distribution Manager. t contains the message code, the message text, the error description, and the message level. Message ext ssue Description Message Level ervice D [D] xecution D [D] egment D [..] ew service execution created. he Distribution Manager has started the execution of a ervice. tat - xecution A D X 0x ervice D [D] xecution D [D] egment D [.] ervice execution finished successfully. he Distribution Manager has successfully completed the execution of a ervice. tat - xecution 0x ervice D [D] xecution D [D] egment D [.] ervice execution canceled. he execution of a ervice has been canceled. his action is usually performed from the arrowcast erver Admin onsole. tat - xecution 0x ervice D [D] xecution D [D] egment D [..] ervice execution finished with error. roblem executing service. Most likely unable to do segmentation. Moderate rror 281

302 Message rror ode Message ext ssue Description Message Level 0x ervice D [D] xecution D [servicexecutiond] egment D [..] ervice definition loaded - [riority: Value], [Recipients per egment: Value], [tart time: imestamp], [xpiration time: imestamp]. he definition of the ervice has been loaded from the bject Repository. tat - xecution 0x ervice D [D] xecution D [D] egment D [.] ervice execution has been paused. Assigned segments have been paused as well. he execution of a ervice has been paused. his action is usually performed from the arrowcast erver Admin onsole. tat - xecution 0x ervice D [D] xecution D [D] egment D [.] ervice execution has been paused. Assigned segments continue to execute. he execution of a ervice has been paused. his action is usually performed from the arrowcast erver Admin onsole. tat - xecution A D X 0x x ervice D [D] xecution D [D] egment D [.] ervice execution has been resumed. ervice D [D] xecution D [D] egment D [.] alling BM to divide service execution into segments. he execution of a ervice has been resumed. his action is usually performed from the arrowcast erver Admin onsole. he ubscription Book Module will create blocks of recipients based on the segment size property of the ervice. tat - xecution tat - xecution 0x ervice D [D] xecution D [D] egment D [.] ervice execution has been divided into id segment(s). he segmentation step has been completed by the ubscription Book Module. tat - xecution 0x00000A28 ervice D [D] xecution D [D] egment D [D] egment assignment update - executed on [Machine name], backed-up by [Machine name], failover count [Value] out of [MaxFailoverountValue], segment timeout at [imestamp]. A segment has been assigned to the specified xecution ngine with the stated parameters. tat - egment 282 Appendix arrowcast erver rror odes

303 Message rror ode Message ext ssue Description Message Level 0x00000A29 ervice D [D] xecution D [D] egment D [D] egment finished successfully. he Distribution Manager has been notified by the xecution ngine about the successful completion of a segment. tat - egment 0x00000A2A ervice D [D] xecution D [D] egment D [D] he segment has failed because the service has timed out or because it has been failedover for the maximum allowed number of times. A segment has failed because the service has timed out or because it's been failed-over for the maximum allowed times. Moderate rror 0x00000A2B ervice D [D] xecution D [D] egment D [D] egment canceled. he Distribution Manager has received the command to cancel a ervice. tat - egment 0x00000A2 ervice D [D] xecution D [D] egment D [D] egment paused. he Distribution Manager has received the command to pause a ervice. tat - egment 0x00000A2D 0x00000A2 0x00000A33 ervice D [D] xecution D [D] egment D [D] egment resumed. roblem starting up the DM [rror : Value]. "Machine name" was just created. he Distribution Manager has received the command to resume a ervice. roblem starting up the Distribution Manager. he Distribution Manager has started a new xecution ngine process on the specified machine. tat - egment ritical rror nfo (DM) A D X 0x00000A34 "Machine name" reported ountvalue executing segments and ountvalue backup segments. egment load information returned by each xecution ngine to the inquiring Distribution Manager. nfo (DM) 0x00000A35 Disconnected from "Machine name". his message is logged when the Distribution Manager is ending communication with an xecution ngine. nfo (DM) Distribution Manager 283

304 Message rror ode Message ext ssue Description Message Level 0x00000A36 uccessfully connected to "Machine name". his message is logged when the Distribution Manager establishes communication with an xecution ngine. nfo (DM) 0x00000A37 Disconnected from "Machine name". he Distribution Manager is no longer connected to the specified xecution ngine. nfo (DM) 0x00000A38 Ding contacted "Machine name" successfully. his message is logged periodically as the Distribution Manger checks the availability of the xecution ngines in the cluster. nfo (DM) A D X 0x00000A39 0x00000A3A 0x00000A3B uccessfully registered the failover recorder with rimary DM "Machine name. Received shutdown request from rimary DM "Machine name. Received failover recorder registration request from Backup DM "Machineame. his message indicates that the backup mechanism for a Distribution Manager has been established. his message indicates that the backup mechanism for a Distribution Manager has been shutdown. his message is logged when the Backup Distribution Manager is establishing the backup mechanism with the rimary Distribution Manager. nfo (DM) nfo (DM) nfo (DM) 0x00000A3 Received failover recorder unregistration request from Backup DM "Machineame. his message is logged when the Backup Distribution Manager is ending the backup mechanism with the rimary Distribution Manager. nfo (DM) 0x00000A3D ountvalue active chedule objects have been loaded from the repository. Logged by the Distribution Manager when initializing its schedule queue. nfo (DM) 284 Appendix arrowcast erver rror odes

305 Message rror ode Message ext ssue Description Message Level 0x00000A3 ountvalue active ervice objects have been loaded from the repository. Logged by the Distribution Manager when initializing its ervice information. nfo (DM) 0x00000A3F DM process has shutdown. Logged as the last statement before the Distribution Manager shuts down. nfo (DM) 0x00000A40 his DM is going to takeover as the new rimary DM. tarting the takeover procedure. Logged when a Backup Distribution Manager detects that the rimary Distribution Manager is no longer available. nfo (DM) 0x00000A41 his DM is running as a rimary DM. Logged by the first Distribution Manager from the cluster to finish its startup protocol. nfo (DM) 0x00000A42 0x00000A43 0x00000A45 he projected rimary DM failed to start, re-electing the rimary DM. his DM is running as a Backup DM. he clock on the Backup DM machine is being synchronized with the rimary DM's clock. Logged by a secondary Distribution Manager when the Distribution Manager that appeared destined to complete its initialization first fails to do so in a timely fashion. Logged by any secondary Distribution Manager. his is required for schedule firing and service timeout purposes in case the Backup Distribution Manager needs to take over. nfo (DM) nfo (DM) nfo (DM) A D X 0x00000A46 chedule firing ignored because the cheduler is set to not running. Logged if the cheduler component is ever turned off within the Distribution Manager. his can only be achieved programmatically as the arrowcast erver Admin onsole does not provide this functionality. nfo (DM) Distribution Manager 285

306 Message rror ode Message ext ssue Description Message Level 0x00000A47 ervice shutdown request received. he ervice hosting the Distribution Manager process has been told to shutdown by the ervice ontrol Manager. nfo (DM) 0x00000A48 DM shutdown request received. he Distribution Manager acknowledges the shutdown request. nfo (DM) 0x00000A49 ystem shutdown request received. he Distribution Manager acknowledges the request to shutdown the entire cluster. nfo (DM) 0x00000A4A Unregistered the failover recorder with rimary DM Machine name. he backup mechanism for the rimary Distribution Manager has stopped. nfo (DM) A D X 0x00000A4B 0x00000A4 ervice D [D] xecution D [D] egment D [D] ("rimary Machine name"->"backup Machine name") s did not report this segment assignment information. he DM's segment info about rimary and Backup will be used for failover. ervice D [D] xecution D [D] egment D [D] he DM's rimary and Backup information for this segment is not consistent with the information reported by the s. he version for rimary and Backup reported by the s will be used for failover. ("rimary Machine name"->"backup Machine name") logged by rimary DM, ("rimary Machine name"->"backup Machine name") reported by s. he xecution ngines did not report this segment assignment information. he Distribution Manager's segment info about rimary xecution ngine and Backup xecution ngine will be used for fail over. he Distribution Manager's rimary xecution ngine and Backup xecution ngine information for this segment is not consistent with the information reported by the xecution ngines. he version for rimary xecution ngine and Backup xecution ngine reported by the s will be used for failover. Minor rror Minor rror 0x00000A4D ervice received an invalid or unknown request. he ervice received an invalid request. Usual requests are sartup or shutdown. Minor rror 286 Appendix arrowcast erver rror odes

307 Message rror ode Message ext ssue Description Message Level 0x00000A4 Unable to obtain status of Machine name when checking the s prior to DM Failover. will be skipped. Unable to obtain the status of an xecution ngine when doing an assessment of the xecution ngines prior to the Distribution Manager Failover. he xecution ngine will be skipped. Moderate rror 0x00000A4F Unable to load object from the object repository [D: D]. Unable to load xecution ngine object from the bject Repository. evere rror 0x00000A50 Unable to load DM object from the object repository [D: D]. Unable to load Distribution Manger object from the bject Repository. ritical rror 0x00000A51 Unable to load chedule object from the object repository [D: D]. Unable to load chedule object from the bject Repository. evere rror 0x00000A52 0x00000A53 0x00000A54 Unable to load ervice object from the object repository [D: D]. More than one ystem objects were found in the repository when loading the system settings. DM initialization failed. rror synchronizing the clock of the backup DM with that of the primary DM, most likely due to the lack of "hange the system time" privilege. Unable to load ervice object from the bject Repository. More than one Broadcast ystem objects were found in the bject Repository when loading the system settings. Unable to set system time, most likely due to the lack of "hange the system time" privilege. evere rror ritical rror Moderate rror A D X 0x00000A55 Received an extra acknowledgement when asking the xecution Recorder to track a service. Received an extra acknowledgement when asking the xecution Recorder to track a service. Minor rror 0x00000A56 he xecution Recorder received a duplicate request to track a ervice execution. he xecution Recorder received a duplicate request to track a ervice execution. Moderate rror Distribution Manager 287

308 Message rror ode Message ext ssue Description Message Level 0x00000A57 Failed to change the ervice to be Automatic startup. Failed to change the ervice to be Automatic startup. evere rror 0x00000A58 Failed to change the ervice to be Manual startup. Failed to change the ervice to be Manual startup. Moderate rror 0x00000A59 Failed to get the address of the local machine. DM intitialization failed. Failed to get the address of the local machine - the address list is empty. ritical rror 0x00000A5B ervice D [D] xecution D [D] egment D [..] More than one BM objects were found in the object repository when initializing the service. ervice initialization will fail. More than one BM objects were found in the bject Repository when initializing the service. evere rror A D X 0x00000A5D 0x00000A5 Failed to get the address of the local machine due to error returned by WAtartup [rror: Value]. DM intitialization failed. Failed to get the address of the local machine due to error returned by ::gethostbyname [rror: Value]. DM intitialization failed. Failed to get the address of the local machine due to an error returned by the call WAtartup. Failed to get the address of the local machine due to an error returned when trying to look up the host name (gethostbyname). ritical rror ritical rror 0x00000A5F Failed to get the address of the local machine due to error returned by ::gethostname [rror: Value]. DM intitialization failed. Failed to get the address of the local machine due to an error obtained when trying to get the host name (gethostname). ritical rror 0x00000A60 Backup DM "Machine name" is trying to register again with primary DM. A Backup Distribution Manager is trying to register again with the rimary Distribution Manager. his should not be a problem. nfo (DM) 288 Appendix arrowcast erver rror odes

309 Message rror ode Message ext ssue Description Message Level 0x00000A61 ervice D [D] xecution D [D] egment D [..] Unable to open ubscription Book [roperty tring: ropertytring]. Unable to open the ubscription Book. he ervice execution will fail. evere rror 0x00000A62 ervice D [D] xecution D [D] egment D [D] nvalid egment D when canceling a segment FL (L). nvalid segment D was passed to one of the following methods: ause, ontinue, ancel, DoFailover, topbackup. Minor rror 0x00000A63 ervice D [D] xecution D [D] egment D ["D"] "Backup Machine name" was supposed to be backing up this segment (according to the information logged by rimary DM), but this does not belong to the list just loaded from the object repository. he information loaded from the bject Repository does not contain an xecution ngine present in the memory structures of the Distribution Manager. Moderate rror 0x00000A64 ervice D [D] xecution D [D] egment D [D] "rimary Machine name" was supposed to be executing this segment (according to the information logged by rimary DM), but this does not belong to the list just loaded from the object repository. he information loaded from the bject Repository does not contain an xecution ngine present in the memory structures of the Distribution Manager. Moderate rror A D X 0x00000A65 ervice D [D] xecution D [D] egment D [..] Unable to load the BM definition from the object repository [D "BMD"]. Unable to load the BM definition from the bject Repository. evere rror 0x00000A66 Unable to connect to object repository (onnection tring "onnection tring Value"). Unable to connect to the bject Repository. ritical rror Distribution Manager 289

310 Message rror ode Message ext ssue Description Message Level 0x00000A67 ervice D [D] xecution D [D] egment D [D] onflicting segment assignment information returned by s. ("rimary Machine name"->"backup Machine name") or ("rimary Machine name"- >"Backup Machine name")? egment D appears to be assigned to two xecution ngines. Moderate rror 0x00000A68 ervice D [D] xecution D [D] egment D [D] egment D appears to be assigned to two s. ("rimary Machine name"->"backup Machine name") or ("rimary Machine name"->"backup Machine name")? egment D appears to be assigned to two xecution ngines. Moderate rror A D X 0x00000A69 0x00000A6A ervice D [D] xecution D [..] egment D [..]. he service execution request has been rejected because the concurrent service executions governor has been reached. his DM has lost its connection to the network. Reconnection will be attempted after Value seconds. he concurrent ervice executions governor has been exceeded. he etwork connection has been lost. Moderate rror evere rror 0x00000A6B ervice D [D] xecution D [D] egment D [..] ervice execution canceled because the number of segments (Value) exceeds the maximum allowed: Max egment Value. he egmentation process resulted in more segments than allowed by the ervice. Moderate rror 0x00000A6 Unable to load the ystem object containing the DM configuration settings from the repository [D: D]. Unable to load the Distribution Manager's configuration settings. ritical rror 290 Appendix arrowcast erver rror odes

311 Message rror ode Message ext ssue Description Message Level 0x00000A6D ervice D [D] xecution D [D] egment D [..] Unable to load the service definition from the object repository. Unable to load the ervice definition from the bject Repository. Moderate rror 0x00000A6 ervice D [D] xecution D [D] egment D [..] Unable to load a ubscription et definition for the ervice from the object repository [ubscription et D: D]. Unable to load a ubscription et Definition for the ervice from the bject Repository. evere rror 0x00000A6F ervice D [D] xecution D [D] egment D [..] Unable to load one of the nformation ource definitions used by the ervice from the object repository [nformation ource D: D]. Unable to load one of the definitions for the ervice from the bject Repository. evere rror 0x00000A70 0x00000A72 ervice D [D] xecution D [D] egment D [..] Unable to load one of the M definitions used by the ervice from the object repository [M D: D]. ervice D [D] xecution D [D] egment D [..] Unable to load one of the M definitions used by the ervice from the object repository [M D: D]. Unable to load one of the M definitions used by the ervice from the bject Repository. Unable to load one of the M definitions used by the ervice from the bject Repository. evere rror evere rror A D X 0x00000A73 ervice D [D] xecution D [D] egment D [..] Unable to load one of the Device definitions used by the ervice from the object repository [Device D: D]. Unable to load one of the Device definitions used by the ervice from the bject Repository. evere rror 0x00000A74 ervice D [D] xecution D [D] egment D [..] Unable to load one of the Locale definitions used by the ervice from the object repository [Locale D: D]. Unable to load one of the Locale definitions used by the ervice from the bject Repository. evere rror Distribution Manager 291

312 Message rror ode Message ext ssue Description Message Level 0x00000A75 ervice D [D] xecution D [D] egment D [..] Unable to load one of the DFM definitions used by the ervice from the object repository [DFM D: D]. Unable to load one of the DFM definitions used by the ervice from the bject Repository. evere rror 0x00000A77 Failed to get the local machine name during DM initialization. Unable to determine the local machine name for this Distribution Manager. ritical rror 0x00000A78 Failed to load all objects from the object repository. Unable to load all the xecution ngine information from the bject Repository. evere rror 0x00000A79 Failed to load all DM objects from the object repository. Unable to load all the Distribution Manager information from the bject Repository. evere rror A D X 0x00000A7A 0x00000A7B 0x00000A7 o DM object is defined in the object repository. he local machine is not defined as a DM in the object repository. Failed to find the ystem object in the object repository. here isn't a Distribution Manager defined in the repository. he local machine is not defined as a Distribution Manager in the bject Repository. Unable to find ystem bject in the bject Repository. ritical rror evere rror ritical rror 0x00000A7D o ystem object is defined in the object repository. here isn't a ystem bject in the bject Repository. ritical rror 0x00000A7F Unable to create thread used by Failover Recorder. Unable to create thread used by Failover Recorder. evere rror 0x00000A80 hutdown signal to ping thread in FailoverRecorder failed. hutdown signal to ping thread in FailoverRecorder failed. Minor rror 0x00000A81 ime conversion call Variantimeoystemime failed in ing method. ime conversion in ing method failed. evere rror 292 Appendix arrowcast erver rror odes

313 Message rror ode Message ext ssue Description Message Level 0x00000A82 he DM has lost its network connection and it will be recycled automatically. he etwork connection has been lost and the Distribution Manager will be recycled automatically. evere rror 0x00000A83 hutdown signal to assignment thread in Master D ontroller failed. hutdown signal to assignment thread in Master D ontroller failed. Minor rror 0x00000A84 hutdown signal to ping thread in Master D ontroller failed. hutdown signal to ping thread in Master D ontroller failed. Minor rror 0x00000A85 Unable to create assignment thread in Master D ontroller. Unable to create assignment thread in Master D ontroller. ritical rror 0x00000A86 Unable to create ing thread in Master D ontroller. Unable to create ing thread in Master D ontroller. ritical rror 0x00000A87 0x00000A88 he inging mechanism has determined that there are no usable s (available, not idled, with segment capacity > 0). he tartup or Failover initialization process has determined that there are no usable s (available, not idled, with segment capacity > 0). All available xecution ngines have been lost. Detected during Doings. All available xecution ngines have been lost. Detected during tartup or Failover. ritical rror ritical rror A D X 0x00000A89 Failed to create egmentavailable vent in Master D ontroller. Failed to create egmentavailable vent in Master D ontroller. ritical rror 0x00000A8A Failed to create D Available vent in Master D ontroller. Failed to create D Available vent in Master D ontroller. ritical rror 0x00000A8B Failed to generate a GUD for the ervice xecution or for one of the egments. he method within the Distribution Manager which generated the unique identifiers has failed. his is likely a symptom of a larger problem at the machine level. evere rror Distribution Manager 293

314 Message rror ode Message ext ssue Description Message Level 0x00000A8 Failed to generate a GUD for the ervice xecution or for one of the egments. tringfromgud2 failed. he method within the Distribution Manager, which generated the unique identifiers has failed. his likely a symptom of a larger problem at the machine level. evere rror 0x00000A8D cheduler failed to load schedule definitions from the object repository. he cheduler failed to load the schedule definitions from the bject Repository. ritical rror 0x00000A8 cheduler failed to load service definitions from the object repository. he cheduler failed to load the service definitions from the bject Repository. ritical rror 0x00000A8F hutdown signal to time keeper thread in Map failed. hutdown signal to time keeper thread in Map failed. Minor rror A D X 0x00000A90 0x00000A91 0x00000A92 Unable to create time monitoring thread in Map. Unable to initialize ervice ontrol Manager, when trying to shutdown DM. ouldn't obtain a handle for the DM service "ervice ame" from the ervice ontrol Manager during shutdown procedure. Unable to create time monitoring thread in Map. Unable to initialize ervice ontrol Manager. Unable to obtain the handle to the Distribution Manager's ervice. evere rror evere rror evere rror 0x00000A93 Unable to reset the onfiguration erver. Unable to Reset the onfiguration erver within the ervice Manager message loop. ritical rror 0x00000A94 Unable to start the onfiguration erver during the attempt to take over as primary DM as part of the failover process. Unable to start the onfiguration erver during an attempt to take over as rimary Distribution Manager as part of the failover process. ritical rror 294 Appendix arrowcast erver rror odes

315 Message rror ode Message ext ssue Description Message Level 0x00000A95 Unable to register the ervice Handler function with the ervice ontrol Manager. Unable to register the ervice Handler function with the ervice ontrol Manager. ritical rror 0x00000A96 ervice D [D] xecution D [D] egment D [..] Unable to cleanup the segment information in the BR. Unable to cleanup the segment information in the BM at the end of the ervice xecution, or while shutting down the system. Moderate rror 0x00000A97 ervice D [D] xecution D [D] egment D [..] Unable to close the ubscription Book. Unable to close the ubscription Book. Might happen when the ervice finishes or right after segmentation. Minor rror 0x00000A98 ervice D [D] xecution D [D] egment D [...] egmentation failed [ubscription et D: D]. Unable to perform segmentation. Moderate rror 0x00000A99 0x00000A9A ervice D [D] xecution D [D] egment D [...] he BM returned 0 segments when asked to segment the subscription set. Marking service execution as successful. ervice D [D] xecution D [D] egment D [...] Unable to create thread to perform segmentation. his is logged when the service fires, but there were no subscriptions for the associated subscription set. Unable to create thread to perform segmentation. tat - xecution Moderate rror A D X 0x00000A9B ervice D [D] xecution D [D] egment D [...] he service definition is invalid - a document element does not contain any information objects. A Document definition is corrupt. Moderate rror 0x00000A9 ervice D [D] xecution D [D] egment D [...] Unable to load the BM definition from the object repository. Unable to load the BM definition from the bject repository. evere rror Distribution Manager 295

316 Message rror ode Message ext ssue Description Message Level 0x00000A9D ime conversion call ystemimeovariantime failed. A time conversion failed. f this happens this could affect when a service times out. evere rror 0x00000AA0 Backup DM "Machine name" has failed. ts failover recorder has been unregistered. Logged when a communication with the Backup Distribution Manager fails. evere rror 0x00000AA1 Unable to connect to "Machine name" while initializing or taking over. Failed to create M bject (::oreatenstancex failed). Unable to connect to an xecution ngine while initializing or during failover. Failed to create xecution ngine M bject. evere rror A D X 0x00000AA2 0x00000AA3 0x00000AA4 Unable to connect to "Machine name" while initializing or taking over. Failed to register allback (DotifyMe.reatenstance failed). Ding call failed to ing "Machine name" [return value: Value]. ervice D [D] xecution D [D] egment D [D] all to instruct backup machine to take over segment failed on "Machine name. Unable to connect to an xecution ngine while initializing or during failover. Failed to register allback. Failed to ing an xecution ngine. he call to instruct the Backup xecution ngine machine to take over a segment execution has failed. evere rror evere rror Moderate rror 0x00000AA5 ervice D [D] xecution D [D] egment D [D] Failed to assign a new backup machine to "Machine name. Failed to assign a new Backup xecution ngine machine to the given xecution ngine. Moderate rror 0x00000AA6 Failed to set the callback from the to the DM for Machine name. Failed to set the callback from the xecution ngine to the Distribution Manager. evere rror 0x00000AA7 ervice D [D] xecution D [D] egment D [D] he command to tell the backup to backup the segment failed on Machine name. he command to tell the Backup xecution ngine to backup the segment failed. Moderate rror 296 Appendix arrowcast erver rror odes

317 Message rror ode Message ext ssue Description Message Level 0x00000AA8 ervice D [D] xecution D [D] egment D [D] he command to assign the segment to an failed on Machine name. he command to assign the segment to an xecution ngine failed. Moderate rror 0x00000AA9 ervice D [D] xecution D [D] egment D [D] he command to cancel a segment currently executing on Machine name failed. he command to cancel a segment currently executing in an xecution ngine failed. Moderate rror 0x00000AAA Unable to connect to Machine name while initializing or during failover take over. Failed to obtain lass D for M omponent (::LDFromrogD failed). Unable to connect to an xecution ngine while initializing or taking over. Failed to obtain lass D for xecution ngine M omponent. evere rror 0x00000AAB 0x00000AA ervice D [D] xecution D [D] egment D [D] he command to resume the execution of a segment currently executing failed on Machine name. ervice D [D] xecution D [D] egment D [D] he command to pause the execution of a segment currently executing failed on Machine name. he command to resume the execution of a segment currently executing in an xecution ngine failed. he command to pause the execution of a segment currently executing in an xecution ngine failed. Moderate rror Moderate rror A D X 0x00000AAD ervice D [D] xecution D [D] egment D [D] he command to stop the backup of a segment failed on Machine name. he command to stop the backup of a segment failed. his command is given when the service execution completes regardless of its result. Moderate rror 0x00000AA rimary Distribution Manager "Machine name" has failed, starting DM failover procedure. he rimary Distribution Manager has gone down. he Backup Distribution Manager will take over. ritical rror Distribution Manager 297

318 Message rror ode Message ext ssue Description Message Level 0x00000AAF Failed to connect to rimary DM "Machine name" (::oreatenstancex failed). he Backup Distribution Manager was unable to establish a connection with the rimary Distribution Manager. evere rror 0x00000AB0 Failed to register the failover recorder with rimary DM "Machine name". onsequently, the Backup DM will be unable to backup the rimary DM. he Backup Distribution Manager was unable to register as backup with the rimary Distribution Manager. evere rror 0x00000A6 Unable to create ing erver in the onfiguration erver. DM initialization failed. Unable to create ing erver in the onfiguration erver. ritical rror 0x00000A7 Unable to connect to repository because there was a problem creating an instance of a Repository A object. Unable to connect to the bject Repository because there was a problem creating an instance of a Repository A object. ritical rror A D X 0x00000A8 0x00000A9 0x00000AA Unable to create the ing lient bject in the onfiguration erver. DM initialization failed. Unable to create Failver Recorder in the onfiguration erver. DM initialization failed. Failed to initialize the Failver Recorder in the onfiguration erver. DM initialization failed. Unable to create the ing lient bject in the onfiguration erver. Unable to create Failover Recorder in the onfiguration erver. Failed to initialize the Failover Recorder in the onfiguration erver. ritical rror ritical rror ritical rror 0x00000AB he backup DM failed to initialize the ing erver used to monitor the primary DM [return value: Value]. he Backup Distribution Manager failed to initialize the ing erver used to monitor the rimary Distribution Manager. evere rror 0x00000A Unable to create Failver erver in Master xecution controller. DM initialization failed. Unable to create Failover erver in Master xecution controller. ritical rror 298 Appendix arrowcast erver rror odes

319 Message rror ode Message ext ssue Description Message Level 0x00000AD Unable to create nformation ource ool in Master xecution controller. DM initialization failed. Unable to create pool in Master xecution controller. ritical rror 0x00000A M nitialization failed in ervice Module. DM initialization failed. M nitialization failed in ervice Module. ritical rror 0x00000AF ervice Module was unable to set security attributes on DM rocess. DM initialization failed. he ervice Module was unable to set security attributes on the Distribution Manager rocess. ritical rror 0x00000AD0 Failed to load information from arrowcast erver's public type library. DM initialization failed. Unable to read Microtrategy's type library. ritical rror 0x00000AD1 0x00000AD2 0x00000AD3 Unable to properly initialize DM as M erver during ervice initialization (ervicemodule::run()). DM initialization failed. all to start the onfiguration erver during the DM ervice initialization. DM initialization failed. ervice D [D] xecution D [D] egment D [...] Unable to log to the failover recorder that the service fired. Unable to complete the Distribution Manager initialization when running as an ervice. all to start the onfiguration erver from the ervice Module failed. Unable to log to the Failover Recorder that service fired. ritical rror ritical rror Moderate rror A D X 0x00000AD4 ervice D [D] xecution D [D] egment D [...] Unable to log to the failover recorder that the service was expanded into segments. Unable to log to the Failover Recorder that service was expanded into segments. Moderate rror 0x00000AD5 ervice D [D] xecution D [D] egment D [D] Unable to log to failover recorder that a segment was assigned. Unable to log to the Failover Recorder that a service segment was assigned. Moderate rror Distribution Manager 299

320 Message rror ode Message ext ssue Description Message Level 0x00000AD6 ervice D [D] xecution D [D] egment D [...] Unable to log to the failover recorder that the service was paused. Unable to log to the Failover Recorder that service was paused. Moderate rror 0x00000AD7 ervice D [D] xecution D [D] egment D [...] he BM object was not found in the object repository. ervice initialization will fail. o BM bject was found in the bject Repository. evere rror 0x00000AD8 ervice D [D] xecution D [D] egment D [...] Unable to get the class D required to instantiate the BM bject. Unable to get class D to instantiate the BM bject required for the service execution. evere rror 0x00000AD9 ervice D [D] xecution D [D] egment D [...] Unable to instantiate the BM bject. Unable to instantiate the BM bject required for the service execution. evere rror A D X 0x00000ADA 0x00000ADB ervice D [D] xecution D [D] egment D [...] he service execution has exceeded the maximum time that it is allowed to run. ervice D [D] xecution D [...] egment D [...]Received request to run service. he ervice has exceeded the maximum time it is allowed to run. he Distribution Manager is acknowledging the command to run a service. he command came most likely from the arrowcast erver Admin onsole or an A call. Moderate rror tat - xecution 0x00000AD Master xecution ontroller is being stopped with btopluster flag set to: Value. ne of the main components in the Distribution Manager is being stopped. nfo (DM) 0x00000ADD ervice D [D] xecution D [D] egment D [D] Failingover to "Machine name" for execution (backed-up by "Machine name"). he Distribution Manager is recording that a segment is being failed over to the Backup xecution ngine. his could be caused by a segment timeout or due to a segment assignment failure. tat - egment 300 Appendix arrowcast erver rror odes

321 Message rror ode Message ext ssue Description Message Level 0x00000AD ervice D [D] xecution D [D] egment D [D] alling "Machine name" to reset the backup to "Machine name. A new Backup xecution ngine has been assigned to the first xecution ngine in this message, and this information is being communicated to the xecution ngine. tat - egment 0x00000ADF ervice D [D] xecution D [D] egment D [D] Assigning to "Machine name" for execution (backedup by "Machine name"). A segment has been assigned to the specified xecution ngine. he xecution ngine is backed up by another xecution ngine. tat - egment 0x00000A0 ervice D [D] xecution D [D] egment D [D] Assigning to "Machine name" for execution (not backed-up). A segment has been assigned to the specified xecution ngine. he xecution ngine is backed up by another xecution ngine. tat - egment 0x00000A1 0x00000A2 ervice D [D] xecution D [D] egment D [D] Failingover to "Machine name" for execution (not backed-up). ervice D [D] xecution D [D] egment D [D] alling "Machine name" to reset the backup to not backed-up. A segment has failed to execute and is now being reassigned to the specified machine, which is backed up by another xecution ngine. An xecution ngine is being notified about the fact that it is no longer backed up by another xecution ngine. tat - egment tat - egment A D X 0x00000A3 ervice D [D] xecution D [D] egment D [D] Assigning to "Machine name" for backup. A segment is being assigned to the specified machine for backup purposes. tat - egment 0x00000A4 ervice D [D] xecution D [D] egment D [D] "Machine name" is not available to call ResetBackupMachine, this segment is no longer backedup. Unable to assign a backup machine for the execution of the specified segment. tat - egment Distribution Manager 301

322 Message rror ode Message ext ssue Description Message Level 0x00000A6 ervice D [D] xecution D [D] egment D [D] egment has timed-out. he specified segment did not complete its execution in the time allowed by the properties of the ervice that it belongs to. tat - egment 0x00000A7 ervice D [D] xecution D [D] egment D [D] tarting segment failover. he Distribution Manager is starting the process of reassigning the segment for re execution. tat - egment 0x00000A8 ervice D [...] xecution D [...] egment D [segmentd] nvalid egment D reported from "Machine name" during segment completion callback. he DM is already done with this segment. An xecution ngine reported back to the Distribution Manager that a given segment was completed. However, at that point the Distribution Manager had already abandoned that segment execution, most likely due to segment timeout or cancellation. Minor rror A D X 0x00000A9 0x00000AA ervice D [D] xecution D [D] egment D [D] "Machine name" rejected the ancelegmentxecution call, probably it's already done with this segment. ervice D [D] xecution D [D] egment D [D] "Machine name" rejected the ontinueegmentxecution call. he Distribution Manager tried to cancel a segment on the specified xecution ngine, which no longer has it among its executing segments. he Distribution Manager tried to resume the execution of a segment on the specified xecution ngine, which no longer has it among its executing segments. Minor rror Moderate rror 0x00000AB ervice D [D] xecution D [D] egment D [D] "Machine name" doesn't have enough information to take over this segment. he specified xecution ngine has been asked to re-execute a segment which it was backing up, but it is unable to obtain all the required information to do so. Moderate rror 302 Appendix arrowcast erver rror odes

323 Message rror ode Message ext ssue Description Message Level 0x00000A ervice D [D] xecution D [D] egment D [D] "Machine name" rejected the auseegmentxecution call, probably it's already done with this segment. he Distribution Manager tried to pause the execution of a segment on the specified xecution ngine, which no longer has it among its executing segments. Moderate rror 0x00000AD ervice D [D] xecution D [D] egment D [D] "Machine name" rejected the ResetBackupMachine call, probably it's already done with this segment. he Distribution Manager tried to change the xecution ngine backing up the specified segment, but the xecution ngine no longer has it among its executing segments. Moderate rror 0x00000AF0 Failovererver::hutdownR ecorder() - telling all backup DMs to shutdown. he primary Distribution Manager is notifying the Backup Distribution Managers to shutdown. nfo (DM) 0x00000AF3 0x00000AF4 ervice D [D] xecution D [D] egment D [D] he segment has been put back into the pending segment queue. ervice D [D] xecution D [D] egment D [D].he failover operation for this segment was aborted because the backup has already gone offline. he Distribution Manager was unable to assign a segment for execution, and therefore the segment has been put back into the pending segment queue. he egment Failover operation was aborted because the Backup xecution ngine for this segment has already gone offline. tat - egment Moderate rror A D X 0x00000AF5 ervice D [D] xecution D [D] egment D [D].his segment has been failed-over for the maximum number of allowed times. his segment has been failed over for the maximum number of times allowed. Moderate rror 0x00000AF6 Unable to locate BM object definition in object repository. his is required because the ransmission Recording tables are in the ubscription book repository. DM initialization failed. Unable to locate the BM definition in the bject Repository. his is required because the ransmission Recording tables are in the BR. ritical rror Distribution Manager 303

324 Message rror ode Message ext ssue Description Message Level 0x00000AF7 More than one ubscription Book Module objects are defined in object repository. DM initialization failed. he Distribution Manager was unable to determine which ubscription Book to use. ritical rror 0x00000AF8 he onfiguration erver failed to initialize the ransmission Recorder. [rror: rror]. DM initialization failed. he onfiguration erver failed to initialize the ransmission Recorder. ritical rror 0x00000AF9 ervice D [D] xecution D [D] egment D [D] "Machine name" returned extra information when ancel was called: [ource: ource] [umber: umber] [Description: "Description"]. he specified xecution ngine returned some error information as a result of processing the call to cancel a segment. tat - egment A D X 0x00000AFA 0x00000AFB ervice D [D] xecution D [D] egment D [D] egment will not be failed-over because the service has timed out. Unable to initialize Admin otification bject. reatenstance call failed for Adminotification.Adminot ifyfactory [return value: Value]. he egment will not be failed over because the service has timed out. he Distribution Manager was unable to create the component responsible for the Administrative otification functionality. his is likely due to a M error caused by improper file registration. Moderate rror Moderate rror 0x00000AF Failed to update administrative notification settings. Administrative notification will continue to operate with its previous values [rror: Value]. he Distribution Manager received a call from the arrowcast erver onsole with new Administrative otification settings, but the call failed and the settings were not updated. Moderate rror 0x00000AFD Admin notification failed to start. DM will continue to execute [rror: Value]. he Administrative otification component failed to complete its startup process. he feature will be disabled. Moderate rror 304 Appendix arrowcast erver rror odes

325 Message rror ode Message ext ssue Description Message Level 0x00000AF Failed to initialize administrative notification object. DM will continue to execute [rror: Value]. he Administrative otification component failed to complete its initialization process. he feature will be disabled. Moderate rror 0x00000AFF ervice D [D] xecution D [D] egment D [D] "Machine name" returned success with information, but no extra information is available. he Distribution Manager tried to cancel a segment, but the call to the xecution ngine did not succeed. Further error information was not available. tat - egment tat - egmentnfo ()0x00000B00 Unable to set the U process affinity for component DM. he license information could not be obtained. DM initialization failed. he Distribution Manager was unable to obtain its license information. ritical rror 0x00000B02 he system will not complete the initialization of the on computer Machineame. Adding this computer to the Microtrategy arrowcast erver cluster will make the cluster use X Us, but the license only allows the cluster to use Y Us. he will be set to idle. o correct this situation, you can remove computers from the cluster or you can decrease the number of Us used by one or several computers. o enable this cluster to use more Us, please contact Microtrategy to upgrade your license. Adding an additional xecution ngine to the cluster would violate the U license. Moderate rror A D X Distribution Manager 305

326 Message rror ode Message ext ssue Description Message Level 0x00000B05 Failed to set schedule status to not-demanded. chedule will execute again at its predefined periodicity [D: D]. he Distribution Manager was unable to set the status of a schedule in the bject Repository to 'not demanded'. his is used for schedules associated with Web deliveries. t is an optimization which allows the schedule to not fire when there are no subscribers to the service. Minor rror 0x00000B10 FAAL RRR: A MRxception occurred in the DM. DM will shutdown [rror: rror]. afety net to catch any unhandled application exceptions. he Distribution Manager will shutdown. ritical rror 0x00000B11 FAAL RRR: An unknown exception occurred in the DM. DM will shutdown. Generic catch all exception handler. he Distribution Manager will shutdown. ritical rror A D X 0x00000B12 0x00000B13 ervice D [D] xecution D [D] egmentd [egmentd] nvalid segment D when calling DoegmentFailover FL (L). ervice D [D] xecution D [D] egment D [egmentd] nvalid segment D when calling auseegment. An nvalid egment D was passed to the specified method. An nvalid egment D was passed to the specified method. Moderate rror Minor rror 0x00000B14 ervice D [D] xecution D [D] egmentd [egmentd] nvalid segment D when calling topegmentbackup FL (L). An nvalid egment D was passed to the specified method. Minor rror 0x00000B15 ervice D [D] xecution D [D] egment D [egmentd] nvalid segment D when calling ontinueegment. An nvalid egment D was passed to the specified method. Minor rror 306 Appendix arrowcast erver rror odes

327 Message rror ode Message ext ssue Description Message Level 0x00000B16 Unable to load ubscription Book Module object containing BM definition [D: D]. his is required to connect to the Database where the BR and ransmission Recording tables reside. Unable to load the BM definition. his is required to connect to BR where ransmission Recording tables reside. ritical rror 0x00000B17 ervice D [D] xecution D [D] egment D [D] his segment has been failedover/re-assigned for the maximum number of allowed times. egment aborted. he egment has been failed over and reassigned for the maximum number of times allowed. he segment execution is being aborted. Moderate rror 0x00000B18 0x00000B19 0x00000B1A ervice D [D] xecution D [D] egment D [D] he backup for this segment has already gone offline as well. Failover aborted. ervice D [D] xecution D [D] egment D [D].he newly assigned backup for this segment just went offline as well. Failover aborted. Failed to spawn thread to load schedules. ::_beginthreadex failed : he Distribution Manager was in the process of reassigning a segment for execution on another xecution ngine, but the new xecution ngine is no longer available. he xecution ngine that was supposed to reexecute the specified segment is no longer available. he segment will not be re-executed. Failed to spawn thread to load schedules. Moderate rror Moderate rror ritical rror A D X 0x00000B1B ervice D [D] xecution D [D] egment D [...] Unable to log to the failover recorder that the service was loaded. Unable to log to Failover Recorder that service was loaded. Moderate rror 0x00000B1 Failed to find the ubscription Book Module object in the object repository. he Distribution Manager failed to initialize because it did not find information about the ubscription Book in the bject Repository. ritical rror Distribution Manager 307

328 Message rror ode Message ext ssue Description Message Level 0x00000B1D ervice D [D] xecution D [D] egment D [..] Failed to create ervice Loader object. he component that loads a ervice from the bject Repository could not be created. he ervice execution will fail. Moderate rror 0x00000B1 ervice D [D] xecution D [D] egment D [..] Failed to initialize ervice Loader object. he component that loads a ervice from the bject Repository could not be initialized he ervice execution will fail. Moderate rror 0x00000B20 Unable to obtain host Address. he Distribution Manager was unable to determine the address of the machine where it is running. his will likely render this Distribution Manager unusable. ritical rror A D X 0x00000B21 0x00000B22 Unable to load chedule object from the object repository [D: D]. Failed to create administrative notification object. DM will continue to execute [rror: Value]. he specified chedule object could not be loaded. he ervices associated with that chedule will not run. he component responsible for the Administrative otification feature could not be created. he feature will be disabled. evere rror Moderate rror 0x00000B23 ervice D [D] xecution D [D] egment D [...] Unable to load the Locale objects from the repository. Unable to determine what Locales are supported by the specified ervice. evere rror 0x00000B24 ervice D [D] xecution D [D] egment D [...] egmentation has been canceled because the re- QL statement returned an empty result [ubscription et D: D]. he reql associated with a ubscription et returned no data, and based on the reql rules, it was determined to stop the ervice execution. his is desired behavior. tat - xecution tat - egment0x etwork status info: tatusnfo. he Distribution Manager has logged its network status information. nfo (DM) 308 Appendix arrowcast erver rror odes

329 Message rror ode Message ext ssue Description Message Level 0x xception caught while checking network connection [rror: rror]. An unknown exception was caught during the network status check. evere rror 0x etwork status info: tatusnfo. he Distribution Manager has logged its network status information. nfo (DM) 0x xception caught while checking network connection [rror: rror]. An unknown exception was caught during the network status check. evere rror 0x etwork status info: tatusnfo. he Distribution Manager has logged its network status information. nfo (DM) 0x xception caught while checking network connection [rror: rror]. An unknown exception was caught during the network status check. evere rror 0x x x ervice D [D] xecution D [D] egment D [D] Failed to resolve recipients due to temporary database error. Will retry later. rocess nfo: rocessontextnformatio n. ervice D [D] xecution D [D] egment D [..]. Resume service execution paused due to temporary BR error. he Distribution Manager was unable to determine the subscribers for a ubscription et. he Distribution Manager has logged its process information. A ervice was resumed but the ubscription Book is unavailable, preventing the completion of the resume operation. evere rror nfo (DM) Moderate rror A D X 0x ervice D [D] xecution D [D] egment D [..]. Failed to load service definition due to temporary database error, will retry later. he Distribution Manager failed to load a ervice from the bject Repository due to DB unavailability. Moderate rror 0x ervice D [D] xecution D [D] egment D [..]. Failed to divide service execution into segments due to temporary database error, will retry later. he egmentation process has failed due to DB unavailability. Moderate rror Distribution Manager 309

330 Message rror ode Message ext ssue Description Message Level 0x DM set to stopped state in ervice ontrol Manager. he Distribution Manager has recorded the change of ervice status to stopped. nfo (DM) 0x ransmission Recording is turned off. he Distribution Manager is recording the status of this feature. nfo (DM) egment xecutor he following table lists the error messages logged by the egment xecutor. t contains the message code, the message text, the error description, and the message level. Message rror ode Message ext ssue Description Message Level A D X 0x x ervice D [D] xecution D [D] egment D [D] rror transmitting to recipient [AddressD] - rror umber:rror Description. ervice D [D] xecution D [D] egment D [D] here was a problem creating the M or DFM modules [rror umber:rror Description]. here was a problem transmitting to the specified recipient. here was a problem creating the M or DFM modules. Without these components, the egment xecutor can not format or deliver messages. Minor rror evere rror evere rrorevere rrormoderate rrortat - egment0x ervice D [D] xecution D [D] egment D [D] here was a problem closing the xecution Recorder when trying to shut down the egment xecutor [rror umber:rror Description]. hutdown will continue. here was a problem closing the component used to backup the execution of a segment. he shutdown process will continue. Minor rror 0x ervice D [D] xecution D [D] egment D [D] here was a problem closing the BM while receiving recipients [rror umber:rror Description]. here was a problem closing the BM component after retrieving the recipient information for this segment. he segment execution will continue. Minor rror 310 Appendix arrowcast erver rror odes

331 Message rror ode Message ext ssue Description Message Level 0x ervice D [D] xecution D [D] egment D [D] - Device DeviceD with Locale LocaleD is supported by multiple publications. he first publication found will be used for this device/locale combination. Warning message stating that a particular device and locale combination is supported by multiple publications. he segment execution will continue. Minor rror 0x ervice D [D] xecution D [D] egment D [D] ould not cancel ransmission Module D [D] while shutting down the FMManager because error [rror umber:rror Description]. here was a problem canceling a transmission or terminating a ransmitter while shutting down the egment xecutor. Minor rror 0x ervice D [D] xecution D [D] egment D [D] ould not close Document Formatter D [D] because rror umber:rror Description. here was a problem terminating a Document Formatter while shutting down the egment xecutor. Minor rror 0x F 0x ervice D [D] xecution D [D] egment D [D] Document Formatter D [D] Document ame [Documentame] FormatDocument failed because error [rror umber: rror Description]. ervice D [D] xecution D [D] egment D [D] nformation ource D [D] ndex [ndex] called Returnegmentnformationb jectresult on the egment xecutor. his is an invalid call and it will be ignored. An error occurred while formatting a Document. f the Document is required for this ublication, then the message will not be transmitted. his would affect all recipients sharing the same personalization/device/loca le values. rror caused by an nformation ource calling an unsupported method on the egment xecutor. his call should only be made back to the BM. Minor rror Moderate rror A D X 0x ervice D [D] xecution D [D] egment D [D] Address [AddressD] will not receive its messages because it does not have a ersonalization set for each nformation ource. he specified recipient will not be processed because his/her number of personalizations does not match the number of nformation ources from which the content needs to be gathered. Minor rror egment xecutor 311

332 Message rror ode Message ext ssue Description Message Level 0x ervice D [D] xecution D [D] egment D [D] egment xecutor could not log recipient array to xecution Recorder [rror umber:rror Description]. will terminate. he egment xecutor could not log the recipient information to the backup infrastructure. Moderate rror 0x ervice D [D] xecution D [D] egment D [D] egment xecutor could not log recipient finished to xecution Recorder [rror umber:rror Description]. he egment xecutor could not log the result of a transmission to the backup infrastructure. Moderate rror 0x A ervice D [D] xecution D [D] egment D [D] Reporting segment execution failure right before shutting down the. he will continue to shutdown [rror umber:rror Description]. A segment failure has been detected as the egment xecutor prepares to shutdown. he egment xecutor will continue to shutdown. Moderate rror A D X 0x B 0x ervice D [D] xecution D [D] egment D [D] Unknown error occurred while trying to flush the transmission recorder [rror: rror umber Desc: rror Description]. ervice D [D] xecution D [D] egment D [D] MRnformationransmitter otify_ransmitallback - Duplicated callback received for address index AddressD. his could be caused by an M error. An unexpected error happened while writing the statistics information to the ransmission Recording database. A transmission callback for a recipient that has already been processed. his will be ignored. Moderate rror Minor rror 0x ervice D [D] xecution D [D] egment D [D] nvalid information callback received for address index Value. his could be caused by an M error. A transmission callback for a recipient that does not exist anymore was received. t means most likely that we already received a previous callback for that recipient and was removed from the array of pending transmissions. his will be ignored. Minor rror 312 Appendix arrowcast erver rror odes

333 Message rror ode Message ext ssue Description Message Level 0x ervice D [D] xecution D [D] egment D [D] ne or more s require reexecution. index: ndex Value. his message is logged when the egment xecutor is exporting data to a file incrementally. his feature is known as Bulk xport. Minor rror 0x ervice D [D] xecution D [D] egment D [D] uccess transmitting to recipient [AddressD] - with the following information : Description. Reporting the successful completion of a transmission for the specified recipient. nfo () 0x ervice D [D] xecution D [D] egment D [D] ould not close ransmission Module D [D] because rror umber:rror Description. he egment xecutor was unable to close the specified ransmitter. his would be logged at the end of the segment execution when the egment xecutor is cleaning up. Minor rror 0x x ervice D [D] xecution D [D] egment D [D] - Userset X has been sent. ervice D [D] xecution D [D] egment D [D] - All Usersets sent. Users sharing the same personalization and preferences are grouped into Userets. he transmission has been completed for the specified Useret. Users sharing the same personalization and preferences are grouped into Userets. he transmission has been completed for all the Userets in the segment. nfo () nfo () A D X 0x ervice D [D] xecution D [D] egment D [D] Recipient [.AddressD] uses a device and locale that is not supported by this service. his recipient will not get any content. he recipient will not receive a message because it uses a device and a locale that are not supported by any of the ublications in the ervice. Moderate rror egment xecutor 313

334 Message rror ode Message ext ssue Description Message Level 0x ervice D [D] xecution D [D] egment D [D] - ublication [D] supports device [D] which is used by recipient [AddressD]. However, the ublication and the Device support conflicting document types. ransmission to this recipient will not be possible. he recipient will not receive a message because there's a conflict between the document types supported by the ervice and the device used by the recipient's Address. Moderate rror 0x ervice D [D] xecution D [D] egment D [D] ubmitting Value s for ndex Value. Recording the number of nformation bjects that will be executed through the specified nformation ource. nfo () A D X 0x x x B ervice D [D] xecution D [D] egment D [D] nformation bject j was not executed because no personalizations were found for a particular nformation ource ndex Value. ervice D [D] xecution D [D] egment D [D] Ready to process userset ndex Value. ervice D [D] xecution D [D] egment D [D] - ublication [D]supports device [D] which is used by recipient [AddressD]. However the ublication and the Device do not support the same ransmission Module. ransmission to this recipient will not be possible. he specified nformation bject was not executed because no personalizations were found for the nformation ource that the nformation bject belongs to. Users sharing the same personalization and preferences are grouped into Userets. he data for the specified Useret has been retrieved and is ready to be formatted and transmitted. he recipient will not receive a message because it uses a device that does not support the same nformation ransmission Module as the ublication in the ervice. Minor rror nfo () Moderate rror 314 Appendix arrowcast erver rror odes

335 Message rror ode Message ext ssue Description Message Level 0x ervice D [D] xecution D [D] egment D [D] rror formatting Document [Documentame]. FormatDocumentlement failed for lement ndex Value [rror umber:rror Description]. rror occurred while formatting a portion of the Document. Document element's error handling rules will be applied to determine if we insert a replacement string or fail the document. f we fail the document, then the whole message might fail if the document is required by the ublication thus affecting all recipients sharing the same personalization and preferences. Minor rror 0x D ervice D [D] xecution D [D] egment D [D] Document [Documentame] ersonalized lement [ndex Value] is being canceled due to partial results [rror umber:rror Description]. An error occurred while trying to replace a document element (no personalizations) with an error string. he Document will be canceled. Minor rror 0x x F ervice D [D] xecution D [D] egment D [D] Document [Documentame] Document lement ndex Value will be replaced because rror Description. ervice D [D] xecution D [D] egment D [D] Document [Documentame] will be removed because Document lement ndex Value rror Description. A document element will be replaced with an error string because it failed to execute. A document element will be removed from the Document because it failed to execute. nfo () nfo () A D X 0x ervice D [D] xecution D [D] egment D [D] BuildUserArrays returned success with info: rror Description Message ode: rror umber. he egment xecutor encountered an error while preprocessing the recipient information for the segment. nfo () 0x ervice D [D] xecution D [D] egment D [D] rror reported when trying to reset back up machine. rror will be ignored and will continue its execution [rror umber:rror Description]. An error was encountered when the egment xecutor was trying to switch the segment backup machine. he segment may no longer be backed up. Moderate rror egment xecutor 315

336 Message rror ode Message ext ssue Description Message Level 0x ervice D [D] xecution D [D] egment D [D] nformation bject ndex Value was not executed during resubmit jobs because no personalizations were found for nformation ource ndex Value. he specified nformation bject was not executed because no personalizations were found for the nformation ource that the nformation bject belongs to. Minor rror 0x ervice D [D] xecution D [D] egment D [D] Document [Documentame] Document lement ndex Value returned partial data, but will not be removed. Document property indicates that partial results are acceptable. nformational message indicating that partial results are acceptable for this Document lement. his is according to the error handling rules configured for the Document lements. nfo () A D X 0x x ervice D [D] xecution D [D] egment D [D] Delivery otification ubscription could not be created for recipient ndex Value. ervice D [D] xecution D [D] egment D [D] Document [Documentame] will be removed because Document lement ndex Value & rror Description. he specified recipient had requested a delivery notification following the delivery of this message, however there was a problem generating the notification and the notification will not be sent. he specified Document will be removed from the ublication. his is a result of the error handling rules for the Document/ublication. Minor rror nfo () 0x ervice D [D] xecution D [D] egment D [D] rror formatting Document [Documentame]. FormatDocumentlement failed for lement ndex Value [rror umber:rror Description]. here was a problem formatting a Document lement for the specified Document. Minor rror 0x ervice D [D] xecution D [D] egment D [D] Document [Fileame] Formatnsertiontring failed for lement ndex Value rror umber : rror Description. here was a problem generating the error message that was supposed to replace a failed Document lement for the specified Document. Minor rror 316 Appendix arrowcast erver rror odes

337 Message rror ode Message ext ssue Description Message Level 0x ervice D [D] xecution D [D] egment D [D] nformation ource D [D] ndex [ndex Value] called Returnubscriptionnformatio nbjectresult on the egment xecutor. his is an invalid call and it will be ignored. rror caused by an nformation ource calling a method that is not supported by the egment xecutor. his call should only be made back to the BM. Moderate rror 0x ervice D [D] xecution D [D] egment D [D] An unknown error occurred while receiving the nformation ource Reference from the ool. he cannot proceed further and it will terminate [rror: rror umber Desc: rror Description]. An unknown error occurred while receiving the reference to an nformation ource. f this happens the segment execution will fail as no content can be retrieved from this nformation ource. Moderate rror 0x x ervice D [D] xecution D [D] egment D [D] Unexpected error while receiving results from nformation ource [ndex Value] [ndex Value] [rror: rror umber Desc:rror Description] execution cannot continue. ervice D [D] xecution D [D] egment D [D] Unexpected rror in Usersetent: [rror: rror umber Desc: rror Description]. will terminate. An unknown error occurred while receiving Jobs from the specified nformation ource. An unknown error occurred in the function that concludes the processing of a given Useret. Moderate rror Moderate rror A D X 0x ervice D [D] xecution D [D] egment D [D] Unexpected rror in Beginerminating: [rror: rror umber Desc: rror Description]. will continue terminating. Unknown error occurred while beginning the shutdown process of the egment xecutor. Moderate rror 0x ervice D [D] xecution D [D] egment D [D] Unexpected rror in Finisherminating: [rror: rror umber Desc: rror Description ]. will continue terminating. Unknown error occurred while ending the shutdown process of the egment xecutor. Moderate rror egment xecutor 317

338 Message rror ode Message ext ssue Description Message Level 0x A ervice D [D] xecution D [D] egment D [D] Unexpected rror in ignalresetbackupmachine: [rror: rror umber Desc: rror Description]. An unknown error was reported when trying to set the flag to reset the back up machine for this segment execution. he egment xecutor will continue its execution. Moderate rror 0x B ervice D [D] xecution D [D] egment D [D] Failed to split ublications. he ervice for Web Deliveries contained elective documents. he egment xecutor failed to create the required ublications per elective Document ype. Moderate rror A D X 0x x D 0x ervice D [D] xecution D [D] egment D [D] Document [Documentame] Formatnsertiontring failed for lement ndex Value - rror umber:rror Description. ervice D [D] xecution D [D] egment D [D] Document [Documentame] lement ndex Value is being canceled due to partial results. rror umber:rror Description. ervice D [D] xecution D [D] egment D [D] Formatted a document of unknown type. An error occurred while trying to replace a failed document element with an error string according to the Document lement error handling rules. he Document will be canceled. A Document lement failed and it is being treated as failure based on the Document lement error handling rules. he egment xecutor encountered a Document of an unknown type. his may happen in an environment in which custom Document Formatters have been developed. nfo () nfo () nfo () 0x F ervice D [D] xecution D [D] egment D [D] Unexpected error while receiving recipient array. he egment xecutor encountered an unexpected error when receiving the recipient information from the BM. Moderate rror 318 Appendix arrowcast erver rror odes

339 Message rror ode Message ext ssue Description Message Level Moderate rrorevere rror0x ervice D [D] xecution D [D] egment D [D] here was a problem trying to cancel service on the nformation ource object while shutting down the FMManager [rror umber:rror Description]. here was a problem trying to notify the nformation ource that the segment is being canceled and the egment xecutor is shutting down. Minor rror 0x ervice D [D] xecution D [D] egment D [D] here was a problem trying to unload service on the nformation ource object while shutting down the FMManager [rror umber:rror Description]. here was a problem trying to notify the nformation ource that the segment has finished and the egment xecutor is shutting down. Minor rror 0x ervice D [D] xecution D [D] egment D [D] Resolved umrecipients recipients in Value milliseconds for segment properties [Value]. Message informing the total amount of time that was taken to obtain the recipient information. tat - egment 0x x ervice D [D] xecution D [D] egment D [D] egment will result in Value Jobs (personalization/ combinations) to be executed. ervice D [D] xecution D [D] egment D [D] egment execution will result in Value formatted documents. Message informing the total number of Jobs (personalization/ combinations) that will be executed. Message informing the total number of Documents that will be formatted. tat - egment tat - egment A D X 0x ervice D [D] xecution D [D] egment D [D] nformation ource D [D] will run nformation bject [D] and Locale string [Localetring] with ount Value personalizations. nformation message logged before executing nformation bject informing how many times an nformation bject will be executed. tat - egment 0x ervice D [D] xecution D [D] egment D [D] nformation ource D [ndex Value] received results for nformation bject [ndex Value] and Locale D [D] with status Value. Message informing that Job results were successfully received from the nformation ource for the given nformation bject. tat - Recipient egment xecutor 319

340 Message rror ode Message ext ssue Description Message Level 0x ervice D [D] xecution D [D] egment D [D] Document Formatter D [D] Document ame [Documentame] formatted in Value milliseconds. Message informing the total amount of time that was taken to format a Document. tat - Recipient 0x ervice D [D] xecution D [D] egment D [D] Address D [D] was transmitted. Message informing that the M sent a message to the given address. tat - Recipient 0x ervice D [D] xecution D [D] egment D [D] Address D [AddressD] ubscription D [D] was finished with status Value. Message informing that egment xecutor is done sending information to the given address. tat - Recipient 0x ervice D [D] xecution D [D] egment D [D] Document [Documentame] has been canceled. Message logged when a Document has been canceled. tat - Recipient A D X 0x x A ervice D [D] xecution D [D] egment D [D] nformation ource D [ndex Value] received o Data Returned for nformation bject [ndex Value]. ervice D [D] xecution D [D] egment D [D] Document Formatter D [Formatterame] Document ame [Documentame] was not formatted because the delivery was canceled. Message informing that Job results from the nformation ource were received with no data for the given nformation bject. Message informing that the Document was not formatted because the segment execution has been canceled. tat - Recipient tat - Recipient 0x B ervice D [D] xecution D [D] egment D [D] will transmit to ount Value Recipients. Message informing the total number of Recipients that will receive a particular message. tat - Recipient 0x ervice D [D] xecution D [D] egment D [D] nformation ource D [ndex Value] received results for nformation bject [ndex Value] with error message: rror Description. Message informing that Job results from the nformation ource were received with errors for the given nformation bject. tat - Recipient 320 Appendix arrowcast erver rror odes

341 Message rror ode Message ext ssue Description Message Level tat - egmenttat - Recipient0x D ervice D [D] xecution D [D] egment D [D] ompression process beginning: ompressed Filename: Value, ompression level: Value, umber of documents to Zip: ount Value, ompressed ection name: Value, ublication D [D]. nformation about the zipping operation that is about to happen. nfo () 0x ervice D [D] xecution D [D] egment D [D] ompression process finished: ompressed ection name: Value, ublication D [D]. Message informing that a zipping operation has completed. nfo () 0x F Moderate rror0x ervice D [D] xecution D [D] egment D [D] ompression process failed. anceling delivery for intended recipient(s). ublication D [D] ection name: Value. rror Message from ompression: rror Description rigin: Value. ervice D [D] xecution D [D] egment D [D] ompression turned on, but there were no documents in the section to compress. ection name: Value, ublication D [D]. An error occurred during the zipping process. he message will be canceled for the recipients in this personalization/device/loca le/compression group. Message indicating that a zipping operation was requested for this service, but the ublication ection, which is supposed to be compressed is empty. Minor rror nfo () A D X 0x ervice D [D] xecution D [D] egment D [D] found a file to include in the ompressed file: Filename: Value, ontent-type: Value, ompressed ection name:value, ublication D [D]. Message indicating that a file will be added to the zip file. nfo () nfo ()Minor rror0x ervice D [D] xecution D [D] egment D [D] Unexpected error in Arrays.ReceiveResults [rror: rror umber Desc:rror Description]. An unknown error occurred while receiving Jobs from nformation ource. ome nformation bject results may be lost. Moderate rror egment xecutor 321

342 Message rror ode Message ext ssue Description Message Level 0x A ervice D [D] xecution D [D] egment D [D] Unexpected error in Heart.ick, state = Value [rror: rror umber Desc: rror Description]. An unexpected error happened in the main loop of the egment xecutor code. Moderate rror 0x ervice D [D] xecution D [D] egment D [D] Unexpected error in FMManager.ick. tate: Value, hutting down value: Value [rror: rror umber Desc:rror Description]. An unexpected error happened in the formatting and transmitting loop of the egment xecutor. Moderate rror 0x D ervice D [D] xecution D [D] egment D [D] Unexpected rror in ransmitallback: [rror: rror umber Desc: rror Description]. An unknown error occurred while a ransmitter was notifying the egment xecutor about the result of a transmission. Moderate rror A D X 0x x000014A0 ervice D [D] xecution D [D] egment D [D] Unexpected rror in AppendFM: [rror: rror umber Desc: rror Description]. ervice D [D] xecution D [D] egment D [D] Unexpected rror in MRnformationourceotif y_nformationourcefailed: [rror: rror umber Desc: rror Description]. An unexpected error happened in the specified function. An unknown error occurred during a callback from the nformation ource to the egment xecutor indicating failure. Moderate rror Moderate rror 0x000014A1 ervice D [D] xecution D [D] egment D [D] Unexpected rror in MRnformationourceotif y_returnnformationbjectre sult: [rror: rror umber Desc: rror Description]. An unknown error occurred while receiving results from the nformation ource. Moderate rror 0x000014A2 ervice D [D] xecution D [D] egment D [D] Unexpected rror in MRnformationourceool otify_returnnformationour cereference: [rror: rror umber Desc: rror Description]. An unknown error occurred while receiving an nformation ource reference from the ool. Moderate rror 322 Appendix arrowcast erver rror odes

343 Message rror ode Message ext ssue Description Message Level 0x000014A3 ervice D [D] xecution D [D] egment D [D] Unexpected rror in MRubscriptionBookotif y_ubscriptionetresults: [rror: rror umber Desc:rror Description]. An unknown error occurred while receiving the results for a ubscription et from the ubscription Book Module. Moderate rror 0x000014A4 ervice D [D] xecution D [D] egment D [D] Unexpected rror in ervicexecutor_ontinuee rvice:[rror: rror umber Desc: rror Description]. An unknown error occurred while the egment xecutor was trying to process the request to resume a segment execution. Moderate rror 0x000014A5 ervice D [D] xecution D [D] egment D [D] Unexpected rror in ervicexecutor_ancelerv ice: [rror: rror umber Desc: rror Description]. An unknown error occurred while the egment xecutor was trying to process the request to cancel a segment execution. Moderate rror 0x000014A6 0x000014A7 ervice D [D] xecution D [D] egment D [D] Unexpected rror in ervicexecutor_auseervi ce: [rror: rror umber Desc: rror Description]. ervice D [D] xecution D [D] egment D [D] Unexpected rror in FMnitialized: [rror: rror umber Desc: rror Description]. An unknown error occurred while the egment xecutor was trying to process the request to pause a segment execution. An unknown error occurred while the egment xecutor was verifying whether the Format Manager was properly initialized. Moderate rror Moderate rror A D X 0x000014A8 ervice D [D] xecution D [D] egment D [D] Unexpected rror in FMFinished [rror: rror umber Desc: rror Description]. An unknown error occurred while the egment xecutor was verifying whether the Format Manager was properly shutdown. Moderate rror 0x000014A9 ervice D [D] xecution D [D] egment D [D] Unexpected rror in Usersetent: [rror: rror umber Desc: rror Description]. An unknown error occurred while the egment xecutor was concluding the processing of a Useret. Moderate rror egment xecutor 323

344 Message rror ode Message ext ssue Description Message Level 0x000014AA ervice D [D] xecution D [D] egment D [D] Unexpected rror in ervicexecutor_resetback upmachine: [rror: rror umber Desc: rror Description]. An unknown error occurred while the egment xecutor was trying to reset its backup machine. Moderate rror 0x000014B ervice D [D] xecution D [D] egment D [D] Unexpected rror in MRnformationransmitter otify2_nformationallback: [rror: rror umber Desc: rror Description]. An unknown error occurred during a callback from the ransmitter Module to the egment xecutor. Moderate rror 0x000014BF ervice D [D] xecution D [D] egment D [D] Unexpected rror in MRnformationourceool otify_nformationourcefail ed: [rror: rror umber Desc: rror Description]. An unknown error occurred while the ool was notifying the egment xecutor about an nformation ource failure. Moderate rror A D X 0x000014D1 0x000014D2 ervice D [D] xecution D [D] egment D [D] Unexpected rror in MRnformationransmitter otify2_ransmitallback: [rror: rror umber Desc: rror Description]. ervice D [D] xecution D [D] egment D [D] Unexpected rror in Handle_ransmitallback: [rror: rror umber Desc: rror Description]. An unknown error occurred during a callback from the ransmitter Module to the egment xecutor. An unknown error occurred during a callback from the ransmitter Module to the egment xecutor. Moderate rror Moderate rror 0x An unexpected error happened. Recycling process App.Xame. An unexpected error occurred, which will cause the egment xecutor to be recycled immediately. Moderate rror 324 Appendix arrowcast erver rror odes

345 xecution ngine he following table lists the error messages logged by the xecution ngine. t contains the message code, the message text, the error description, and the message level. Message rror ode Message ext ssue Description Message Level 0x00000D01 ervice D [D] xecution D [D] egment D [D] here was a problem initializing the ervice xecutor. he segment will not be executed [rror: Value]. here was a problem when trying to initialize the ervice xecutor. he segment will not be executed. Moderate rror 0x00000D04 ervice D [D] xecution D [D] egment D [D] Unable to get callback reference to pass to the egment xecutor while loading it. he segment will not be executed. Unable to provide the egment xecutor with a mechanism to communicate back to the xecution ngine. he segment will not be executed. Moderate rror 0x00000D05 0x00000D06 ervice D [D] xecution D [D] egment D [D] Unable to load ervice xecutor because the M component is not properly registered. he segment execution will not continue. ervice D [D] xecution D [D] egment D [D] Unable to create xecution Recorder because the M component is not properly registered. egment back up will not take place. Unable to load the ervice xecutor because the M component is not properly registered. he segment execution will not continue. Unable to create an xecution Recorder component because the M component is not properly registered. he backup feature will be disabled for this segment. Moderate rror Moderate rror A D X 0x00000D07 ervice D [D] xecution D [D] egment D [D] Unable to load ervice xecutor because nformation ource ool M object is not properly registered. egment execution will not continue. Unable to load the ervice xecutor because the nformation ource ool M object is not properly registered. he segment execution will not continue. Moderate rror 0x00000D08 ervice D [D] xecution D [D] egment D [D] he egment xecutor could not be created because of an instantiation error. egment execution will not continue. he ervice xecutor could not be created because of an instantiation error. he segment execution will not continue. Moderate rror xecution ngine 325

346 Message rror ode Message ext ssue Description Message Level 0x00000D09 ervice D [D] xecution D [D] egment D [D] Unable to create xecution Recorder because of an instantiation error. egment back up will not take place. Unable to create xecution Recorder because of an instantiation error. he backup feature will be disabled for this segment. Moderate rror 0x00000D0 here was a problem instantiating an nformation ource ool object. will continue executing, but may not function properly. here was a problem instantiating an nformation ource ool object. egment executions are likely to fail. evere rror 0x00000D0D ervice D [D] xecution D [D] egment D [D] annot stop segment backup because this was not recording that particular segment. Unable to stop segment backup because this xecution ngine was not recording that particular segment. Minor rror A D X 0x00000D0 0x00000D0F 0x00000D11 ervice D [D] xecution D [D] egment D [D] Unable to Reset Backup machine for segment because this is not executing that particular segment. ervice D [D] xecution D [D] egment D [D] Unable to start segment execution because this is currently executing a segment with the same D. An error occurred when signaling the pinging thread to stop. he will continue shutting down. Unable to reset the Backup xecution ngine machine for the specified segment because this xecution ngine isn't executing that particular segment. Unable to start segment execution because this xecution ngine is currently executing a segment with the same D An error occurred when signaling the pinging thread to stop. he xecution ngine will continue shutting down. Minor rror Moderate rror Minor rror 0x00000D12 Unable to start egment xecutor ping thread. will continue executing, but may not function properly. Unable to start the egment xecutor ping thread. he xecution ngine will continue executing. Moderate rror 0x00000D13 ervice D [D] xecution D [D] egment D [D] Unable to perform segment failover because the xecution recorder could not recover the segment's execution [rror:description]. Unable to do segment failover because the xecution Recorder could not recover the segment's execution information. Moderate rror 326 Appendix arrowcast erver rror odes

347 Message rror ode Message ext ssue Description Message Level 0x00000D14 ervice D [D] xecution D [D] egment D [D] Unable to finish segment execution because this is not executing that particular segment. Unable to process the completion of a segment's execution because this xecution ngine does not have a record of that particular segment. Moderate rror 0x00000D15 ervice D [D] xecution D [D] egment D [D] Unable to call back DM in order to notify that the segment execution has finished. Unable to call back the Distribution Manager in order to notify that the service execution has finished. evere rror 0x00000D16 ervice D [D] xecution D [D] egment D [D] could not open xecution Recorder for backup. egment back up will not take place [rror:description]. xecution ngine could not open the xecution Recorder for backup. he backup feature will be disabled for this segment. Moderate rror 0x00000D17 0x00000D18 0x00000D20 ervice failed during M initialization [rror: Value]. here was a problem while trying to load the arrowcast erver ype Library (BypLib.DLL) [rror: Value]. will terminate. ervice D [D] xecution D [D] egment D [D] An error was reported while loading the ervice xecutor. egment execution will be canceled [rror:description]. he initialization of the xecution ngine's ervice failed. he xecution ngine will not be able to operate. here was a problem while trying to load the file BypLib.DLL. he xecution ngine will stop. An error was reported while loading the ervice xecutor. he segment execution will be canceled. evere rror evere rror Moderate rror A D X 0x00000D21 ervice D [D] xecution D [D] egment D [D] here was a timeout while waiting for callback from the. here was a timeout while waiting for callback from egment xecutor process. Moderate rror 0x00000D22 ervice D [D] xecution D [D] egment D [D] here was a timeout while waiting for the segment cancel to take effect. here was a timeout while waiting for call to cancel a segment to take effect. Minor rror xecution ngine 327

348 Message rror ode Message ext ssue Description Message Level 0x00000D23 egment xecutor with process D did not respond to command "ontinueervice" and was terminated. he egment xecutor process did not respond to the "ontinueervice" command and was terminated. evere rror 0x00000D24 egment xecutor with process D did not respond to command "auseervice" and was terminated. he egment xecutor process did not respond to the "auseervice" command and was terminated. evere rror evere rrortat - xecution0x00000 D25 egment xecutor with process D did not respond to command "ancelervice" and was terminated. he egment xecutor process did not respond to the "ancelervice" command and was terminated. Moderate rror Moderate rrorevere rror0x00000d26 here was a problem reading the DM calls timeout setting from the registry. Using default timeout (Value seconds). [rror: rror]. here was a problem reading DM calls timeout setting from the registry. Minor rror A D X 0x00000D27 0x00000D28 Unable to set the U process affinity for component. he license information could not be obtained. he Us used by this will not be counted towards the maximum allowed by the license. ervice D [D] xecution D [D] egment D [D] Received segment execution request with egment D of a segment that is in the process of being canceled. Unable to set the U process affinity for this xecution ngine. he license information could not be obtained. he Us used by this xecution ngine will not be counted towards the maximum allowed by the license. he Distribution Manager has assigned a service to this xecution ngine which was previously assigned and has already been canceled. Moderate rror Moderate rrormoderate rror 0x00000D29 An unknown exception occurred in the. will shutdown. Generic catch all exception handler. he xecution ngine will shutdown. evere rror 0x00000D32 rocess nfo: rocessontextnformatio n. he xecution ngine is logging its process information. nfo () 0x00000D35 ervice D [D] xecution D [D] egment D [D] etwork status info: tatusnfo. he xecution ngine is logging its network status information. nfo () 328 Appendix arrowcast erver rror odes

349 Message rror ode Message ext ssue Description Message Level 0x00000D36 ervice D [D] xecution D [D] egment D [D] An application exception was caught while checking for network connection during a segment completion callback [rror: rror]. is presumed off the network and failover process is expected to be triggered once the DM detects the situation. afety net to catch any unhandled application exceptions while checking for network connection in case we could not callback to the Distribution Manager when the segment execution completes. evere rror 0x00000D37 here was a problem getting an nformation ource ool reference because the M component is not properly registered. will continue executing, but may not function properly. here was a problem getting an nformation ource ool reference because the M component is not properly registered. he xecution ngine will continue executing, but may not function properly. evere rror 0x00000D38 0x00000D39 ervice D [D] xecution D [D] egment D [D] here was a problem getting an nformation ource ool reference while failing a segment execution. he M component is not properly registered. he ool will not be notified. here was a problem getting an nformation ource ool reference because the M component is not properly registered. will continue shutting down. here was a problem getting an nformation ource ool reference because M component is not properly registered. he process of failing the segment will continue. here was a problem getting an nformation ource ool reference because the M component is not properly registered. he xecution ngine will continue shutting down. Moderate rror Minor rror A D X 0x00000D3A here was a problem getting an nformation ource ool reference because of an instantiation error. will continue shutting down. here was a problem getting an nformation ource ool reference because of an instantiation error. he xecution ngine will continue shutting down. Minor rror 0x00000D3B ervice D [D] xecution D [D] egment D [D] here was a problem instantiating an nformation ource ool object. egment execution will fail. rror: Value. Unable to load ervice xecutor because there was an error creating nformation ource ool. egment execution will not continue. Moderate rror xecution ngine 329

350 Message rror ode Message ext ssue Description Message Level 0x00000D3 ervice D [D] xecution D [D] egment D [D] he nformation ource ool could not be created because of error umber while failing a segment execution. he ool will not be notified. he nformation ource ool could not be created. his happened while failing a segment execution. he ool will not be notified. Moderate rror 0x00000D3D ervice D [D] xecution D [D] egment D [D] an not perform segment failover because this was not recording the segment's execution. Unable to perform the segment failover because this xecution ngine was not recording the segment's execution. Moderate rror 0x00000D3 ervice D [D] xecution D [D] egment D [D] Unable to cancel segment execution because this is not executing that particular segment. Unable to cancel the segment execution because this xecution ngine is not executing that particular segment. Minor rror A D X 0x00000D3F 0x00000D40 ervice D [D] xecution D [D] egment D [D] Unable to continue segment execution because this is not executing that particular segment. ervice D [D] xecution D [D] egment D [D] Unable to pause segment execution because this is not executing that particular segment. Unable to continue segment execution because this xecution ngine is not executing that particular segment. Unable to pause the segment execution because this xecution ngine is not executing that particular segment. Minor rror Minor rror 0x000005A ervice D [...] xecution D [...] egment D [D] Unable to locate the ervice D for this segment. he ervice D information is not available for this segment. Messages logged from this point forward will not contain a ervice D. Minor rror 0x000005B ervice D [...] xecution D [...] egment D [D] Unable to locate the ervice xecution D for this segment. he ervice xecution D information is not available for this segment. Messages logged from this point forward will not contain a ervice xecution D. Minor rror 330 Appendix arrowcast erver rror odes

351 nformation ource Module he following table lists the error messages logged by the nformation ource Module. t contains the message code, the message text, the error description, and the message level. Message rror ode Message ext ssue Description Message Level 0x2377 ubscription D [D] exceeds maximum allowed number for ransmission Recording (2,147,483,64). he ransmission Recorder will not save records for this ubscription D. he subscription D specified in the ubscription Book Repository is greater than 2,147,483,647. Moderate rror nformation ransmission Module Message rror ode 0x2377 he following table lists the error messages logged by the nformation ransmission Module. t contains the message code, the message text, the error description, and the message level. Message ext ssue Description Message Level ubscription D [D] exceeds maximum allowed number for ransmission Recording (2,147,483,64). he ransmission Recorder will not save records for this ubscription D. he subscription D specified in the ubscription Book Repository is greater than 2,147,483,647. Moderate rror A D X nformation ource Module 331

352 A D X 332 Appendix arrowcast erver rror odes

353 ADX D D.arrowcast erver ecurity D Microtrategy arrowcast erver affords specific levels of security in its architecture. his appendix describes: Microtrategy arrowcast erver M transmitter through network firewall upported security measures Distributed omponent bject Model Remote Method nvocations ample configuration options Microtrategy arrowcast erver M transmitter through network firewall n some cases, corporate networks make use of firewalls to protect the internal LA resources from external unauthorized access. Microtrategy arrowcast erver is unable to transmit M nternet messages if the server nternet access is restricted by a firewall. n this case, all the M messages need to be sent through an M server with relay capabilities configured as a smart host. For additional information, refer to mart host mode. o deliver a message using the smart host mode, perform the following steps: 1. n the Device ditor, click the Delivery ptions tab. 2. pecify the address of the M server. he M server should have access to the nternet and it should be configured to relay messages originated in the Microtrategy arrowcast erver machine. A D X 333

354 3. pecify the port number where the M server receives incoming elect the Use mart Host Always check box. 5. Repeat steps 1 to 4 above for all the devices used by the subscribers. upported security measures ecurity with Microsoft A D X Microtrategy arrowcast erver uses Microsoft nternet nformation erver () to publish information and bring business applications to the Web. is a required component when the ubscription ortal is installed. wo procedures can be performed to restrict access to the admin folder to valid Windows users: When the virtual directories are created the virtual directories are set to have both anonymous access and Windows authentication enabled. he admin folder under the virtual directory only has Windows authentication enabled, while anonymous access is disabled. hese procedures are performed automatically as part of the installation and again as part of the virtual directory creation in the ortal Administrator. For additional information on anonymous access or Windows authentication, refer to the documentation provided with Microsoft. Account privileges arrowcast erver requires Windows Administrator Account privileges on the machine on which arrowcast erver is installed. At the time of installation you are prompted to provide an account for arrowcast erver to run. arrowcast erver does not run if the account you provide does not have full Administrator privileges. For more information on account privileges, refer to Windows domain requirements in the arrowcast erver nstallation and onfiguration Guide. 334 Appendix D arrowcast erver ecurity

355 ryptography arrowcast erver uses the Blowfish algorithm to encrypt the following data: Repository data source name (D) passwords that are stored in the registry Repository data source name (D) passwords that are stored in the properties file ersonal identification numbers (s) stored in the ubscription Book Repository User passwords in the ubscription Book Repository asswords for the Microtrategy nformation ource Module that are stored in the respositories ubscription ortal subsystem arrowcast erver ubscription ortal operates through a Web browser. herefore it requires different security measures. ubscription ortal supports the following security measures and configurations: ecure ockets Layer (L) Firewalls nternet rotocol ecurity (ec) hese measures have been tested to work with the ubscription ortal. Distributed omponent bject Model A D X A Microtrategy arrowcast erver distribution manager uses Distributed omponent bject Model (DM) to communicate with distribution managers and execution engines on other machines. he Windows ervice account used by the distribution manager should have both the DM launch and access permissions on all the machines. During the installation of arrowcast erver, DM launch and access permissions are automatically granted to the local Administrators group, which should contain the Windows ervice account used by the distribution manager. Multiple ports are needed for DM. ort 135 is needed for the initial negotiation. nce the initial port is set, the communication ports can range between 1024 and hese ports, with the exception of the initial Distributed omponent bject Model 335

356 port, can be configured. onfiguration details can be found at /msdn_dcomfirewall.htm. Remote Method nvocations Microtrategy arrowcast erver uses Remote Method nvocations (RM) to communicate between the ubscription ortal subsystem and the ubscription erver subcomponent. he RM registry runs when the ubscription ortal accesses the ubscription erver using RM communicating with a dynamically configured port. here is not a set of designated, configured ports for the RM, so setting a firewall between the ubscription ortal A and the ubscription erver is not advisable. However, the initial port the RM registry is running from is configurable. Additional information on RM can be found at mi/spec/rmi-arch.doc.html#4799. A D X ample configuration options Microtrategy arrowcast erver is available in two separate editions, tandard and nterprise. ach edition is dependent on the serial key purchased from Microtrategy, as each edition supports different configuration options. he following examples detail some of the different scenarios of security in a arrowcast erver ubscription ortal subsystem environment, but do not provide a comprehensive list of the options available. hree configurations are described: onfiguration A: All components on one server onfiguration B: ypical nstallation onfiguration : nterprise dition using Windows load balancing onfiguration A: All components on one server n this configuration all ubscription ortal subsystem components are housed on one server. he repositories are stored on a separate database server. A firewall can be placed between the nternet and the ubscription ortal subsystem. 336 Appendix D arrowcast erver ecurity

357 onfiguration B: ypical nstallation erver 1: ubscription ortal subsystem erver 2: equelink and repositories Firewall to nternet H ubscription ortal ubscription ortal A Web server JDB (uses H) Firewall to orporation equelink ortal Repository bject Repository DB ubscription Book Repository A D X his configuration contains all ubscription ortal subsystem components on one machine. equelink and the repositories are contained on their own servers. Firewalls are placed between the nternet and Web server as well as the Web server and equelink server. onfiguration : nterprise dition using Windows load balancing erver 1: ubscription ortal subsystem erver 2: ubscription ortal subsystem erver 3: ubscription ortal subsystem ample configuration options 337

358 erver n: equelink and repositories firewall to nternet A D X n the Windows load balancing environment, multiple Web browsers filter through a Windows load balancing server and are distributed to the servers that can best handled the incoming workload. o complete a scenario such as this, multiple servers (numbering n) are set up with the ubscription ortal subsystem to balance the incoming workload. he firewall is placed between the nternet connection and the server. Windows load balancing server 338 Appendix D arrowcast erver ecurity

359 ADX.arrowcast erver Windows ervices arrowcast erver provides several components that run as Microsoft Windows services on arrowcast erver systems. A Windows service can be defined as a program, routine, or process that performs a specific system function to support other programs, particularly at low (close to the hardware) level. hese arrowcast erver Windows services are described in summary. References to more information are provided. Microtrategy Distribution Manager: riggers and manages service execution by distributing service workload to available execution engines. eeds to run under a Windows network account with administrative privileges on all machines that are part of the arrowcast erver system. For more information, see Distribution managers. Microtrategy xecution ngine: erforms the work of gathering service content, formatting it, and delivering it to devices. eeds to run under a Windows network account with administrative privileges on all machines that are part of the arrowcast erver system. For more information, see xecution engines. Microtrategy Logging lient: Receives logging messages from arrowcast erver components and relays them to the Microtrategy Logging erver. Logging messages include segment status information, statistics information, and error event notification. For more information, see Microtrategy Logging erver and lients. Microtrategy Logging onsumer: Receives messages from Microtrategy Logging erver and logs them to a variety of destinations such as the Windows vent Log, a set of text files, or the ystem Message Viewer dialog box. For more information, see Microtrategy Logging erver and lients. Microtrategy Logging erver: ollects logging messages from Microtrategy Logging lients and distributes them to Microtrategy Logging onsumers. For more information, see Microtrategy Logging erver and lients. A D X 339

360 Microtrategy DF Formatter: nables arrowcast erver to produce DF output. nly used for the DF generation of reports from Web ubscription. For more information, see Web subscription. Microtrategy M ervice: nables arrowcast erver to generate messages and transmit them via M. For more information, see etting up arrowcast erver for transmission. All services require the Log on as a service privilege. Microsoft Windows automatically grants this privilege to an account when that account is used to run a service. As long as this privilege is not revoked manually, no changes are needed. A D X 340 Appendix arrowcast erver Windows ervices

361 ADX F F.ervice xecution Flow in arrowcast erver F he following sections describe the flow of service executions in Microtrategy arrowcast erver. ach section is one step in the process. he step is explained and failure points are identified where appropriate. ervice triggered and inserted into queue ummary: A service is triggered by an Application rogram nterface (A) call or a schedule and inserted into the service execution queue. Details: A service execution can be triggered two ways: n arrowcast Administrator, select Run mmediately on the toolbar. he scheduler has a list of occurrences for every service (with its subscription sets) that is associated with a schedule. he scheduler requests the execution for each of those occurrences, according to the system time in the distribution manager machine. For example, if: ervice 1 is associated with the very 30 minutes schedule and the two subscription sets ubeta and ubetb ervice 2 with very 10 minutes is to be sent to one subscription set ubet then the scheduler triggers executions at these times: 00:10 ervice 2-ubet 00:20 ervice 2-ubet 00:30 ervice 1-ubetA, ervice 1-ubetB, ervice2- ubet 00:40 ervice 2-ubet etc. A custom application can execute a service at any time by calling the A function MRDeliveryngine_xecuteervice. For more information, see the online arrowcast erver DK Guide. A D X 341

362 Highest priority service selected, recipients per segment determined A D X ummary: he service with the highest priority in the execution queue is selected. he distribution manager looks at the service definition to determine the maximum number of recipients per segment. Details: he entire service definition is loaded recursively from the repository by the rimary Distribution Manager (DM). f it is an ad hoc service definition, it instead might be passed in. A service definition includes the following: service properties service-unique identifier, priority, execution timeout, segment size, and segment expiration subscription set definition interpretable only by the ubscription Book Module content definition list of publications, with their documents, supported devices, and locales components definition initialization properties for the ubscription Book Module, information sources, formatters, and transmitters Failure oints f the distribution manager cannot load the service definition because the bject Repository is unavailable due to a network problem or if the database server is offline, the service is retried continuously. After the service is loaded, if the service has already exceeded the expiration time, it is not executed. f the service definition fails to be loaded because the service does not exist in the repository, the service is failed. ne situation where this can occur is if the distribution manager and the arrowcast Administrator are pointing to different repositories. ubscription et Ds and segment size passed to ubscription Book Module ummary: he distribution manager passes the subscription set Ds and segment size to the ubscription Book Module. 342 Appendix F ervice xecution Flow in arrowcast erver

363 egments created and information passed to distribution manager ummary: he ubscription Book Module (BM) divides the subscription set into segments and passes the segment boundaries and the number of recipients back to the distribution manager. he segments are then inserted into the segment execution queue. Details: o distribute the load as equally as possible among execution engines, the rimary Distribution Manager (DM) divides the subscription set into equal segments. First it creates an instance of the ubscription Book Module. he DM then asks it to segment the subscription set into segments, the segment size depending on the service destination. For example, consider a service with a segment size of 3 that is to be executed using ubscription et 1, which contains 11 users. he communication between the DM and the BM would look like this: he DM asks BM to segment (ubscription et 1, segment size=3). After running Microtrategy reports, the BM returns a list of segments to the DM: seg1= (recipients 1 to 3) seg2= (recipients 4 to 6) seg3= (recipients 7 to 9) seg4= (recipients 10 to 11) he DM does not know how to interpret the segments returned by the BM; it only knows that there are four of them and that the BM will deal with them later, during each segment execution. n some instances, such as with dynamic subscription sets, the BM requires running a report to segment the service. n this case, the BM requests an instance of the information source that will run the report. he BM uses the instance to run the segmentation report (segment information object) and then returns the segments to the DM, the same as in the previous example. he execution engine and distribution manager manage information sources through the nformation ource ool. he ool is created when the DM or execution engine () are created. t is responsible for managing information source instances and providing them to the components that need them, such as the BM or the segment executor. A D X egments created and information passed to distribution manager 343

364 Failure oint he subscription set segmentation can fail because the BM cannot connect to the ubscription Book Repository database, such as when the network has problems, the database is offline, and so on. egmentation is retried until the ubscription Book Repository becomes available again or until the service expiration time is exceeded. A common situation, which is not considered an error, is when the BM returns zero recipients. n this case the service execution terminates successfully. egment assigned to execution engine and information provided A D X ummary: f an execution engine is available, the segment with the highest priority is assigned to that execution engine and its backup is determined. he segment definition is sent to the execution engine and then the execution engine checks the service definition for a list of required information sources. Details: nce the rimary Distribution Manager (DM) knows how many segments need to be executed for a given service execution, it gives each segment a unique D and inserts them in the queue of segments to be executed. his queue holds all the pending segments, for all the service executions, because there could be segments from different services waiting to be executed. he DM starts assigning segments from the queue to available execution engines. egment executor initialized and information sources identified ummary: he execution engine initializes the segment executor. he segment executor determines what information sources to use. Details: he segment executor requests the instances of the information sources it needs to complete the service execution. 344 Appendix F ervice xecution Flow in arrowcast erver

365 Failure oint f an information source fails to be initialized, the segment is failed over. A possible cause could be that the information source is unavailable because the ntelligence erver is not running. he segment is placed back into the distribution manager's segment queue to be reassigned. he number of times an individual segment is failed over is determined by the failover count of the system governing settings. egment definition sent to ubscription Book Module to retrieve recipients ummary: he segment executor sends the segment definition to the ubscription Book Module to get all the recipients for that segment. Details: he segment executor creates an instance of the BM and passes the segment definition to it. he BM returns a list of recipients. ome of the relevant fields that are returned for each recipient are: Device D Locale D Authentication-ecurity-ersonalization for each question object hysical Address ime Zone Failure oint f resolving recipients fails, the segment is failed over. his can occur if the ubscription Book Repository (BR) is unavailable because of network problems, an offline BR database, or incorrect DB settings. he segment is replaced into the segment queue to be reassigned. f the BR is unavailable, the failover count for the segment is not incremented when the segment is reassigned. A situation that is not considered an error is when zero recipients are returned for a segment. his might happen when a service uses dynamic subscription sets. he segment execution finishes successfully. A D X egment definition sent to ubscription Book Module to retrieve recipients 345

366 Recipient list sent to segment executor and analyzed A D X ummary: he recipient list is sent to the segment executor () and the analyzes that list to determine what results are needed. Details: o support internationalization, which is achieved through the use of locales, the segment executor matches the service content with the recipient's locale. ach recipient receives only one publication, according to the following rules: f a publication supports the exact device-locale combination that the recipient has, the recipient receives this publication. f not, determine if the next rule applies. f a publication supports the recipient's device and the ystem Locale, the recipient receives this publication. f not, the recipient does not receive any content. deally, the same device-locale combination should be supported by only one publication. However, if two or more publications match the device and locale for that recipient, the first of those publications found in the service definition is used. he publications in the definition are sorted in the same order as they are shown in the ervice ditor. nce the segment executor determines which publications need to be sent to whom, it works only on the ones that have at least one recipient. For each publication, the following steps occur: tep 1. nitialize transmitter tep 2. nitialize formatters tep 3: erform personalization bucketing tep 4: egment executor sends information object request to information source module ach step is described below. tep 1. nitialize transmitter he transmitter used by this publication is initialized. Remember that one publication supports only one transmitter. 346 Appendix F ervice xecution Flow in arrowcast erver

367 Failure oint f a transmitter fails to initialize itself, the segment is failed over. he segment is placed back into the segment queue to be reassigned. An example of M ransmitter failure is if the Domain ame erver (D) registry setting is not located. tep 2. nitialize formatters Formatters used by this publication are initialized. he static content is passed to the formatters so they are only waiting to receive dynamic content, if any exists. Failure oint f one of the formatters fails to be initialized, the segment is failed over. he segment is placed back into the segment queue to be reassigned. tep 3: erform personalization bucketing his step attempts to reduce the number of jobs submitted to the information sources for dynamic content. he segment executor analyzes the list of recipients and determines if several recipients share the same authentication-security-personalization objects combination for each question object used in a publication. he recipients with common characteristics are grouped in buckets or Usersets since they will receive the same content. he segment executor analyzes the list of recipients and determines if several recipients share the same authentication-security-personalization objects combination for each question object used in a publication. he recipients with common characteristics are grouped in buckets or Usersets since they will receive the same content. o understand how the bucketing is improved, consider the following scenario: A D X User nformation ource nformation bject nformation bject preference (prompt answer) David Y 1 A David Y 2 no prompt on report Recipient list sent to segment executor and analyzed 347

368 User nformation ource nformation bject nformation bject preference (prompt answer) James Y 1 B James Y 2 no prompt on report A D X n this case, the following four jobs are created: Job 1 for nformation bject 1 for personalization A Job 2 for nformation bject 2 Job 3 for nformation bject 1 for personalization B Job 4 for nformation bject 2 n Microtrategy arrowcast erver and earlier, for some cases the bucketing algorithm did not result in the least number of jobs possible. his is possible with Microtrategy arrowcast erver o obtain the optimal bucketing behavior, in Microtrategy arrowcast erver 8.0.3, you can combine the jobs by changing the default value of the UsemprovedMstr7Bucketing registry key. With the registry key value as 0, we get four buckets. When you change the value of the registry key to 1, job 2 and job 4 are joined to create the following three buckets: Bucket 1: nformation bject 1 - personalization A Bucket 2: nformation bject 1 - personalization B Bucket 3: nformation bject 2 - no personalization ow to understand how the number of jobs is reduced, consider the following scenario: User nformation ource nformation bject nformation bject preference (prompt answer) David Y 1 A David Y 2 no prompt on report James Y 1 A James Y 2 no prompt on report 348 Appendix F ervice xecution Flow in arrowcast erver

369 o reduce the number of jobs, in Microtrategy arrowcast erver 8.0.3, you can combine the jobs by changing the default value of the UsemprovedMstr7Bucketing registry key to 0. With this we have only two jobs as follows: Job 1: nformation bject 1 - personalization A Job 2: nformation bject 2 - no personalization Modifying registry values incorrectly may cause serious, system-wide problems that may require the re-installation of Microsoft Windows. Any edit of the registry is done at the user s own risk. ince these are user-initiated changes, they are not covered by any Microtrategy warranty. f using Microsoft Windows, the user should backup the registry and/or update an mergency Repair Disk (RD) prior to alterations. o change the registry key value, perform the following steps: 1. Browse to the location: HKY_LAL_MAH\oftware\microstrategy\ Microstrategy broadcast server\ 7.0\execution engine. 2. hange the value of the UsemprovedMstr7Bucketing registry key to 1. nce personalization bucketing is done the recipient's locale is no longer used. nstead, the document locale is passed to the information sources, formatters, and transmitters. he document locale is considered the run-time locale and is defined in the document editor by selecting File, then roperties. For example, if a recipient's locale is panish and the publication that supports this locale contains documents with the locale set to Japanese, A D X he information source requests the report results from the ntelligence erver with Japanese date and currency formats. he transmitter uses the encoding method for Japanese (shift-j). f the system is intended to support multi-language settings, the services must be carefully designed to take full advantage of the locale feature and to avoid sending conflicting content to the end user. Recipient list sent to segment executor and analyzed 349

370 tep 4: egment executor sends information object request to information source module his step includes seven substeps, 4A through 4G. hey are described below. 4A. he segment executor submits jobs to the information source module. ach information source receives the request to each of the information objects used in the publication. he request contains a list of all the unique personalizations (user sets). he information source calls back with the job results as they are completed. A D X Failure oint f the information source encounters a critical error during the job execution, it notifies the egment xecutor. he segment is failed and placed back into the segment queue to be reassigned. An example is when the Microtrategy nformation ource detects that the ntelligence erver is not responding to the requests. 4B. he result sets are returned to the segment executor and queued. 4. he segment executor sends the result sets to the document formatting module where the document templates and elements are formatted. After all the document elements that need to be placed in a document are formatted, the segment executor asks the formatter to format the document. he complexity of this operation depends on the kind of formatter. For example, the Hyper ext Markup Language (HML) formatter has to paste the document elements into the HML source. n contrast, the xcel formatter has to first parse the document elements to extract table structures and then insert those table structures into the specified xcel binary file. nce the information object results are ready, the segment executor begins to submit them to the formatters. A set of information objects that belong to the same document element is passed to the formatter at once. ince each document element can have an assigned stylesheet, a formatter is expected to apply the stylesheet, process the output if necessary, and then return the intermediate formatting result to the segment executor. f a certain document element consists only of non-personalized information, the segment executor can cache formatted document element results. ome error handling decisions are made depending on the settings defined for each information object and each document within a publication. Refer to appendix G, roubleshooting. 4D. he document formatting module sends the formatted documents back to the segment executor. 350 Appendix F ervice xecution Flow in arrowcast erver

371 4. When all of the personalized documents for a subscriber are complete, the segment executor sends the formatted documents to the appropriate information transmission module for message delivery. he segment executor sends notification to the execution recorder that the message was sent, and also to the transmission recording log tables. 4F. he segment executor notifies the execution engine when all of the messages in the segment were sent and it is done processing the segment. he segment executor is unloaded. 4G. he execution engine notifies the distribution manager that the segment is complete. he segment is updated in the execution queue. When all segments for a service are complete, the ubscription Book Module is disconnected. A D X Recipient list sent to segment executor and analyzed 351

372 A D X 352 Appendix F ervice xecution Flow in arrowcast erver

373 ADX G G.roubleshooting G his appendix identifies troubleshooting tools useful in resolving issues and lists problem symptoms, potential causes, and corrective actions. Modifying registry values incorrectly can cause serious, system-wide problems that might require the reinstallation of Microsoft Windows. Any edit of the registry is done at your own risk. ince these are user-initiated changes, they are not covered by any Microtrategy warranty. f using Microsoft Windows, you should back up the registry and/or update an mergency Repair Disk (RD) prior to alterations. roubleshooting tools ystem Message Viewer You can access this from arrowcast Administrator by selecting View ystem Messages from the ools menu. n general, you can use the ystem Message Viewer to view error information and statistical messages that are generated by Microtrategy arrowcast erver. You can control the amount of information generated by Microtrategy arrowcast erver by modifying the registry settings located in: HKY_LAL_MAH\oftware\Microtrategy\ Microtrategy Broadcast erver\7.0\ Distributed Logging ervice\ ML lient ettings\logging Levels. For more information about the registry settings, refer to onfiguring the Microtrategy Logging erver in chapter 3. A D X 353

374 ortal Administrator error log For the ubscription ortal, you can go to the ortal Administrator and modify the URL to be name/virtual directory/admin/showerrors.asp to see a description of the error that was raised in the A code. Log files Use the logging files generated by the product, which are stored in the same location as the product files. hese files have names that begin with DLog followed by a date, and the suffix.txt. Monitor Monitor is an application that lets you monitor debug output on your local Microtrategy arrowcast erver system. t can display Win32 debug output; therefore, you do not need to open the arrowcast erver logs to capture the output of the system. A D X ystem creation Modifying registry values incorrectly can cause serious, system-wide problems that might require the reinstallation of Microsoft Windows. Any edit of the registry is done at your own risk. ince these are user-initiated changes, they are not covered by any Microtrategy warranty. f using Microsoft Windows, you should back up the registry and/or update an mergency Repair Disk (RD) prior to alterations. ymptom You cannot browse to find or type in name of the distribution manager. ause: he machine is not accessible on the domain or is unavailable. Actions: 1. Add the machine to the domain or verify network connectivity and check login and startup permissions. 2. urn on Level_nfo_DM and Level_race_DM in the registry and obtain those logs plus the debug viewer log. 354 Appendix G roubleshooting

375 ymptom bject Repository and/or ubscription Book tables were not created. ause 1: ot enough permissions. Action: Verify that the same user can drop/create tables on the database. ause 2: he database is full. Action: Verify that there is enough space in the database by creating a table. You can use stodbc2.exe from the Util folder. ymptom bject Repository and/or ubscription Book Repository tables were not created in DB2. ause: he default code set of DB2 does not support VARGRAH data type. Action: reate a new DB2 database with the UF-8 code set. ymptom A Registry settings on the target machine indicate that the machine is currently being used by Delivery ngine system ' ' as 'Microtrategy Logging server', message appears when trying to add a distribution manager or execution engine machine. ause: he machine to be added as a distribution manager, execution engine, or Microtrategy Logging erver is already being used by another system. Action: Remove the machine from the distribution manager, execution engine, or Microtrategy Logging erver list of the other system. A D X ymptom An Unexpectedrror: Unable to perform the operation because you have insufficient privileges message appears when trying to add a distribution manager or execution engine machine. ause: he user is not an administrator on the machine to be added as a distribution manager or execution engine. Action: Add the user to the administrator group of the target machine. ystem creation 355

376 ymptom A D X A JVM creation failed (ot enough memory) message appears when the reate a ubscription ortal site check box is selected while configuring the ubscription ortal. ause: While configuring a ubscription ortal, arrowcast erver reserves a certain amount of consecutive memory from the memory heap. he portal configuration fails because the size of this heap is too large and arrowcast erver does not use the JVM HeapMaxize value from the registry. Actions: 1. Delete the Xmx64M value from the HKY_LAL_MAH\FWAR\Microtrategy\J Bridge\onfiguration\JVM ptions\webptions registry key, if you had added the value while configuring the ubscription ortal in arrowcast erver onfigure the HKY_LAL_MAH\FWAR\Microtrategy\ Microtrategy Broadcast erver\7.0\ ubscriptionortal registry key and set it to a value that is less than 192MB. he tarting the Delivery ngine ubscriptionortal registry key is added in arrowcast erver to control the memory used by the ubscription ortal. he ubscriptionortal key is created only when you create a ubscription ortal. ymptom A ystem is not running message appears when trying to start the system. ause 1: he distribution manager services account is not an administrator on the distribution manager machine. Action: Add the distribution manager service account to the Administrators group on the target (distribution manager) machine. ause 2: Administrators do not have DM permissions on the distribution manager machine. 356 Appendix G roubleshooting

377 Action: Add the administrators group to DM: 1. lick tart and select Run. 2. ype dcomcnfg and click K. 3. n the Distributed M onfiguration roperties dialog box, select the Default ecurity tab. 4. Under Default Access ermissions, click dit Default. 5. n the Registry Value ermissions dialog box, click Add. 6. n the Add Users and Groups dialog box, to add a group, highlight the group name and click Add. o add individual users, highlight the group name and click Members. Highlight the user names to add and click Add. 7. he names appear in the Add ames field. lick K. 8. n the Registry Value ermissions dialog box, the names appear. lick K. 9. Under Default Launch ermissions, click dit Default. 10. n the Distributed M onfiguration roperties dialog box, click Apply, then click K. hese services must be set up on the machines where the distribution manager and execution engine will be running. ymptom A an t create distribution manager message appears when trying to start the distribution manager. ause 1: he distribution manager services account is not an administrator on the distribution manager machine. Action: Add the distribution manager service account to the administrator group on the target (distribution manager) machine. ause 2: Administrators do not have DM permissions on the distribution manager machine. Action: Add the administrators group to DM. For steps to add DM permissions to the administrators group, see the previous ymptom. A D X ymptom A an t start any distribution managers message appears when starting the system. tarting the Delivery ngine 357

378 ause 1: he Microtrategy Logging lient Windows service failed to start. Action: ry using the ystem onfiguration Wizard to reset the Microtrategy Logging erver and Logging lient configuration. heck the vent viewer on the machine where the Microtrategy Logging lient is not loading to determine if there is a port conflict or other problem. ause 2: one of the distribution manager machines is available. nsufficient permissions. Action: Verify that all the machines configured as distribution managers have the software installed correctly. s at least one of them up and running? Does the Windows login being used on the arrowcast Administrator machine have administrator permissions on the distribution manager machines? s the distribution manager services account password correct? ymptom A D X A database deadlock occurs during service segmentation on the Microtrategy arrowcast erver system for Web scheduling and end ow. ause: For a end ow schedule, the Microtrategy arrowcast erver system executes six services every minute. hese six services are for delivering a Document or a Report in a File, rint, and -mail format. f no service is associated with the end ow schedule, the six services are not required to run. n such cases, the Distribution Manager yields zero segments. hus, the Distribution Manager is unnecessarily loaded, which subsequently loads the ubscription Book Repository database. Action: elect the n Demand chedule check box on the nterval page of the chedule Wizard. n this case, if there are no end ow schedules, the service execution is stopped before the segmentation of a service is done. egmentation is done only when a end ow subscription is created for the service. elect the n Demand chedule check box on the nterval page of the chedule Wizard. elect this check box for a end ow schedule so that service execution is stopped before the segmentation of a service is performed. egmentation is performed only when there is a subscription associated with the schedule that is fired. 358 Appendix G roubleshooting

379 ervice creation and execution Modifying ymptom registry values incorrectly can cause serious, system-wide problems that might require the reinstallation of Microsoft Windows. Any edit of the registry is done at your own risk. ince these are user-initiated changes, they are not covered by any Microtrategy warranty. f using Microsoft Windows, you should back up the registry and/or update an mergency Repair Disk (RD) prior to alterations. When users send messages via , wireless, or to a directory location using the -mail (M) or Wireless (M) nformation ransmitters, the service fails to be delivered and one or more of the following error messages is present in the system message viewer: Unavailable D for the system or Unable to initialize M ervice M is down. ause: he Domain ame erver (D) settings used by the Microsoft Windows imple Mail ransfer rotocol (M) service are not properly configured in the registry (D settings are Windows operating system networking properties used by arrowcast erver). he machine has Dynamic Host onfiguration rotocol (DH) enabled but is logged off from the DH-erver. Action: o resolve this problem you need to update the appropriate keys in the Windows registry in all machines used as execution engines by your arrowcast erver system. he specific keys to be modified or added depend on whether the network uses DH (Dynamic Host onfiguration rotocol machines that obtain their address configured dynamically) or tatic addresses (machines that have hard-coded addresses). o check whether the machine uses DH or a tatic Address, follow the steps below: 1. Right-click My etwork laces (etwork eighborhood in Windows ) and select roperties. 2. Right-click Local Area onnection or the LA icon currently in use and click roperties. 3. Double-click nternet rotocol (/). 4. lick Advanced. A D X ervice creation and execution 359

380 5. lick the ettings tab. his tab displays DH nabled under addresses if this machine uses DH. hen follow the procedure described below to update the registry on every machine used as an execution engine by arrowcast erver. When in doubt about which values to enter, contact the ystem Administrator for assistance. You can also check if this information is already entered on another machine in the same domain. A D X Updating the registry 1. top all arrowcast erver services (distribution manager, execution engines, logging services, and so on) before manually editing the registry. 2. Locate and update the Domain ame and D address keys in the registry. For machines that use static addresses, locate the following registry location: HKY_LAL_MAH\YM\urrentontrolet\ ervices\cpip\arameters hen add Domain and ame server string keys with values as specified by your ystem Administrator. For networks using DH, locate the following registry location: HKY_LAL_MAH\YM\urrentontrolet\ ervices\cpip\arameters heck whether the DhcpDomain and Dhcpameerver keys are present. he action you take now depends on whether the required keys are present and contain empty strings of whether the keys themselves are not present. cenario 1: Registry Keys are resent n this scenario, the registry values are present but contain empty strings. his often occurs in a test domain scenario where there is a DH-erver but no D configured. heck the address of the DH-erver using the ipconfig /all command at the Windows command prompt. ontact the Domain Administrator to perform the following changes on the DH- erver: 1. Log in to the DH-erver as Domain Admin. 2. onfigure DH (Windows ). pen the Win tool DH Manager. elect the localmachine (that is, the DH-erver). 360 Appendix G roubleshooting

381 From the DH ptions menu, select cope. Move the item Domain ame to the Active ptions. nter the user s domain name into the string box. ote: For the purpose of sending messages to directory locations only, that is, not using M, you can enter any dummy value. 3. onfigure DH (Windows 2000 Advanced erver). n omputer Management, expand ervices and Applications. xpand DH and right-click erver ptions. hoose onfigure ptions. n the General tab, select the 015 D Domain ame check box and type the domain name in the space provided for tring Value. ote: For the purpose of sending messages to directory locations only, that is, not using M, you can enter any dummy value. 4. When you reboot any client in that domain, it picks up the dummy value at startup and writes it into the registry. cenario 2: Registry Keys are ot resent n this scenario, the two registry values are not present although the client is configured as DH enabled. his happens most likely on a laptop that is not connected to its DH-erver. 1. top the Microtrategy Distribution Manager service. 2. Add the registry string values DhcpDomain and Dhcpameerver as tring values into HKY_LAL_MAH\YM\urrentontrolet\ ervices\cpip\arameters. 3. nter any dummy entries into the two string values. 4. Restart the Microtrategy Distribution Manager service. he service should now run successfully. A D X ymptom You cannot access, write to or manipulate the bject Repository. ause: You have incorrect or insufficient permissions to the bject Repository. Action: heck to see if the login used to access the database was entered correctly and if it has the appropriate permissions for that database. ervice creation and execution 361

382 ymptom he bject Repository is not responding or is returning incorrect information or no information at all. ause: A non-supported or non-certified pen Database onnectivity (DB) driver is used for the repository. Action: Determine the answers to the following questions: 1. Where is the repository stored (same machine as arrowcast erver or ubscription Book Repository)? 2. s the data source name (D) for that database configured properly (check to ensure validity)? 3. What database platform is used for the repository? 4. What version of the DB driver is used for that database platform? 5. s your platform and/or driver certified or supported? (heck the readme for supported and certified platforms and drivers.) 6. s the repository an upgrade from or connection to a previous version or a new repository altogether? A D X ymptom ome documents are removed from the service. For example, only the subject is sent, while the message body is empty. ause: he document contains information objects that are failing to execute or to be formatted. Action: dit the document that is failing. Double-click each document element and add rror Handling Rules for each field. Run the service again. his time the document is received, possibly with some error messages, as specified in the rules. ymptom An information object within a document is returning an error or no data. ause 1: he recipient is not personalized correctly. Action: f the information object has a question object associated to it, ensure that the recipients have a preference objects associated to them. Go to the tatic ubscription et ditor and for each user, double-click and check the reference tab. r double-click each subscription and check the reference tab. 362 Appendix G roubleshooting

383 ause 2: he Microtrategy report is not configured properly to run in arrowcast erver. Action: Run the report using the Microtrategy Desktop interface. Does the report fail? Fix the problem in Desktop and try to run the service again. Does the report contain prompts? hen you need to set up a default answer or create question and preference objects in arrowcast Administrator. heck the documentation for more information. Does the report return no data? his is fine. Add appropriate error handling for it or change the filtering criteria so that the report returns data. ymptom A document element failed to be formatted. ause 1: he stylesheet applied does not match the document type. Action: nside the document editor, verify that the selected stylesheet matches the type of document. hat is, for HML, use the Microtrategy7 default XL file stored in the For HML documents folder. ause 2: he stylesheet file in the repository was not loaded correctly. Action: From the object browser, double-click the XL file. he path and file name appears in the File text box. s it pointing to the right location? f not, click the browse ( ) button and reimport it. ause 3: XML results combined with XL do not produce the expected output. Action: here might be a problem with the XL definition that causes it to fail during XL transformation. r the resulting XML might not match the format expected for the xcel or lain text DFMs. f you wrote custom XLs, verify that they meet the specifications as specified in the XML for arrowcast erver bjects appendix of the arrowcast erver Application Designer Guide. Verify that they transform correctly by testing your custom XLs using the estxml ool. By default, this tool is installed in the :\rogram Files\Microtrategy\arrowcast erver\delivery ngine\utilities folder. A D X ymptom ome or all of the messages for a service are not sent. ause 1: he recipient device-locale combination does not match any publication. Action: pen the tatic ubscription et ditor and verify that ervice creation and execution 363

384 the user locale matches the publication locale. ystem is the default for services created with the ervice Wizard. the addresses subscribed to the service use the devices supported by the publication. By default, the ervice Wizard uses Generic -mail. ause 2: f using remote machines as the distribution manager or execution engine, the data source name (D) for the ubscription Book is not present on one of those machines. Action: onfigure a D for the ubscription Book Repository on all the machines. onfigure a D for the bject Repository on machines used as distribution managers. ause 3: A document failed that is required for the publication. Actions: dit the documents contained in the service that is failing. Double-click each document element and add rror Handling Rules for each field. ause 4: he subscription set contains zero valid recipients. Action: pen the tatic ubscription et ditor. Make sure that the ubscription et box contains at least one valid and active address. A D X ymptom ervices are not fired. ause: A schedule or service might be inactive. Action: Verify that both the service and schedule are active. lick Administration, then cheduled ervices. Are the next occurrences for the service shown? f not, click et Queue arameters in the toolbar and change the parameters accordingly. f you still cannot see your services, the schedule definition might be incorrect. ymptom n the ublication Wizard, a device does not appear in the list of available devices. ause: he device does not correspond to the selected transmitter. Action: Go back and select the transmitter that is used by the device, or create an additional publication that uses the desired transmitter. ymptom n the ublication Wizard, when browsing for files to be attached, imported files are not displayed. 364 Appendix G roubleshooting

385 ause: Files cannot be used as attachments. Action: reate a new document of type Formatted ontent. Associate it with the imported file and save it. Go to the ublication Wizard. he document is displayed and it can be used as a binary attachment. ymptom Graphic information objects are not available to be inserted in an xcel document. ause: Graphic information objects can only be used in HML documents. Action: reate a new tabular information object and insert it in the workbook. Use an xcel macro to render this tabular data as an xcel chart. ymptom A service with a dynamic subscription set delivers some duplicated e- mails. ause: egment Boundary prompt default values were altered, becoming uninterpretable by arrowcast erver. Action: Use automatic segmentation. ee the arrowcast erver Application Designer Guide for instructions on using automatic segmentation. ymptom o data is returned for a service with a segment size of 1. ause: egmentation metrics are incorrectly constructed (or set with 7.0 directions). Action: Use automatic segmentation. ee the arrowcast erver Application Designer Guide for instructions on using automatic segmentation. A D X ymptom ccasionally, the toolbar icons are shown as black squares. ause: his is because the toolbar file agent.tb is corrupted. Action: Find and delete the agent.tb file, close the application, and open again. ervice creation and execution 365

386 ymptom A D X ymptom 1: he arrowcast ervices are started on the server machine, but you see that the system is stopped in the arrowcast Administrator. ymptom 2: You have enough arrowcast privileges and you are trying to run a service, but nothing happens. ymptom 3: When a user configures the arrowcast Administrator on a remote machine, a message appears indicating that the account is not set up in the arrowcast system. Along with this message, any of the following cases can be applicable: he Microtrategy setup application does not ask for credentials in an upgrade process. he user decides to use the local system account as the account for the services. he credentials presented during installation are not correct. he password used to set up the identity has expired. ause: he user does not have administrative privileges on the remote machine. Action: f your non-administrative users want an access to the arrowcast run time functionality, you need to configure the dentity settings of the DM servers. he DM user in charge of configuring a arrowcast cluster still needs to be a Windows Administrator. configuration must be correct for the system to run successfully. An error in the DM configuration may render the system unusable. o configure the DM servers, perform the following steps: 1. lick tart and select Run. 2. nter dcomcnfg and click K. 3. elect the DM servers to configure. You need to configure the MDMroxy and Mroxy servers. 4. lick the dentity tab. 5. elect his user: and enter the required data in the User, assword, and onfirm assword text boxes. 6. lick K. 366 Appendix G roubleshooting

387 7. Restart the system. f you want to revert to the regular Administrative mode, set the DM identity for the servers to the user that is launching the arrowcast erver. ymptom When a protected xcel 2003 file is imported and used as a template for an report delivery in a service, the xcel file is not editable. But after the report is generated and delivered to the user, the cells that contain the report data can be edited. ause: arrowcast erver changes the properties of the xcel file so that the protected cells that contain the report data become editable after it is imported into a service. Action: nsure that the xcel 2003 file has worksheet/workbook-level protection enabled, before it is imported into arrowcast erver. After the xcel file is imported, you need to create a Lockxcelells registry key and set the value to true. he registry key should be created at the following location: \HKY_LAL_MAH\FWAR\Microtrategy\ Microtrategy Broadcast erver\7.0\ xecutionngine. ymptom While executing a service that uses nformation bjects, the arrowcast erver M cannot connect to the ntelligence erver machine. Due to the connectivity issue, the execution fails and an error message is displayed. ause: f your system is clustered, and if the ntelligence erver machine and the arrowcast erver machine that contains the M are in different domains, you may encounter connectivity issues. Action: o establish a connection between the arrowcast erver M and the ntelligence erver, add the machine name and address of the ntelligence erver in the host file (:\WDW\system32\drivers\etc\hosts) of the arrowcast erver M machine. he machine name specified in the host file should match with the ntelligence erver name in the arrowcast erver M. A D X ymptom arrowcast erver is not responding while executing a service and the Maximum oncurrent ervice execution error is listed in the error log. ervice creation and execution 367

388 ause: f the number of segments in the segment execution queue reaches the specified At least value of the segment queue size, the segment queue does not receive new segments from the service queue. Due to this, the service queue exceeds the maximum number of concurrent executing services limit and the Maximum oncurrent ervice execution error is listed. Action: You can reset the At least value of the segment queue size as follows: 1. From the ystem menu, select the system, then select et Governing ettings. he ystem ettings dialog box opens. 2. n the xecution tab, in the egmentation section, increase the value in the At least field. ncreasing the At least value ensures that the available segment executors on the operational xecution ngines are fully utilized and the queue is not empty. As more segments are included in the segment queue, the number of services in the service queue is reduced. ymptom A D X When a service execution fails in arrowcast erver, an error message Unable to instantiate the BM object is listed in the DLogs and ystem Message Viewer. ause: his message can appear when some of the Microtrategy DLL (Dynamic Link Library) files are not registered or are invalid. Action: From Windows Add or Remove rograms, reinstall the Microtrategy components. For steps to reinstall the Microtrategy components, see nstallation rocedures of the arrowcast erver nstallation and onfiguration Guide. ymptom A delivery failure occurs during service execution on arrowcast erver. ause: ne possible cause of a failed service can be an authentication failure. he subscribed arrowcast user is configured to inherit the authentication of a Microtrategy user that is deleted in Microtrategy Desktop. Action: o delete the authentication definition of arrowcast user, edit the following settings from the ubscription Book in arrowcast Administrator: 368 Appendix G roubleshooting

389 1. From the ools menu, select pen ubscription Book. he ubscription Book ditor opens. 2. elect the user to edit from the list of Users and addresses. 3. From the dit menu, select dit. he User roperties ditor opens. 4. lick the Authentication and ecurity tab. he user s Authentication and ecurity information is displayed in the tables. 5. elect the information source in the Authentication table whose authentication definition needs to be removed. 6. lick lear. 7. lick K to save the changes. For more information about editing users, see User roperties ditor of the arrowcast Administrator Application Designer Guide. ymptom After upgrading Microtrategy metadata, some services using dynamic subscriptions fail during segmentation and the error message egmentation failed or Unexpected error while receiving recipient array is displayed in the DLog file. his occurs only for services that use information sources which existed prior to the upgrade. t does not affect those services that use a newly created information source in arrowcast erver that is pointing to the same project on the ntelligence erver. ause: During Microtrategy metadata upgrade, the system object D unification process unifies the system object Ds to a fixed value. tarting with version 8.0.2, Microtrategy creates uniform system object Ds to support various Microtrategy features. nformation objects created prior to may continue to use old Ds, causing this error. Action: Run the Metadata Ds Updater ool to find and fix any inconsistencies in arrowcast objects caused by the metadata system objects unification process. You can run this tool in one of the following modes: Assess: o check whether there are any inconsistencies in your arrowcast objects in the arrowcast system. Fix: o fix the definition of your arrowcast objects in the arrowcast system. he changes are applied to the arrowcast object repository. rerequisites t is important to back up the arrowcast object repository before using the tool in Fix mode. A D X ervice creation and execution 369

390 A D X he Updater ool needs to be executed on a computer that has the arrowcast erver system registered. he Updater ool must have access to the metadata upgrade log file (MDUD-m-dd.log). By default, this log file resides on the computer that performs the upgrade, in rogram Files\ommon Files\Microtrategy\Log. he log is used to determine the objects that have changed in the metadata and those that need to be changed in the arrowcast erver repository. o install the Updater ool Run the register.bat file to register all the DLLs that are necessary to run the tool. he file is located in /Delivery ngine/utilities/metadata Ds Updater ool. For Windows Vista, Windows 2008, and Windows 2007, run the register.bat file in one of the following ways: Right-click ommand rompt and select Run as administrator. Run the register.bat file. Log in to Windows as the Local Administrator and double-click the register.bat file. For all other Windows operating systems, double-click the register.bat file. o execute the Updater ool 1. Run the MDDsAssessool.exe file. 2. elect the arrowcast system from the ystem election drop-down list. f the system connection is successful, a onnected to: Myystem message appears in the tatus section. 3. ype the location of the log file in the MD Upgrade Log File field or browse to locate the log file. he default location of the log file is ommon Files\Microtrategy\Log. 4. hoose either Assess or Fix mode. 5. lick Run. he result is displayed in the tatus section once the Assess or Fix is completed. 370 Appendix G roubleshooting

391 ubscription administration ymptom You cannot access, write to, or manipulate users, addresses, subscriptions, or preferences in the ubscription Book Repository. ause: You have incorrect or insufficient permissions to the ubscription Book Repository. Action: heck to see if the login used to access the database was entered correctly and if it has the appropriate permissions for that database. ymptom he ubscription Book Repository is not responding or is returning incorrect information or no information at all when you try to manipulate users, addresses, subscriptions, or preferences. ause: A nonsupported or noncertified DB driver is used for the repository. Action: Determine the answers to the following questions: 1. Where is the repository stored (same machine as arrowcast erver or bject Repository)? 2. s the data source name (D) for that database configured properly (check to ensure validity)? 3. What database platform is used for the repository? 4. What version of the DB driver is used for that database platform? 5. s your platform and/or driver certified or supported? (heck the readme for supported and certified platforms and drivers.) 6. urn on the Level_nfo_BM and Level_race_BM keys in the registry and obtain those logs plus the debug viewer log. A D X ymptom he message You do not have Write access to this rompt object appears when you try to define a security object or a preference object. ause: he authentication object for the user (or the default authentication object for the information source, if no authentication object is defined for the user) does not have Write permissions for the security object and/or question object prompts. ubscription administration 371

392 Action: Allow users to have Write access to prompts. 1. n the Microtrategy Desktop interface, right-click the prompt. 2. hoose roperties. 3. elect the ecurity tab. 4. Add a user or group and set permissions to Modify (or create a custom access control entry that grants Write permission). ince all users created in the Microtrategy Desktop interface could potentially be used to define authentication objects in arrowcast erver, it might be useful to set all prompts with Write access for the veryone group. n addition, it might be desirable to prevent users in Microtrategy Desktop from having access to the prompts used for security objects and question objects in arrowcast erver. o prevent unauthorized users from editing prompt objects through Microtrategy Desktop, keep prompt objects in a separate folder, and set the security on the parent folder to prohibit unauthorized users to access the children of the folder. o do this, set the permissions to Default in the hildren list for the user or group. A D X ymptom A prompt for a personalized service fails to be rendered. ause: he prompt is a level prompt. Action: Level prompts are not supported in the ubscription ortal. Redefine your prompt in the Microtrategy Desktop interface. ymptom he first prompt for a personalized service is rendered, but the second prompt is skipped. ause: he second prompt is an embedded prompt (a prompt based on the answer to the first prompt). Action: mbedded prompts are not supported in the ubscription ortal. Redefine your prompts in the Microtrategy Desktop interface and your question objects in arrowcast erver. ymptom howerrors.asp is showing a large number of communication link failure errors, or similar error messages indicating a lost database connection. 372 Appendix G roubleshooting

393 ause: equelink has lost contact with one or more databases. Action: top and start the equelink erver service from the services ontrol anel. ymptom Many display issues (question marks, blanks ) are encountered while using DB2 repositories. ause: he DB D may not be correctly configured. Action: Follow the instructions in DB2 requirements in the arrowcast erver nstallation and onfiguration Guide to correctly set up the DB2 driver. ymptom equelink seems to raise frequent Access Violations. ause: he DB driver version used is not the certified one. Action: Verify that your driver version is certified. heck Database requirements of the arrowcast erver nstallation and onfiguration Guide. ymptom ome of the service schedules are not shown under the ubscription ortal. ause: he ubscription ortal does not display any schedules in which the associated subscription set is reused as part of the definition of another service. Action: Make sure each schedule in your service definition is associated with a unique subscription set. A D X ymptom A link to an xcel attachment for a report on the ubscription ortal fails to open an xcel document. ause: he wrong version of xcel is on the client machine. Action: n the client machine, install the correct version: xcel 97 or xcel 2000 R-1. ymptom When using the ubscription Book synchronization tool, some valid V files are rejected as corrupted files. ubscription administration 373

394 ause: he ubscription Book cannot process the V files in which the number of fields in each row does not match the number of fields in the header row. Action: When generating the V files, ensure that every row has the same number of fields. You can do this by using Microsoft xcel. Add a dummy column to the end of each row and populate that column with the values in each row. ymptom A D X -mail (M) An error message lement not found appears when you try to edit a subscription information object. ause: f an information source definition is modified so that some information is no longer retrieved from the ubscription Book, editing a subscription information object that relies on this information produces this error message. Action: 1. Modify the information source definition temporarily to allow retrieving information from the ubscription Book. 2. Modify the affected subscription information object definition so that it no longer retrieves information from the ubscription Book. 3. Revert the information source definition back to its previous state, removing the ability to retrieve information from the ubscription Book. Modifying registry values incorrectly may cause serious, system-wide problems that may require the re-installation of Microsoft Windows. Any edit of the registry is done at the user s own risk. ince these are user-initiated changes, they are not covered by any Microtrategy warranty. f using Microsoft Windows, the user should backup the registry and/or update an mergency Repair Disk (RD) prior to alterations. ymptom -mails are neither saved to file nor delivered to the recipient s inbox. ause 1: he M information transmission module was misconfigured. Action: Verify that the from, reply-to and delivery notification addresses are well constructed, that is, something similar to aaa@aaa.aaa. 374 Appendix G roubleshooting

395 ause 2: M is using the wrong character set. Action: reate a new locale. lick -mail (M) and choose an appropriate character set for the language you want to broadcast. For example, use Kanji for Japanese and Western for French and other uropean countries. For each document used in the service, edit it, select File, then roperties, and change its locale to the one you just created. ause 3: n the M information transmission module configuration, ender Display ame or Reply o Display ame contain double-byte characters. Action: reate a new plain text document. elect File, then roperties. hange the document locale to the locale for the language you are trying to broadcast. Delete any content from the document (leave it empty). ave. nclude this document in the publication in the ontrol document section. ause 4: he recipient name contains double-byte characters. Action: Japanese or Korean characters in the recipient name are not supported for this release. et the ransmission roperties for addresses to be in neither the o nor the c list. ymptom During Microtrategy arrowcast erver configuration, the following message appears: 'he operating system(s) on machine(s): XXX are not properly configured to support transmission...'. ause: he Domain ame ystem (D) addresses for the machines on which Microtrategy arrowcast erver is installed are not in the required Windows registry entries. Action: dit the registry string value with the appropriate D addresses. You can enter either the address of the machine or the complete domain name. For the networks using Dynamic Host onfiguration rotocol (DH): 1. Browse to the following location: HKY_LAL_MAH\YM\urrentontrolet\ ervices\cpip\arameters 2. dit the DhcpDomain and Dhcpameerver registry string values. For the networks using tatic nternet rotocol addresses: 1. Browse to the following location: A D X -mail (M) 375

396 HKY_LAL_MAH\YM\urrentontrolet\ ervices\cpip\arameters 2. dit the Domain and ameerver registry string values. ymptom -mails are saved to file but not delivered to the recipient s inbox. ause: he physical address has an invalid domain. Action: n the ubscription Book, double-click the address. Verify that the domain name exists and is well constructed (address@domain.com). ymptom A delivery notification is not sent to the address specified. ause: he recipient s server does not support notifications. Action: heck that the Delivery otification address is valid. f a valid address does not work, it is possible that the recipient s server does not recognize/accept delivery notifications. A D X ymptom Messages sent to devices that use smart host are not delivered to the smart host server. ause: he device is not configured with the correct smart host address or port number. Action: pen the Device ditor to verify the definition of the device. Verify that the Delivery ptions tab contains correct information about the smart host. Verify that the server working as smart host is listening for M messages in the port number that has been configured for the device. ymptom Messages sent to devices that use smart host are delivered to the smart host server but not to the final recipients. ause: he smart host server is not running or it is not running in relay mode. Action: heck with the server administrator if the smart host server is running and ready to send messages. heck that the server is configured to work as a relay server. 376 Appendix G roubleshooting

397 ymptom Messages do not reach the recipients, even when the addresses are valid. ause: he M transmitter logs error messages indicating that the transmission to all the domains failed. he D server is not accessible to the M transmitter. Action: pen the registry and open the following key: HKY_LAL_MAH\YM\ urrentontrolet\ervices\cpip\arameters heck the parameter ameerver (if the machine has a static address) or Dhcpameerver (if the machine uses a dynamic address). Make sure that these parameters contain valid D addresses. heck with the network administrator for proper values for this parameter. ymptom -mails cannot be sent. ause: he network is configured with an internal-only D. arrowcast erver and all applications depend on D servers to send . here are two types of D: nternal, which do not contain the information necessary for applications (MX records) xternal, which allow applications to function When the network is configured with an internal-only D, no applications can send messages. his might have been done as a temporary measure to move a machine from one domain to another. Action: Remove the internal D and reconfigure the network with an external D. A D X ymptom HML is not rendered properly for some recipients. ause: he client does not support a certain type of HML. Action: Use the MR7toHML.xsl stylesheet specifically for AL, etscape, and Lotus otes clients. he stylesheet is located in the Delivery ngine folder. -mail (M) 377

398 ymptom arrowcast reports delivered in HML format are not correctly displayed in utlook ause: utlook 2007 uses Microsoft Word 2007, which does not support all HML attributes. Action: Use the MR7oHMLDefaultFormatting.xsl and MR7oHMLDefaultFormatting2.xsl stylesheets. hese XLs are located in the Delivery ngine folder. ymptom A D X Multi-layout Report ervices documents are not delivered as multiple sheets in a single Microsoft xcel file. ause: he layout settings for the multi-layout Report ervices document are not enabled in arrowcast Administrator. Action: nable Report ervices documents to display each layout on a separate Microsoft xcel sheet. teps on how to complete this configuration are provided below. 1. n the Desktop Document elector dialog box, select the document to edit from the list of Microtrategy Desktop documents. 2. From the hoose document format drop-down list, select xcel. 3. elect the xcel 2003, xcel X and above on recipient s machine option. 4. lick Advanced roperties. he Advanced roperties dialog box opens. 5. n the General tab, select the All Layouts option to receive all the layouts of a multi-layout Report ervices document. 6. elect the xpand all pages option to display all the pages of a group by field in the document. 7. lick K to save the changes. For more information about the Desktop Document elector dialog box, see the Desktop Document elector dialog box chapter of the arrowcast Administrator Application Designer Guide. ymptom Documents exported to Microsoft xcel using ntelligence erver cannot be opened or saved using utlook Web Access. 378 Appendix G roubleshooting

399 ause: he document is generated as an html file, and utlook Web Access cannot open html files. Action: nable Report ervices documents to be generated as mht files, which are compatible with utlook Web Access. teps on how to complete this configuration are provided below. 1. n the Desktop Document elector dialog box, select the document to edit from the list of Microtrategy Desktop documents. 2. From the hoose document format drop-down list, select xcel. 3. elect the xcel 2003, xcel X and above on recipient s machine option. 4. lick K to save the changes. rinting ymptom o document is printed. ause: he temp file location is full. Action: lean up the temp file location, or select another location using the device editor. ymptom You cannot print to a particular printer. ause: he printer cannot be registered dynamically at execution. Action: Register the printer manually using the Microsoft Add rinter Wizard. A D X ymptom You cannot print DF documents. ause: either Adobe Acrobat nor Adobe Acrobat Reader is installed. Action: nstall either Adobe Acrobat or Adobe Acrobat Reader on all execution engine machines. rinting 379

400 nformation ource Module ymptom While configuring the nformation ource Module, the following error message is displayed: ystem user needs to be a member of at least one of the following Microtrategy groups: ystem Monitors, arrowcast ystem Administrators, ystem Administrators. ause: he Microtrategy user is not assigned to the required group. Action: Assign the Microtrategy user to the ystem Monitors, arrowcast ystem Administrators, or ystem Administrators group. For detailed steps on how to assign users to a group, see the Microtrategy Desktop Help. ymptom A D X While configuring the nformation ource Module, the following error message is displayed: ystem user needs to have the privilege chedule Request in order to use this nformation ource. ause: he chedule Request privilege is removed from the ystem Monitors, arrowcast ystem Administrators, or ystem Administrators group. Action: Grant chedule Request privilege to the Microtrategy user. For detailed steps on how to grant privileges, see the Microtrategy Desktop Help. HML Document ditor Modifying registry values incorrectly can cause serious, system-wide problems that might require the re-installation of Microsoft Windows. Any edit of the registry is done at your own risk. ince these are user-initiated changes, they are not covered by any Microtrategy warranty. f using Microsoft Windows, you should back up the registry and/or update an mergency Repair Disk (RD) prior to alterations. 380 Appendix G roubleshooting

401 ymptom ome characters, such as æ,å,and ö, are not displayed correctly in HML documents when an HML document attachment is opened in nternet xplorer. ause: A Microsoft update has changed the character set that is automatically applied to HML documents that are edited in arrowcast erver Administrator on certain machines. Action: You need to create a new registry string value for the registry key: \HKY_LAL_MAH\FWAR\Microtrategy\ Microtrategy Broadcast erver\7.0\ Documentditors. he new string value is keepcharset. he value must be set to true to retain the original character set of the HML document. etting the value to false allows the HML editor to change the character set to Unicode, which may cause garbled characters. ortal Administrator ymptom n Windows 2008 nterprise R2 (64 bit) operating system, a local administrator (belonging to administrator group) is unable to access ortal Administrator by providing local admin credentials. ause: Microsoft changed the permissions structure for Windows 2008 and therefore privileges are not granted to the local administrator. Action: o grant the privileges: 1. Browse to \rogram Files\Microtrategy\arrowcast erver\ubscription ortal\asp\admin folder. he following message is displayed. A D X ortal Administrator 381

402 2. lick ontinue. he required user is automatically added. ymptom A D X While setting up Microtrategy ubscription ortal through the ortal Administrator, the error An error has occurred on this page is displayed after specifying the database connection name. he error details are listed in the ortal log at the following location: \rogram Files\Microtrategy\arrowcast erver\ ubscription ortal\asp\logs. ause: he error can appear if the ubscription ortal site was not created from Microtrategy arrowcast Administrator and hence the MRBJR table is not created. Action: You must create the ubscription ortal site using Microtrategy arrowcast Administrator. 1. From the ystem menu, point to the system that you want to edit, and select dit ystem onfiguration. he ystem onfiguration Wizard opens. 2. lick lustering at the top of the window. he verview page opens. 3. lick ext. he elect onfiguration ptions page opens. 4. elect the elect and configure a single machine for arrowcast erver option. You can click (the Browse button) to locate another machine. 5. elect the reate a ubscription ortal site check box to create the ubscription ortal site from arrowcast Administrator. 6. lick ext to go to the next configuration step. 382 Appendix G roubleshooting