OA2install

An Installation Guide for OAenterprise

License Terms. Any information furnished in this documentation ("Documentation") is the copyrighted work of ObjectAutomation, Inc. ("ObjectAutomation") and or its supp!iers. "se of the #oftware described herein ("#oftware") and Documentation is go$erned by the terms of the end user !icense agreement which accompanies or is inc!uded with the !icense fi!e and or insta!!ation of the #oftware ("%icense Agreement"), there is no transfer of tit!e. An end user wi!! be unab!e to insta!! any #oftware that is accompanied by or inc!udes a %icense Agreement, un!ess the end user first agrees to the %icense Agreement terms. Use Restrictions. &he #oftware and Documentation is made a$ai!ab!e so!e!y for use by end'users according to the %icense Agreement. Any reproduction or redistribution of the #oftware and Documentation not in accordance with the %icense Agreement is e(press!y prohibited by !aw. )opying or reproduction of the #oftware and Documentation, in who!e or in part, in print or to any other media, or in any other storage and retrie$a! system for further reproduction or redistribution is prohibited. Warranty Disclaimer. &*+ #O,&-A.+ A/D DO)"0+/&A&IO/ I# -A..A/&+D, I, A& A%%, O/%1 A))O.DI/2 &O &*+ &+.0# O, &*+ %I)+/#+ A2.++0+/&. +3)+4& A# -A..A/&+D I/ &*+ %I)+/#+ A2.++0+/&, O56+)&A"&O0A&IO/, I/). *+.+51 DI#)%AI0# A%% -A..A/&I+# A/D )O/DI&IO/# -I&* .+2A.D &O &*+ #O,&-A.+ A/D DO)"0+/&A&IO/, I/)%"DI/2 A%% I04%I+D -A..A/&I+# A/D )O/DI&IO/# O, 0+.)*A/&A5I%I&1, ,I&/+## ,O. A 4A.&I)"%A. 4".4O#+, &I&%+ A/D /O/'I/,.I/2+0+/&. Disclaimer Regarding Documents. ObjectAutomation and or its respecti$e supp!iers make no representations about the suitabi!ity of the information contained in the Documents and re!ated graphics pub!ished in this guide for any purpose. A%% #")* DO)"0+/&# A/D .+%A&+D 2.A4*I)# A.+ 4.O7ID+D "A# I#" -I&*O"& -A..A/&1 O, A/1 8I/D. O56+)&A"&O0A&IO/ A/D O. I&# .+#4+)&I7+ #"44%I+.# *+.+51 DI#)%AI0 A%% -A..A/&I+# A/D )O/DI&IO/# -I&* .+2A.D &O &*I# I/,O.0A&IO/, I/)%"DI/2 A%% I04%I+D -A..A/&I+# A/D )O/DI&IO/# O, 0+.)*A/&A5I%I&1, ,I&/+## ,O. A 4A.&I)"%A. 4".4O#+, &I&%+ A/D /O/'I/,.I/2+0+/&. In no e$ent sha!! ObjectAutomation and or its respecti$e supp!iers be !iab!e for any specia!, indirect or conse9uentia! damages or any damages whatsoe$er resu!ting from !oss of use, data or profits, whether in an action of contract, neg!igence or other tortious action, arising out of or in connection with the use or performance of information a$ai!ab!e from this guide. &he documents and re!ated graphics pub!ished in this guide cou!d inc!ude technica! inaccuracies or typographica! errors. Notice Regarding Software, Documents and Services. In no e$ent sha!! ObjectAutomation and or its respecti$e supp!iers be !iab!e for any specia!, indirect or conse9uentia! damages or any damages whatsoe$er resu!ting from !oss of use, data or profits, whether in an action of contract, neg!igence or other tortious action, arising out of or in connection with the use or performance of software, documents, pro$ision of or fai!ure to pro$ide ser$ices, or information a$ai!ab!e from these materia!s. Restricted Rights Legend. Any #oftware and Documentation on this )D !icensed for or on beha!f of the "nited #tates of America or its agencies and or organi:ations ("".#. 2o$ernment"), is pro$ided with .estricted .ights. "se, dup!ication, or disc!osure by the ".#. 2o$ernment is subject to restrictions as set forth in subparagraph (c)(;)(ii) of the .ights in &echnica! Data and )omputer #oftware c!ause at D,A.# <=<.<<>'>?;@ or subparagraphs (c)(;) and (<) of the )ommercia! )omputer #oftware ' .estricted .ights at AB ),. =<.<<>';C, as app!icab!e. 0anufacturer is ObjectAutomation, Inc., 4.O. 5o( =;<@D, Ir$ine, )A C<D;C';<@D. Copyright and Trademar Notice. OAenterpriseE is a registered trademark and ObjectAutomation is a trademark of ObjectAutomationF, Inc. 0icrosoft, -indows <???, -indows /&, -indows 34 and -indows #er$er <??@ are either registered trademarks or trademarks of 0icrosoft )orporation in the "nited #tates and or other countries. 6a$a and a!! 6a$a'based marks are trademarks or registered trademarks of #un 0icrosystems, Inc. in the "nited #tates and other countries. ObjectAutomation, Inc. is independent of #un 0icrosystems, Inc. Other product and company names mentioned herein may be the trademarks of their respecti$e owners. Any rights not e(press!y granted herein are reser$ed. )opyright G ;CCC'<??B ObjectAutomation, Inc. ObjectAutomation, Inc. 4.O. 5o( =;<@D Ir$ine, )A C<D;C';<@D httpH www.oa.com

Ta!le of Contents
"ntroduction#####################################################################################################iii $!out this %uide###############################################################################################v About the &utoria!.................................................................................................$ Document Conventions#####################################################################################v Related Documentation #################################################################################vii $!out &!'ect$utomation###############################################################################viii $ccessing the &!'ect$utomation We! Site#####################################################i(
&o access the ObjectAutomation web site.............................................................i( )orporate *ead9uarters.....................................................................................$iii

Contacting the Customer Satisfaction Team####################################################(

&o open the -indows &ask 0anager.....................................................................( &o open the -indows +$ent 7iewer !og fi!e...........................................................( &o create a #ystem Information ,i!e ....................................................................(

Chapter ) *uic Start "nstallation in +our ,asy Steps#########################################################)

; ' )heck 1our *ardware #oftware )onfiguration ..........................................; < ' Insta!! OAenterprise.................................................................................; /etworked )omputers..................................................................................; #ing!e )omputer..........................................................................................; @ ' Obtain the OAenterprise %icense )o!!ection ,i!e.........................................< A ' Insta!! 1our %icense )o!!ection ,i!e on the *ost /ode.........................................................................................<

Chapter Setting Up an &$enterprise "nstallation#############################################################. /lanning the "nstallation##################################################################################. .unning OAenterprise as a #tand'a!one /ode........................................................@ .unning OAenterprise as a Distributed #ystem.......................................................@
"nderstanding the OAenterprise )e!!................................................................................A )onfiguring an OAenterprise )e!!.....................................................................................A -hat is a )e!! 0anagerI..............................................................................................A -here is the best p!ace to insta!! the )e!! 0anagerI..................................................= -hat is a )e!! )!ientI...................................................................................................= -here is the best p!ace to insta!! a )e!! )!ientI..........................................................D Determining -hat to .un on an OAenterprise )e!! /ode................................................D -here is the best p!ace to run contro! enginesI........................................................D On what nodes shou!d the *0I screens runI............................................................D -hat shou!d I do, if response time deterioratesI.......................................................D

"nstallation Re0uirements################################################################################1 )hecking the .+AD0+ ,i!e....................................................................................B )hecking #ystem .e9uirements.............................................................................B O!der 7ersion of OAenterprise Insta!!edI..............................................................;? /otes about "pgrading the Operating #ystem .....................................................;; "nstalling &$enterprise##################################################################################)&o initiate the setup program.............................................................................;< &o insta!! a stand'a!one node..............................................................................;A &o insta!! a distributed OAenterprise system........................................................;= "pgrading an OAenterprise )e!!.....................................................................................;? -hat *appens to 1our +(isting OAenterprise %icense ,i!e after "pgradingI......................;? &o open the .+AD0+ fi!e.....................................................................................B

Licensing &$enterprise##################################################################################)2

http344www#oa#com

ii

Important /otes about %icensing.........................................................................;> 2enerating an OAkey..........................................................................................;B

If you are running one (or more) #tand'a!one /ode(s)....................................................;B If you are running an OAenterprise distributed ce!!.........................................................;B *ow do I decide which node I want to manage !icensingI...........................................;B &o generate an OAkey.......................................................................................;B &o obtain your !icense co!!ection fi!e through emai! or phone ...............................<?

&o !icense OAenterprise for a stand'a!one node en$ironment................................;D &o !icense OAenterprise for a distributed ce!! en$ironment ...................................;D

Obtaining a %icense ()O%) ,i!e.............................................................................<? Insta!!ing the %icense ,i!e....................................................................................<;

&o insta!! the !icense co!!ection fi!e......................................................................<;

http344www#oa#com

iii

Introduction
-e!come to OAenterprise, ObjectAutomationJsF Industria! Automation software p!atform. OAenterprise integrates rea!'time, distributed Object'5ased )ontro!F into production management systems to pro$ide a responsi$e, ru!es'based so!ution. OAenterpriseKs interacti$e data representation means better communication and contro! between and within business and operationa! systemsLa!! personne!, from management to operations, wi!! ha$e time!y access to the information they need to perform their jobs more effecti$e!y. And, with OA<webAccess, authori:ed users and systems can access critica! data and contro! operations through the Internet. OAenterprise enab!es creation and maintenance of app!ications that monitor and contro! di$erse manufacturing operations and business processes from a network of computers running 0icrosoft -indows <???, 34, 34 +mbedded and or #er$er <??@. OAenterprise can be used in a wide $ariety of app!icationsLinc!uding discrete, process, batch, distribution, motion contro!, and numerica! contro!Land pro$ides ser$ices that bridge these app!ications into enterprise p!anning and schedu!ing systems. OAenterprise is bui!t on an open, distributed object framework based on 0icrosoft operating systems and techno!ogy. &his framework a!!ows transparent distribution of an app!ication across a !oca! or wide'area network of computers, whi!e keeping the appearance, and simp!icity, of running on a sing!e, !oca! computer. 4ro$iding the foundation for bui!ding mission'critica!, rea!'time Industria! Automation, )ontro!, and Operationa! Inte!!igence so!utions, OAenterprise inc!udesH OAframework ' &he foundation for OAenterprise, the OAframework pro$ides a sing!e, coherent process mode! for manufacturing operations, business processes, and the supp!y chain, and inc!udes the basic network'computing infrastructure, resource management, and communication ser$ices for enterprise'wide contro!. OAworkbench ' &he primary user interface for designing, operating and maintaining OAenterprise so!utions, OAworkbench hosts a $ariety of user interface too!s that pro$ide specific configuration, $iewing, and editing functions. OA<contro! ' &he brain behind Operationa! Inte!!igence and )ontro!, pro$iding system design and e(ecution of business ru!es, data conso!idation scripts, process contro! a!gorithms and industria! automation !ogic. OA<contro! inc!udes the rea!'time e(ecution engine, strategy editor, and associated program editors for OAenterprise. OA<$iew ' &he eyes for seeing and hands for contro!!ing operations managed by OAenterprise. OA<$iew pro$ides the too!s to bui!d, maintain, and $iew animated graphica! representations of manufacturing operations and business processes.. OA<a!arms ' 4ro$ides the ser$ices to configure, detect, and manage a!arm conditions and system e$ents anywhere in manufacturing operations and a!ong the supp!y chain. -hi!e OA<a!arms is an integra! part of OAenterprise, its user interface components can be used either in OA<$iew or any standard Acti$e3 container. OA<history ' 4ro$ides process data storage, retrie$a!, and presentation ser$ices to gi$e operators, engineers, and managers a way of $iewing current, recent, and past operationa! detai!s as a function of time. %ike OA<a!arms, OA<history ser$ices are integrated with the OAenterprise mode! and its user interface components can be used in OA<$iew and any other standard Acti$e3 container.

http344www#oa#com

iv

OA<inform ' 4ro$ides *&0%'based information management by !inking a $ariety of !oca!, Intranet' or Internet'based documents, such as operating procedures and maintenance instructions, to OAenterprise c!asses and objects. OA<inform inc!udes a pre'configured set of *&0% pages that pro$ide detai!ed information about c!asses, objects, groups, and ce!!s. OA<webAccess ' 4ro$ides access to and interaction with OAenterprise so!utions through an internet connection. OA<webAccess pro$ides secure access to OAenterprise resources using standard web'based protoco!s. &he OA<webAccess components use *&&4 and 30% to e(tend the reach of the OAenterprise ce!! to the Internet.

)o!!ecti$e!y, OAenterprise pro$ides the core features re9uired for any monitoring and contro! systemH rea!'time data ac9uisition, contro!, $isua!i:ation, histori:ation, and a!arm detection and management. -ith OAenterprise you can create your own +nterprise'wide )ontro! conso!eLintegrating mission critica! systems and a!!owing your users to proacti$e!y effect change based on business opportunities.

http344www#oa#com

About this Guide

&his guide is di$ided into two chapters and one appendi(. )hapter ; is a "9uick start" road map to insta!!ing OAenterprise. )hapter < gi$es you more in'depth information about configuration, insta!!ation, and !icensing. &he appendi( contains system configuration recommendations.

About the Tutorial

A 9uick start guide to using OAenterprise, ca!!ed &$-start, is inc!uded with OAenterprise in e!ectronic format as a 0icrosoft -ord document. &he &$-start#doc 0# -ord fi!e is !ocated in the C35/rogram +iles5&$5&$-help fo!der (or the !ocation where you insta!!ed OAenterprise).

Document Conventions
&his document uses the fo!!owing typographic con$entions.
Example of Convention Description

6a$a 7irtua! 0achine (670)

)&.%, &A5

Acronyms are spe!!ed out the first time they are used. #ma!! capita! !etters are used for key names, key combinations, and key se9uences. A p!us sign (M) between key names indicates a combination of keystrokes. In this case, you ho!d down the )&.% key whi!e pressing the A%& and D+% keys. In procedures, the fo!!owing appear in bo!d !ettersH

)&.%MA%&MD+%

+ile menu &6 /roperties dia!og bo(

menu names commands on menus and buttons dia!og bo( tit!es and options
NOTE In supplemental text, menu names, dialog boxes, and other user interface elements will appear capitalized, but not in bold letters.

&ype Tan

In procedures, ita!ic bo!d !etters indicate

http344www#oa#com

vi

Example of Convention

Description

information that you type in e(act!y as shown. &ype your password In procedures, ita!ic !etters indicate p!aceho!ders for information you supp!y. Ita!ic !etters a!so are used occasiona!!y for emphasis. In te(t, ita!ic !etters indicate the introduction of a new term. 5oth upper and !ower case !etters are used in paths and fi!enames.

Attributes

NOANoaj

TIP In general, to complete a procedure quickly, follow the items that appear in boldface.

http344www#oa#com

vii

Related Documentation
OAenterprise inc!udes a number of documentation too!s designed to he!p you !earn and use the product. +$erything that there is to know about using OAenterprise is a$ai!ab!e in the documentation set that was insta!!ed with the product and that you can $iew whi!e you are working in OAworkbenchF. &he OAenterprise Documentation #et inc!udesH Readme 7 &he .eadme fi!e !ists any changes to the OAenterprise documentation since the pub!ication date. It can be found at the root directory of the compact disc and in the 5&$ fo!der after you insta!! the product. )heck this fi!e for any new information, !efore insta!!ing OAenterprise. &$enterprise Li!rary 7 Inc!udes a!! of the "ser and .eference 2uides that are a$ai!ab!e for OAenterprise. &he !ibrary is accessib!e from the 8elp menu, the OAenterprise 4rogram 2roup (c!ick &$-documentation), and the &$-help window within OAworkbench. &he "ser 2uides e(p!ain de$e!opment concepts and techni9ues, especia!!y for bui!ding and integrating app!ications into OAworkbenchH &$-start %uide 7 &his 9uick start guide inc!udes basic setup and insta!!ation instructions and a tutoria! broken into separate !essons to fami!iari:e you with the process of creating an app!ication and using features in OAenterprise. OA printed $ersion of this guide shipped with the OAenterprise compact disc.P &$enterprise User9s %uide 7 &his guide describes configuration and de$e!opment techni9ues, as we!! as an in'depth !ook at OAworkbench, OA<browse, OA<he!p, OApackager, and OA<inform. It a!so e(p!ains the concepts that you shou!d understand before setting up your OAenterprise en$ironment and creating an OAenterprise app!ication. $dditional User %uides Q Depending on the products purchased, you may ha$e additiona! user guides a$ai!ab!e to youLsuch as the OA<contro! "serKs 2uide, OA<a!arms "serKs 2uide, OA<history "serKs 2uide, OA<$iew "serKs 2uide, and so forth. &hese guides inc!ude setup, concepts, and de$e!opment techni9ues for the particu!ar product. &he .eference 2uides inc!ude programmerKs references, definitions of OA<contro! snippets, function !ibraries, and function b!ocks, as we!! as detai!ed information about the OAenterprise automation objects, and so forth. 8elp 7 4ro$ides 9uick answers to 9uestions that occur whi!e using OAenterprise. *e!p topics are a$ai!ab!e from the 8elp menu, by pressing ,;, or by c!icking the 8elp button found on many of the dia!og bo(es.
NOTE To use the online documentation, you should be familiar with using a mouse, opening a menu, and choosing menu and dialog box options.

http344www#oa#com

viii

About ObjectAutomation
ObjectAutomationF, Inc. (OA) is a #outhern )a!ifornia'based )orporation specia!i:ing in !eading edge industria! automation, contro!, and operationa! inte!!igence software. OA techno!ogies and products encapsu!ate e(isting p!ant e9uipment such as sensors and actuators, the !atest -indows +mbedded contro!!ers, 4rogrammab!e %ogic )ontro!!ers (4%)s), Distributed )ontro! #ystems (D)#s), 4)s, machines, work ce!!s, and other p!ant systems. OA too!s encourage users to embrace !egacy systems by wrapping them in app!ication component containers. -hen p!anning for the future, users now ha$e the choice of uti!i:ing e(isting assets whi!e !e$eraging new techno!ogies and adopting future products in a rea!'time p!atform for industria! automation, contro!, and operationa! inte!!igence. OAKs primary product suite, the OAenterprise, uti!i:es an open, mu!ti'tier contro! architecture based on 0icrosoft -indows . &he OAenterprise foundation is a distributed object management too! ca!!ed the OAframework, which e(tends -indows <???, 34 4rofessiona!, 34 +mbedded, #er$er <??@, and )O0M mode!s for manufacturing automation app!ications. A simp!e, intuiti$e "ser +n$ironment ("I) ca!!ed the OAworkbench, based on Acti$e Document techno!ogy, sits on top of the OAframework, pro$iding a common de$e!opment and runtime host for the app!ications in the OAenterprise suite. A!! of the products in the OAenterprise suite share common faci!ities to increase performance and interaction between modu!es. OA<contro! adds inte!!igence to operations by turning raw data in to key performance indicators (84I), by running optimi:ation a!gorithms, and by contro!!ing components, machines, work ce!!s, or entire process !ines. OA<$iew pro$ides *uman 0achine Interface (*0I) capabi!ities and a!!ows users to interact with any process using intuiti$e graphics and can$ases. OA<history is a comprehensi$e distributed storage and retrie$a! system. OA<a!arms rounds out the suite with a sophisticated, f!e(ib!e too! for hand!ing simp!e, comp!e(, or hierarchica! a!arm scenarios. OA<webAccess e(tends the reach and power of OAenterprise to the Internet by pro$iding access to app!ication data through an Internet connection. Adding the OA<webAccess too! to OAenterprise means authori:ed users can secure!y access and interact with a!! OAenterprise ce!! resources using standard web'based protoco!s, such as *&&4 and 30%.
Corporate 8ead0uarters

Address

ObjectAutomation, Inc. ;@>?? A!ton 4arkway #uite ;=A';A@ Ir$ine, )A C<D;B ".#.A.

&e!ephone Office *ours +'mai! Internet

M; (B>>) D<<'<BCC 0onday through ,riday BH?? A.0. ' =H?? 4.0. 4acific #tandard &ime supportRoa.com httpH www.oa.com

http344www#oa#com

i(

Accessing the ObjectAutomation Web Site

&he ObjectAutomation web site pro$ides additiona! information about OAenterprise and ObjectAutomation.
To access the &!'ect$utomation we! site

In your Internet browser, type the ObjectAutomation -or!d -ide -eb addressH httpH www.oa.com
TIP You also can access the Web site when you are working in the OAworkbench. n the Help menu, point to ObjectAutomation on the Web, and then select from options, such as Downloads, Online Support, and so forth.

http344www#oa#com

Contacting the Customer Satisfaction Team

,or genera! support 9uestions, contact our )ustomer #atisfaction &eam. "nternet Support +'mai!H supportRoa.com -eb addressH httpH www.oa.com Telephone Support &o!! ,ree for "# and )anadaH M; (B>>) D<<'<BCC +uropeH M@; AC> @B@B;B It wou!d be he!pfu! if you ha$e the fo!!owing information a$ai!ab!eH 1our customer ID /umber. &his number was e'mai!ed or fa(ed to your designated insta!!ation contact at the time of purchase. 1ou a!so can find this by opening &$wor !ench and, on the 8elp menu, se!ecting $!out. &he OAenterprise product $ersion number. 1ou can find this by opening &$wor !ench and, on the 8elp menu, se!ecting $!out. A prob!em description (e(act wording of screen messages or error numbers). A description of what you were trying to do when the prob!em occurred and how you tried to so!$e the prob!em. &he memory status at the time of the error (if app!icab!e). &his information is found in the -indows &ask 0anager uti!ity on the /erformance tab. &he -indows +$ent 7iewer !og. &he -indows #ystem Information fi!e.
:anager

To open the Windows Tas 1

On a b!ank area of the taskbar, right'c!ick. On the shortcut menu, c!ick Tas :anager.

To open the Windows ,vent ;iewer log file

On your desktop, c!ick the Start button, point to /rograms, point to &$enterprise, and then c!ick ,vent ;iewer. Do one of the fo!!owingH #a$e the !ogs as +$ent %og fi!es (with .+7& e(tension) and attach the fi!es to an e'mai!. #a$e the !ogs as &e(t fi!es (with .&3& e(tension), print the fi!es, and fa( them.

To create a System "nformation +ile

On your desktop, c!ick the Start button, point to /rograms, point to $ccessories, point to System Tools, and then c!ick System "nformation. &he #ystem Information window appears. In the System "nformation window, on the $ction menu, c!ick Save $s System "nformation. &his creates a fi!e with the e(tension "nfo" (S.nfo).

http344www#oa#com

(i

#end the #ystem Information ,i!e (S.nfo) to supportRoa.com.

TIP If you do not ha!e an Internet connection, you can print the file to fax. In the S stem In!ormation window, right"click S stem In!ormation, and then click Print.

http344www#oa#com

Chapter 1 Quick Start Installation in our Eas! Steps

&his chapter out!ines in four easy steps how to insta!! OAenterprise. ,or more detai!s and step'by'step procedures, refer to )hapter <.

1 - Check Your Hardware/Software Configuration

OAenterprise wi!! effecti$e!y insta!! and run on any 4) running one of the fo!!owing operating systemsH -indows <???, -indows 34 or -indows #er$er <??? and <??@. &he optimum configuration is a function of the e$entua! OAenterprise app!ication !oad that wi!! run on any gi$en machine.

2 ' Install OAenterprise

Single Computer .un the setup program and choose the Stand7alone Node configuration option. etworked Computers .un the setup program and choose either the Cell :anager or the Cell Client configuration option. 2i$en the insta!!ation options for a distributed system, we high!y recommend that you fami!iari:e yourse!f with these, before insta!!ing a distributed system.
"A#TION If you are upgrading to #enterprise, make sure you check the $EAD%E&T'T file located at the root of the compact disc for important steps to take be!ore upgrading. TIP If you installed the trial license during installation, you may run the product for $% days before you must complete the licensing procedure, outlined in steps &"'.

http344www#oa#com

! - O"tain the OAenterprise #icense Collection $ile

'ia (mail or )hone +mai! or te!ephone your 8ost Name, 8ost Code, Customer "D Num!er, /assword, contact name and current address to the )ustomer #atisfaction &eam. +mai!H supportRoa.com 4honeH M; (B>>) D<<'<BCC (&o!! ,ree for "#, )anada) 1our !icense co!!ection fi!e(s) wi!! be mai!ed to you.

% - Install Your #icense Collection $ile on the Host ode

-hen you recei$e your !icense co!!ection fi!e, copy it to the C35/rogram +iles5&$5License fo!der (or the !ocation where you insta!!ed the ObjectAutomation software), on the %icense *ost node. If necessary, de!ete the install#tmp temporary !icense fi!e from the 5License fo!der. #hut down and then restart OAframework ser$ices on the %icense *ost node and a!! associated ce!! nodes.

Congratulations&
1ou are now ready to start OAenterprise. On your desktop, doub!e'c!ick the OAworkbench icon. ,or a 9uick introduction to OAenterprise, see the &$-start tutoria!. #ee "About the &utoria!" for information about accessing the tutoria!.

http344www#oa#com

Chapter 2 Settin" #p an OAenterprise Installation

&his chapter co$ers the things you shou!d consider before insta!!ing OAenterprise, the insta!!ation re9uirements and recommendations, the insta!!ation procedure, and the !icensing procedure.
TIP If you ha!e not seen it already, please check (hapter $ )*uick +tart Installation in ,our -asy +teps.)

"lanning the Installation

OAenterprise is a $ery powerfu! program that co$ers the spectrum from simp!e stand' a!one *0I to fu!!y distributed contro!. It can run e9ua!!y we!! on either a sing!e computer or a group of networked computers (a mu!ti'node distributed OAenterprise ce!!). &his sca!abi!ity a!!ows you to create a sma!!, sing!e'computer contro! system and then e(pand it as your needs change. .egard!ess of which configuration you choose (stand'a!one or distributed), e$erything begins with insta!!ation, and, whi!e the simp!est insta!!ations can be done without much forethought, it is important to consider the !ayout or topo!ogy of your system for !arger, distributed systems. &his section pro$ides an o$er$iew of the two OAenterprise configurations and of the things to consider when designing an OAenterprise distributed system.

$unnin" OAenterprise as a Stan%&alone 'o%e

&he OAenterprise stand'a!one system (referred to as a stand'a!one node) is a se!f' sufficient workstation that contains a!! of the ser$ices necessary to run OAenterprise. It does not need to be part of a network and wi!! not be ab!e to share OAenterprise resources with other OAenterprise systems. &he stand'a!one node norma!!y is insta!!ed on a standard -indows <??? workstation but can be insta!!ed on a -indows <??? <??@ #er$er. 34 4rofessiona!

&he setup program a!ways gi$es you the option of configuring a workstation as a stand' a!one node. ,or more detai!s, see "Insta!!ing OAenterpriseT.
TIP While it is possible to later upgrade an #enterprise system configured as a stand"alone node to a distributed #enterprise cell, it is not as easy a process as expanding a single" node #enterprise cell to multiple nodes. If you will be expanding in the future, it is recommended that you select the (ell .anager option during installation rather than the +tand"alone /ode option. 0efer to the )0unning #enterprise as a 1istributed +ystem) section, for more information.

$unnin" OAenterprise as a Distribute% S!stem

OAenterprise may be run on a sing!e computer using a !oca! database (a stand'a!one node) or on se$era! networked computers using shared, distributed databases (an OAenterprise ce!!). An OAenterprise ce!! is a distributed system that pro$ides the abi!ity to

http344www#oa#com

<

distribute app!ication components (objects) transparent!y across a network of processors. &o the end'user, howe$er, it !ooks !ike a sing!e app!ication. &o setup a distributed OAenterprise ce!!, the machines in$o!$ed shou!d be in the same domain. (Other situations can be accommodated but are beyond the scope of this discussion. If you ha$e mu!tip!e domains, workgroups or simi!ar situations, p!ease contact OA customer support.)

*nderstanding the OAenterprise Cell

An OAenterprise ce!! is a group of computers (referred to as nodes or ce!! members) that share a common set of OAenterprise resources. .esources inc!ude c!asses, objects, can$ases, contro! worksheets, and so forth. .esources can be distributed among the nodes of a ce!!, and each member of a ce!! can access a resource without regard to its physica! !ocation. &his means that you can grow your contro! system simp!y by adding a new node to a ce!! and mo$ing resources onto it. &he addition of a new node affords your system the additiona! computing power and storage space of that machine Q as we!! as another disp!ay screen. After adding a new node, you can mo$e contro! engines, history $au!ts, objects, and so forth, to that new resource. At the minimum, an OAenterprise ce!! consists of one ce!! manager node and usua!!y Q but doesnJt necessari!y ' one ce!! c!ient node. Assuming the appropriate !icensing is in p!ace, e$ery node within the same ce!! has the potentia! to de$e!op, maintain, modify and monitor an app!ication. And, as a!!uded to ear!ier, objects can be mo$ed easi!y from one node within a ce!! to another node to ba!ance the processing !oad and increase efficiency. 1ou can run mu!tip!e OAenterprise ce!!s within a sing!e 0icrosoft -indows domain or across mu!tip!e domains. 5ecause each ce!! has its own ce!! manager, the ce!! c!ient nodes in one ce!! are not affected, if nodes in another ce!! fai! or are shutdown. ,or the most part, ce!!s can be administered independent!y and can be started, stopped, or upgraded without impacting other ce!!s. If you insta!! mu!tip!e OAenterprise ce!!s, it is possib!e for objects in one ce!! to communicate with the objects in another ce!!. &his is referred to as cross'ce!! communication and is true whether the ce!!s are !ocated within the same -indows domain or across domains. )ross'ce!! communication inc!udes reading data from, writing data to, and registering with the attributes of, objects in remote ce!!s.

Configuring an OAenterprise Cell

&he setup program insta!!s OAenterprise on your workstation. During the insta!!ation, the setup program prompts you to choose how to configure the node. 1ou can choose from three optionsH
1 !

)e!! 0anager )e!! )!ient #tand'a!one /ode

&he first two are re!ated to setting up a distributed system, known as an OAenterprise )e!!, and the third one is for a se!f'contained, stand'a!one system. &his section addresses the first two options. (hat is a Cell )ana"er*

http344www#oa#com

An OAenterprise )e!! 0anager is the host for an OAenterprise ce!!. &he ce!! manager has OAworkbench and a!! products insta!!ed on it and pro$ides the core OAframework ser$ices for the ce!!. &he ce!! manager is responsib!e for maintaining c!ass definitions, a ce!!'wide object directory, and other centra!i:ed information. It a!so is responsib!e for tracking the status of the other members of the ce!!. In a!! other respects, though, the ce!! manager node functions as any other c!ient node Q it can be used to host objects, $iew graphics, and so forth. +he r e is the "e s t pla ce to i ns tal l the Ce l l ,a na ge r A!though the members of a ce!! wi!! be ab!e to continue ongoing operations if the ce!! manager becomes una$ai!ab!e, they wi!! not be ab!e to !ocate additiona! objects on other nodes or start new objects. ,or this reason, the ce!! manager shou!d be insta!!ed on a high'a$ai!abi!ity machine running either -indows <??? 4rofessiona!, -indows <??? #er$er, -indows 34 4rofessiona! or -indows #er$er <??@. &he setup program gi$es you the option of configuring as a ce!! manager node when it detects your workstation is part of a -indows domain. ,or more detai!s, see "Insta!!ing OAenterprise". (hat is a Cell Client* An OAenterprise ce!! c!ient runs as a node in an OAenterprise ce!!. OAworkbench and a!! products are insta!!ed on it. &he ce!! c!ient participates with other ce!! c!ients and the ce!! manager to share OAenterprise resources and data. A!! of the nodes in a ce!! access a common set of c!asses, objects, can$ases, graphics, and so forth.

http344www#oa#com

+he r e is the "e s t pla ce to i ns tal l a Ce l l Cl i e nt&he ce!! c!ient norma!!y is insta!!ed on a standard -indows <??? 4rofessiona! workstation or -indows 34 4rofessiona!, but can be insta!!ed on a -indows <??? #er$er or -indows #er$er <??@. &he setup program gi$es you the option of configuring as a ce!! c!ient node when it detects the fo!!owing two conditionsH
1

1our workstation is part of a -indows domain. A ce!! manager e(ists in the domain.

Determinin" (hat to $un on an OAenterprise Cell 'o%e -hi!e the configuration types designate a node as either a )e!! 0anager or )e!! )!ient, it is important to rea!i:e that either type can support many ro!es within your app!ication, inc!udingH .unning a )ontro! +ngine and Objects *osting the *istory 7au!t and or .epository *osting the A!arm Area Acting as the I O source Disp!aying Operator #creens (*0I)

-hi!e the p!acement of a!! of these can be decided after the insta!!ation, it he!ps to p!an your system beforehand. A few common 9uestions might he!p you with the taskH +he r e is the "e s t pla ce to r un c ontr ol engi nes It is a good idea to run your contro! as near as possib!e to your I O ser$ers, therefore, it is recommended that you run your contro! engines and store your objects on the same nodes. O n w ha t node s shoul d the H,I sc re e ns r unDepending on the type of animation taking p!ace in these screens, this cou!d be a )4"' intensi$e operation. #uch operations are not desirab!e on a node that is running critica! processes. If a node is going to be used primari!y for operator $iewing, consider running the contro! engines on a different node in the ce!!. +ha t s houl d I do. i f re s ponse ti m e de te r i ora te s If you notice that the user'interface response time is deteriorating or )4" !oad is peaking, consider the fo!!owingH 0o$ing a!! screen processing (*0I and )ontro!7iew) to a node that is not running contro!. 4utting contro! on a dedicated node where the primary task is running contro!. 0o$ing history processing by mo$ing the history $au!ts to a separate node(s).

&here are few re9uirements regarding where system components can reside. In fact, as !ong as you respect the c!ose re!ationship that I O connecti$ity, contro!, and objects ha$e, you are ab!e to mo$e objects to any node.

http344www#oa#com

>

1ou can measure )4" uti!i:ation with the -indows &ask 0anager. 1ou a!so can use the )omputer#ummary c!ass to bui!d this monitoring capabi!ity into your *0I screens. ,or more information about using the )omputer#ummary c!ass, p!ease refer to "&he )omputer#ummary App!ication" topic in the on!ine &$enterprise User9s guide.

http344www#oa#com

Installation Re#uirements
5efore you insta!! OAenterprise, make sure thatH
1 !

1ou check the .+AD0+ fi!e for any changes regarding insta!!ation. 1our computer meets the system re9uirements. 1ou are !ogged on as member of the !oca! computers Administrator group so that the OAenterprise ser$ices can be registered on the computer.

Checkin" the $EAD)E ile

&he .+AD0+.&3& fi!e contains !ast minute changes to the OAenterprise documentation since its pub!ication and can contain the !atest instructions for the setup program.
To open the R,$D:, file

In Windows ,(plorer, na$igate to the root directory of the &$enterprise compact disc, and then doub!e'c!ick readme. )heck the first section of the fi!e for any new information about insta!!ing OAenterprise. After insta!!ing OAenterprise, the .+AD0+ fi!e a!so is a$ai!ab!e in the C35/rogram +iles5 &$ fo!der (or the !ocation where you insta!!ed the ObjectAutomation software).

Checkin" S!stem $e+uirements

5efore insta!!ing OAenterprise, $erify that each workstation meets the minimum hardware and software re9uirements re9uired to support OAenterprise.

Hardware /e0uirements
OAenterprise wi!! insta!! and run on any modern 4) p!atform inc!uding !aptops, desktops, User$ersT and sma!! form factor industria! 4)s. As a point of reference, OAenterprise was origina!!y designed and de$e!oped to run entire!y on 4entium ;DD 0*: machines with as !itt!e as DA 05 of .A0, #uper 72A graphics, and !ess than a ha!f gigabyte of disk spaceV #o, any machine on the market today Q with the possib!e e(ception of specia! purpose, !ow power de$ices with e(treme!y !imited hardware resources Q wi!! run OAenterprise. Of course, certain app!ications may re9uire more disk space, fast graphics, more memory, faster )4"sW this is a system architecture design prob!em and is, therefore, beyond the scope of this document. &his said, these considerations shou!d be $iewed as the e(ception and not the ru!e, so for testing, e$a!uation, and e$en for most modest app!ication purposes, any modern machine wi!! do. (If you ha$e 9uestions about your configuration, p!ease contact the )ustomer #atisfaction &eam.)

Software /e0uirements
OAenterprise wi!! insta!! and run proper!y on any (combination, in the case of a distributed, mu!ti'node ce!!) of the fo!!owing -indows operating system $ersionsH 0icrosoft -indows <??? #4< or !ater 0icrosoft -indows <??@ #er$er #4; or !ater 0icrosoft -indows 34 #4<

http344www#oa#com

&he fo!!owing software a!so is re9uired, and, if not detected, is insta!!ed as part of OAenterprise. 0#7).&.D%% 0icrosoft #D8 for 6a$a A.? 0icrosoft 6a$a 7irtua! 0achine

OAenterprise #ser Account

-hen running OAenterprise as a distributed system, it is necessary to ha$e a domain' !e$e! user account a$ai!ab!e for OAenterprise use. &his is the account OAenterprise uses to run its ser$ices, and it shou!d be a Domain User as we!! as a Local $dministrator on a!! nodes in the OAenterprise ce!!. During insta!!ation, when configuring a ce!! manager, you wi!! be prompted for this account user name and password. #ince a!! nodes in a gi$en ce!! shou!d use the same account to run their ser$ices, it is recommended that you create an OAenterprise'specific domain account ca!!ed OA#1#&+0 that can be used for a!! nodes.
TIP You can use the same user account for multiple cell managers in a single domain.

NOTE You also will need to make sure that the node that will manage licensing has a default administrator account with the user name )#dministrator.) This account is created, by default, when Windows is installed. 1o not remo!e or rename this account. 2You may, howe!er, change the administrator password to conform to your site3s security guidelines.4

,or more information about creating user accounts, p!ease refer to the 0icrosoft -indows documentation.

http344www#oa#com

)@

Ol%er ,ersion of OAenterprise Installe%*

If you are upgrading OAenterprise, make sure you (;) back up your e(isting OAframework database or package your app!ication c!asses, objects, worksheets, can$ases, and graphic !ibraries and (<) check the R,$D:,#TAT fi!e !ocated at the root of the compact disc for important steps to take !efore upgrading. ,or more information about backing up your e(isting OAframework database, and packaging your app!ication, respecti$e!y, p!ease refer to the on!ine documentation as referenced be!ow. S ee $lso "#ystem Administration" in the on!ine &$enterprise User9s %uide "%esson ,i$e Q 4ackaging the App!ication," in )hapter @ of the &$-start tutoria! If you are not insta!!ing OAenterprise and wou!d !ike to remo$e OAenterprise manua!!y, refer to the ".emo$ing OAenterprise" in the #ystem Administration chapter in the on!ine &$enterprise User9s %uide.

*pgrading an OAenterprise Cell

5efore starting the setup program to upgrade, shut down OAenterprise (inc!uding OAworkbench and a!! OA ser$ices) on a!! ce!! c!ient nodes and then on the ce!! manager node. .un the setup program on the ce!! manager node first, and then run it on each ce!! c!ient node.
"A#TION It is highly recommended that you upgrade all nodes in the target cell5 whereas #enterprise may function in an en!ironment that has mixed !ersions, it is not a supported configuration.

+hat Happens to Your (1isting OAenterprise #icense $ile after *pgradingIf you are upgrading from any pre$ious $ersion of OAenterprise, you need a new !icense fi!e. After the insta!!ation process is finished, you must regenerate the OAkey and obtain a new !icense co!!ection fi!e from ObjectAutomation, before you can run OAenterprise.

http344www#oa#com

))

'otes about #p"ra%in" the Operatin" S!stem

If you ha$e -indows /& insta!!ed, you must upgrade your operating system to -indows <???, 34 or #er$er <??@ before insta!!ing OAenterprise. It is not necessary to remo$e current $ersions of OAenterprise before upgrading the operating system. A!though pre$ious $ersions of OAenterprise do not run on -indows <???, 34, or #er$er <??@, the databases wi!! remain intact through the operating system upgrade process. (-e do recommend that you back up your data before upgrading your operating system.)

http344www#oa#com

)-

Installing OAenter$rise
&he setup program insta!!s OAenterprise on your computer. #pecifica!!y, it insta!!s the OAenterprise program fi!es, the on!ine *e!p system, the OAenterprise documentation !ibrary, prepackaged graphics that you can use in OA<$iew can$ases, function b!ocks that you can use in your contro! methods, e(amp!e app!ications, and other product components from the )D'.O0 to your hard disk. 1ou must use the setup program to insta!! OAenterprise, because it decompresses and insta!!s fi!es in specific directories. 1ou cannot simp!y copy fi!es from the )D'.O0 to your hard disk to run OAenterprise.
"A#TION If you are running in a cell en!ironment, remember to run the setup program on the cell manager node !irst, and then run it on each cell client node. #enterprise does not support en!ironments with mixed #enterprise !ersions. If you are upgrading #enterprise, make sure that you 2$4 back up your existing #framework database or package your application classes, ob6ects, worksheets, can!ases and graphic libraries, and 274 check the $EAD%E&T'T file located at the root of the compact disc for additional steps to be taken be!ore upgrading.

To initiate the setup program 1

%og on to your workstation with a domain account that is a member of the !oca! workstationKs Administrator group so that the OAenterprise ser$ices can be registered on the workstation. If you ha$e any -indows'based programs (inc!uding a screen sa$er) running, c!ose them, before continuing.

Do one of the fo!!owingH If you are insta!!ing OAenterprise from a !oca! )D'.O0 dri$e, then insert the compact disc in the )D'.O0 dri$e. If you are insta!!ing OAenterprise from a network share, then map the network dri$e to a dri$e !etter.

Do one of the fo!!owingH If the &$enterprise Welcomes BouC window automatica!!y opens when you insert the compact disc, continue with step =. If Auto4!ay is not enab!ed or if you are insta!!ing from a network share, then in Windows ,(plorer, na$igate to the root directory of the OAenterprise compact disc, and c!ick &$Splash. &his opens the &$enterprise Welcomes BouC window.

http344www#oa#com

).

&

In the &$enterprise Welcomes BouC window, c!ick &$-install.

O A e n t e r p r i s e W e l c o m e s Yo u ! w i n d o w

'

&he setup program prompts you through the insta!!ation process. ,o!!ow the onscreen instructions.
TIP To find out more about options during setup and installation, click the Help button a!ailable on many dialog boxes.

NOTE #enterprise requires that certain software be installed on the node, prior to installing #enterprise. -ach of these is a!ailable from the #enterprise compact disc, and, if any are not detected, the appropriate installation program2s4 will be launched by the #enterprise installation. ,ollow the onscreen instructions for each, including the instruction to reboot your computer.

http344www#oa#com

)<

To install a stand7alone node 1

In the &$framewor Configuration dia!og bo(, c!ick Stand7alone Node.

Stand-alone Node OAframe wo rk Configuration option

-hen the first part of the insta!!ation is finished, you wi!! be prompted to restart your workstation to comp!ete the insta!!ation. )!ick +inish to c!ose the dia!og bo(, and restart your workstation.
!

After the second part of the insta!!ation process is comp!ete, the &$enterprise "nstallation is complete message appears.

Insta!!ation is finished and you are ready to proceed with !icensing your software.
TIP If you installed the trial license during the installation procedure, you may run the product for $% days, before you must complete the licensing procedure and obtain a registered license.

http344www#oa#com

)=

To install a distri!uted &$enterprise system 1

In the &$framewor Configuration dia!og bo(, c!ick the option corresponding to the distributed ce!! node you are configuring.

Cell

anager node OAframe work configuration option

-hen the first part of the insta!!ation is finished, you wi!! be prompted to restart your workstation to comp!ete the insta!!ation. )!ick +inish to c!ose the dia!og bo( and restart your workstation.
! %

If you are insta!!ing a ce!! c!ient, the Select the cell to 'oin dia!og bo( appears. )!ick the ce!! you want to join, and then, c!ick &6. After the second part of the insta!!ation process is comp!ete, the &$enterprise "nstallation is complete message appears.

Insta!!ation is finished and you are ready to proceed with !icensing your software.
TIP If you installed the trial license during the installation procedure, you may run the product for $% days, before you must complete the licensing procedure and obtain a registered license.

http344www#oa#com

)2

(icensing OAenter$rise
If you insta!!ed the tria! !icense during the OAenterprise insta!!ation procedure, you may run the product for ;A days, before obtaining a registered !icense from ObjectAutomation. -hen you are ready to obtain a registered !icense, fo!!ow the procedure re!e$ant to your system en$ironmentH a #tand'a!one /ode or an OAenterprise )e!! (mu!ti'node ce!!). &o !icense OAenterprise, you must generate an OAkey on, and insta!! a !icense co!!ection fi!e to, the &$5License fo!der on each stand'a!one node and on (at !east) one node within an OAenterprise distributed ce!!.
To license &$enterprise for a stand7alone node environment 1 ! % &

2enerate an OAkey on the node. #end the OAkey information to ObjectAutomation to obtain a !icense co!!ection fi!e. Insta!! the !icense fi!e. #hut down, and then, restart the OAframework ser$ices on the %icense *ost node and a!! associated ce!! nodes. .epeat steps ;'A for each stand'a!one node.

To license &$enterprise for a distri!uted cell environment 1

Decide on which node you want to run the !icense co!!ection fi!e. &his is known as the %icense *ost node.
NOTE You may want to designate more than one 8icense 9ost node. If you do, then you will follow this procedure for each 8icense 9ost node.

2enerate an OAkey on the designated %icense *ost node.

! % &

#end the OAkey information to ObjectAutomation to obtain a !icense co!!ection fi!e. Insta!! the !icense fi!e. #hut down, and then, restart the OAframework ser$ices on the %icense *ost node and a!! associated ce!! nodes.

http344www#oa#com

)>

Important 'otes about -icensin"

0ake sure that the node(s) that wi!! manage !icensing has a defau!t administrator account with the user name "Administrator." &his account is created, by defau!t, when -indows is insta!!ed. Do not remo$e or rename this account. 1ou may, howe$er, change the administrator password to conform to your siteKs security guide!ines. )hanging the name of the node in$a!idates your !icense fi!e. 1ou wi!! not be ab!e to run OAenterprise on the node, and other OAenterprise nodes in the OAenterprise ce!! wi!! not be ab!e to access any objects on the node after the name change. ,or more information, refer to ".enaming a /ode After Insta!!ing OAenterprise" in the on!ine &$enterprise User9s %uide. Insta!!ing OAenterprise =.A o$er OAenterprise =.@ (or ear!ier) in$a!idates your e(isting OAenterprise !icense fi!e. 2enerate a new OAkey and contact ObjectAutomation for a new !icense co!!ection fi!e. .einsta!!ing -indows on the %icense *ost node, after running OAenterprise, in$a!idates your !icense fi!e. 2enerate a new OAkey and contact ObjectAutomation for a new !icense co!!ection fi!e. 1ou can use the %icense 7iewer to $iew and $erify information about a!! of the !icenses a$ai!ab!e in an OAenterprise system and print !icense reports. It gathers information from a!! %icense 0anagers running in a gi$en OAenterprise ce!!W co!!ates the informationW and disp!ays it in a tabu!ar format. ,or more information about using the %icense 7iewer, refer to "-orking with the %icense 7iewer" in the on!ine &$enterprise User9s %uide.

http344www#oa#com

)1

.eneratin" an OAke!
&he OAkey is the *ost /ame and *ost )ode of the node that wi!! manage the OAenterprise !icensing.

If 2ou are running one 3or more4 Stand-alone ode3s4

+ach stand'a!one node manages its own !icenses. 1ou wi!! generate an OAkey on each stand'a!one node.

If 2ou are running an OAenterprise distri"uted cell

5ecause the OAenterprise %icense 0anager (OA %icense 0anager) is insta!!ed automatica!!y on e$ery node on which OAenterprise is insta!!ed, you can designate which node in the ce!! you want to manage the OAenterprise !icensing. &his node is referred to as the %icense *ost node. 1ou wi!! generate an OAkey on the %icense *ost node. If you want to ha$e more than one %icense *ost node in a ce!!, generate an OAkey on each one of those designated %icense *ost nodes. /o0 %o I %eci%e 0hich no%e I 0ant to mana"e licensin"* Any node can manage the OAenterprise !icenses. *owe$er, keep in mind that if the %icense *ost node is shutdown or otherwise stops running or communicating with the network, nodes that try to obtain a !icense (after the communication !oss), wi!! be unab!e to do so.
"A#TION #fter running #enterprise, renaming the 8icense 9ost node in!alidates your license file. You will not be able to run #enterprise on the node, and other #enterprise nodes in the #framework cell will not be able to access any ob6ects on the node after the name change. Your license file also will be in!alidated, if, after running #enterprise, you reinstall Windows 7::: on the 8icense 9ost node. In either case, you must regenerate the #key on that node and contact b6ect#utomation for a new license collection file.

To generate an &$ ey

.epeat this procedure on each stand'a!one node and on at !east one node in each OAenterprise ce!!.
1

On the desktop of the node that you want to manage OAenterprise !icensing (the %icense *ost node), c!ick the Start button, point to /rograms, and then, point to &$enterprise.

http344www#oa#com

)?

On the &$enterprise program group menu, c!ick &$configure. &he OAframework #ystem )onfiguration dia!og bo( appears.

OAframe wo rk S!stem Configuration dialog "o #

)!ick &$ ey. &his generates the OAkey information needed to obtain your !icense fi!e from

OAke! dialog "o#

ObjectAutomation. &he &$ ey dia!og bo( appears disp!aying the 8ost Name and 8ost Code for this node.
% &

)opy the 8ost Name and 8ost Code into a te(t fi!e using /otepad or any other te(t editor. )!ose the &$ ey dia!og bo(, and then c!ick &6 to c!ose &$configure.

http344www#oa#com

-@

Obtainin" a -icense 1CO-2 ile

&he ne(t step is to send your OAkey to ObjectAutomation to obtain your !icense co!!ection fi!eH

To o!tain your license collection file through email or phone 1

+mai! or te!ephone the 8ost Name, 8ost Code, your 17digit Customer "D Num!er, /assword, Contact Name and Current $ddress to the )ustomer #atisfaction &eam. ,mail3 !icenseRoa.com /hone3 M; (B>>) D<<'<BCC (&o!! ,ree for "# and )anada)W M@; AC> @B@B;B (+urope) 1our )ustomer ID /umber and 4assword were e'mai!ed or fa(ed to your designated Insta!!ation )ontact at the time of purchase. &he )ustomer #atisfaction &eam wi!! mai! a f!oppy disk with the !icense co!!ection fi!e(s) to you.

After recei$ing the !icense fi!e (S.)O%), copy it to a safe backup area. (Do not rename the !icense fi!eW renaming the fi!e in$a!idates it.) It is recommended that you archi$e this backup fi!e. &he ne(t step is to insta!! the !icense co!!ection fi!e(s).

http344www#oa#com

-)

Installin" the -icense ile

&he ne(t step is to insta!! the !icense co!!ection fi!e(s) on the node(s).
To install the license collection file 1

-hen you recei$e the !icense fi!e(s), copy it to the C35/rogram +iles5&$5License fo!der (or to the !ocation where you insta!!ed the ObjectAutomation software) on the %icense *ost node. A!so, remember to make a backup of your !icense co!!ection fi!e and archi$e it. If a fi!e ca!!ed install#tmp e(ists in the NLicense fo!der, de!ete it. /ow, you wi!! shut down the OAframework ser$ices on the %icense *ost node and on a!! ce!! nodes that wi!! be using !icenses from this !icense co!!ection fi!e. (&his inc!udes any node from which you de!eted the install#tmp fi!e.) If this is a distributed ce!!, shut down ce!! c!ient nodes before ce!! manager nodes. On the des top, on the Tas !ar, right'c!ick the &$enterprise tray (OAtray) icon.

On the shortcut menu, c!ick Shutdown &$enterprise. In the confirmation dia!og bo(, c!ick Bes. &his shuts down a!! of the running objects and the OAframework ser$ices on the node. -hen the ser$ices are shutdown, the OAenterprise icon in the &askbar tray turns red.
% &

If this is a distributed ce!!, repeat step @ to continue shutting down OAframework ser$ices on nodes as re9uired. /ow, you can begin to restart the OAframework ser$ices. If this is a distributed ce!!, restart the ser$ices on ce!! manager nodes before ce!! c!ient nodes. On the des top, on the Tas !ar, right'c!ick the &$enterprise tray icon again. On the shortcut menu, c!ick Start &$enterprise. In the confirmation dia!og bo(, c!ick Bes. &his starts the OAframework ser$ices on the node. -hen the ser$ices are started, the OAenterprise icon in the &askbar tray turns green.

'

If this is a distributed ce!!, repeat step = to continue restarting OAframework ser$ices on nodes as re9uired.

Congratulations&
1ou are now ready to start OAenterpriseV On your desktop, doub!e'c!ick the OAworkbench icon. &he first time you start an OAenterprise app!ication that re9uires a !icenseLfor e(amp!e, &$wor !enchQ'the OA %icense 0anager !oads the !icense fi!e.
TIP You can use the 8icense ;iewer to !iew and !erify information about all of the licenses a!ailable in an #enterprise system and print license reports. It gathers information from all 8icense .anagers running in a gi!en #enterprise cell5 collates the information5 and displays it in a tabular format. To open the 8icense ;iewer, on any node in the #enterprise cell, open #configure 2from the Start menu, point to Pro(rams, point to OAenterprise, and then click OAcon!i(ure.4 In the OA!ramework S stem "on!i(uration dialog box, on the S stem tab, click )icense *iewer. ,or more information about using the 8icense ;iewer, refer to )Working with the 8icense ;iewer) in the online OAenterprise #ser+s ,uide.

http344www#oa#com