Deployment Files for PowerBuilder, InfoMaker, and the HTML - Sybase

Deployment Files for PowerBuilder, InfoMaker, and the Web DataWindowScenarioWeb application using WebDataWindow with PowerDynamoand MTSWeb application using WebDataWindow with ASP and MTSor IISWeb application using theDataWindow Web control forActiveXWeb application usingPowerBuilder plugins or thewindow ActiveXSee these sections"Files required on the MTS or IIS server" onpage 23"Files required on the PowerDynamo server" onpage 24"Files required on the MTS or IIS server" onpage 23"Files required on the ASP server" on page 24"DataWindow Web control for ActiveX" onpage 25"Plugins and PowerBuilder window ActiveXcontrols" on page 26Installed anddeployment pathsApp Path registry keyThe Installed path listed after some of the tables in this document is thelocation where files are installed when you install PowerBuilder or anotherEAStudio tool and select the default installation location. The Deployment pathtells you where those files can be copied to on the computer where you installyour application or component.Some tables are followed by a list of the Registry entries your installationprogram needs to make so that your application or component can find the filesit needs. When an application runs on Windows, it looks for supporting files inthese locations and in this order:1 The directory where the executable file is installed.2 The Windows system and Windows directories (on NT, inC:\WINNT\SYSTEM32, C:\WINNT\SYSTEM, and C:\WINNT).3 In an application path that can be specified in the registry.4 In the system path.You don’t need to specify an application path, but it is recommended.To specify the path the application uses to locate supporting files, yourinstallation program should create an App Path key for your application in thisregistry location:HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\App PathsLast updated November 23, 1999 3

Using this documentSet the data value of the (Default) string value to the directory where theapplication is installed and create a new string value called Path that specifiesthe location of shared files. The following example shows a typical registryentry for an application called MYAPP.EXE that uses Adaptive ServerAnywhere. The registry key is enclosed in square brackets and is followed bystring values for the key in the format "Name"="Value":[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\myapp.exe]"Default"="C:\Program Files\myapps\MYAPP.EXE""Path"="C:\Program Files\myapps;C:\Program Files\sybase\shared\PowerBuilder;c:\program files\sybase\Adaptive Server Anywhere 6.0\win32\;"About REG filesRegistry update files that have a .REG extension can be used to importinformation into the registry. The format used in registry key examples in thisdocument is similar to the format used in registry update files but theseexamples are not intended to be used as update files. The pathnames in datavalue strings in registry update files typically use a pair of backslashes insteadof a single backslash, and the "Default" string value is represented by the atsign (@).About filenamesTables in this document show the ANSI versions of filenames. Some otherversions of PowerBuilder have a letter at the end of the filename to distinguishamong versions. For example, if you are using a non-ANSI version ofPowerBuilder, your Sybase\Shared\PowerBuilder directory may contain fileswith names such as PBVM70M.DLL or PBVM70U.DLL instead ofPBVM70.DLL. When you deploy an application, deploy the samePowerBuilder DLLs with which you developed it.4 Last updated November 23, 1999

Deployment Files for PowerBuilder, InfoMaker, and the Web DataWindowPowerBuilder runtime filesDatabase connectivityFiles required for database connectivity are listed separately in "Databaseconnections" on page 6.The following table lists the core PowerBuilder runtime files. You only need toinstall the files that your application requires. For example, PBVM70.DLL isrequired for all deployed applications, but you need to install PBRTC70.DLLonly if your application uses Rich Text controls or RichText DataWindowobjects.NamePBVM70.DLLLIBJCC.DLLPBDWE70.DLLPBRTC70.DLLPBAEN70.TLBPBFNT70.INIPBLAB70.INIPBTRA70.DLLRequired forAllAllDataWindows and DataStoresRich TextOLE automation servers that use PowerBuilder.ApplicationMapping unavailable fontsLabel DataWindow presentation style predefined formatsDatabase connection tracingInstalled path C:\Program Files\Sybase\Shared\PowerBuilderDeployment path Same directory as the application, in a directory on thesystem path, or in the App Path registry key.Registry entries See "App Path registry key" on page 3.Last updated November 23, 1999 5

Deployment Files for PowerBuilder, InfoMaker, and the Web DataWindowNative database driversThe following table lists the native database drivers supplied withPowerBuilder. If an application or component uses the database specified, thefile is required on the computer. The first two characters of the native databasefilename are PB, the next three characters identify the database, and the lasttwo identify the version of PowerBuilder:NameRequired forPBIN770.DLL INFORMIX I-Net 7PBIN970.DLL INFORMIX I-Net 9PBMSS70.DLL Microsoft SQL Server 6 and 7PBO7370.DLL Oracle 7.3PBOR870.DLL Oracle 8.0PBO8470.DLL Oracle 8.0.4 and laterPBDIR70.DLL Sybase DirectConnectPBSYC70.DLL Sybase Adaptive Server Enterprise CT-LIBPBSYJ70.DLL Sybase Adaptive Server Enterprise CT-LIB for Jaguardeployment onlyInstalled pathC:\Program Files\Sybase\Shared\PowerBuilderDeployment path Same directory as the application, in a directory on thesystem path, or in the App Path registry key.Registry entries See "App Path registry key" on page 3.Notes When you deploy a PowerBuilder custom class user object to Jaguar,you need to use the SYJ database interface rather than SYC to connect to anAdaptive Server Enterprise database. You cannot use SYJ in the PowerBuilderdevelopment environment, but you can use the SYJ Database Profile Setupdialog box to set the appropriate connection parameters. You can then copy thesyntax from the Preview tab into the script for your Transaction object.ODBC database drivers and supporting filesPowerBuilder ODBCinterfaceThis section lists files that are required for all ODBC database connectionsfrom PowerBuilder or InfoMaker applications, as well as files required for aspecific database interface or DBMS.The following PowerBuilder ODBC interface files are required if yourapplication uses ODBC:Last updated November 23, 1999 7

Database connectionsNamePBODB70.DLLPBODB70.INIDescriptionPowerBuilder ODBC interfacePowerBuilder ODBC initialization fileMicrosoft ODBC filesInstalled pathC:\Program Files\Sybase\Shared\PowerBuilderDeployment path Same directory as the application, in a directory on thesystem path, or in the App Path registry key.Registry entries See "App Path registry key" on page 3.Notes The INI and DLL files must be in the same directory. If you havemodified the PBODB70 initialization file, make sure you deploy the modifiedversion.The following Microsoft ODBC 3.5 files are required if your application usesODBC:NameDS16GT.DLLDS32GT.DLLODBC32.DLLODBC32GT.DLLODBCAD32.EXEODBCCP32.CPLODBCCP32.DLLODBCCR32.DLLODBCINST.CNTODBCINST.HLPODBCINT.DLLODBCTRAC.DLLDescriptionMicrosoft ODBC driver manager, DLLs, and Help filesIntersolv ODBCdrivers and supportingfilesInstalled pathDeployment pathRegistry entriesWindows system directoryWindows system directoryNoneNotes The Microsoft ODBC Driver Manager (ODBC32.DLL) andsupporting files are usually already installed in the user’s Windows systemdirectory. You can use the MDAC_MIN.EXE setup file in the Supportdirectory on Install Disk 2 to update users’ systems if necessary.The following Intersolv ODBC files are required if you use the databaseinterface specified.8 Last updated November 23, 1999

Deployment Files for PowerBuilder, InfoMaker, and the Web DataWindowInstall options Name DescriptionCommon Files DBODB6.DLL ASA ODBC driverDBBACKUP.EXE ASA backup utilityDBCON6.DLL Connection dialog, required if you do notprovide your own dialog and your end usersare to create their own data sources, if theyneed to enter user IDs and passwords whenconnecting to the database, or if they needto display the Connection dialog for anyother purposeDBISQL.EXE Interactive SQL utilityDBLGEN6.DLL Language-specific string library (ENindicates the English version)DBLIB6.DLL Interface libraryDBODTR6.DLL ODBC translator, required if yourapplication relies on OEM to ANSIcharacter set conversionDBTOOL6.DLL ASA database toolsDBUNLOAD.EXE ASA unload utilityDBVALID.EXE ASA validation utilityRuntime Server RTENG6.EXE Restricted runtime engineDBCTRS6.DLL Performance utilityDBEXTF6.DLL External interfaceDBSERV6.DLL Server utilityDBWTSP6.DLL Tools supportInstalled path6.0\win32C:\Program Files\Sybase\Adaptive Server AnywhereDeployment path Same directory as the application, in a directory on thesystem path, or in the App Path registry key.Registry entries See "App Path registry key" on page 3 and "ConfiguringODBC data sources and drivers" next.Notes Supporting files should be installed in the same directory asDBODB6.DLL. If you are not using the English string library, make sure youdeploy the appropriate version of the language-specific string library.Last updated November 23, 1999 11

Database connectionsConfiguring ODBCdata sources anddriversODBC.INI To allow the user to connect to a particular data source, yourinstallation program must provide a definition for that data source in theODBC.INI key in the registry on the computer that accesses the data source, inHKEY_CURRENT_USER for a user DSN or in HKEY_LOCAL_MACHINE fora system DSN. The data source definition specifies the name and location ofthe database driver as well as the command required to start the databaseengine. The data source in the ODBC Data Sources key must also be listed inODBC.INI.The following shows typical registry entries for a data source called MyAppDB that uses Adaptive Server Anywhere. Registry keys are enclosed in squarebrackets and are followed by string values for that key in the format"Name"="Value":[HKEY_CURRENT_USER\SOFTWARE\ODBC\ODBC.INI\MyApp DB]"Driver"="C:\Program Files\Sybase\AdaptiveServer Anywhere 6.0\win32\dbodbc6.dll""Start"="c:\program files\sybase\AdaptiveServer Anywhere 6.0\win32\rteng6.exe -c8m""UID"="dba""PWD"="sql""Description"="Database for my application""DatabaseFile"="C:\Program Files\myapps\myapp.db""AutoStop"="Yes"[HKEY_CURRENT_USER\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources]"MyApp DB"="Adaptive Server Anywhere 6.0"ODBCINST.INI Your installation program needs to make two types of entry inthe ODBCINST.INI key in HKEY_LOCAL_MACHINE\SOFTWARE\ODBCfor each driver that your deployed application uses:• Add a string value with the name of the driver and the data value"Installed" to the ODBC DRIVERS key in ODBCINST.INI.• Add a new key for each driver to the ODBCINST.INI key with stringvalues for Driver and Setup. Some drivers require additional string valuesin ODBCINST.INI.If the ODBC database driver files are not located in a directory on the systempath, you also need to add their location to the App Paths key for the executablefile.If you are using ODBC drivers obtained from a vendor, you can use the driver’ssetup program to install the driver and create registry entries.12 Last updated November 23, 1999

Deployment Files for PowerBuilder, InfoMaker, and the Web DataWindowThe following shows typical registry entries for Adaptive Server Anywhereand INTERSOLV Sybase drivers. Registry keys are enclosed in squarebrackets and are followed by string values for that key in the format"Name"="Value":[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\myapp.exe]"Default"="C:\Program Files\myapps\MYAPP.EXE""Path"="Program Files\sybase\shared\PowerBuilder;c:\program files\sybase\Adaptive ServerAnywhere 6.0\win32\;c:\program files\sybase\shared\IntersolvODBC;"[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers]"Adaptive Server Anywhere 6.0"="Installed""PB INTERSOLV OEM 3.11 32-BIT Sybase"="Installed"[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Adaptive Server Anywhere 6.0]"Driver"="c:\program files\sybase\AdaptiveServer Anywhere 6.0\win32\dbodbc6.dll""Setup"="c:\program files\sybase\AdaptiveServer Anywhere 6.0\win32\dbodbc6.dll"[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\PB INTERSOLV OEM 3.11 32-BIT Sybase]"Driver"="C:\Program Files\sybase\shared\IntersolvODBC\pbsyb13.dll""Setup"="C:\Program Files\sybase\shared\IntersolvODBC\pbsyb13.dll""APILevel"="1""ConnectFunctions"="YYY""CPTimeout"="60""DriverODBCVer"="03.00""FileUsage"="0""SQLLevel"="0""UsageCount"="1"For more information about the contents of the registry entries for ODBCdrivers and data sources, see Connecting to Your Database.Last updated November 23, 1999 13

Database connectionsOLE DB database providersIf your application uses OLE DB to access data, you must install Microsoft’sData Access Components software on each user’s computer if it is not installedalready.You can use the MDAC_MIN.EXE setup file in the Support directory on theInstall Disk 2 to update users’ computers. The Microsoft OLE DB providers,SQLOLEDB and MSDASQL, will be installed when you runMDAC_MIN.EXE.The following files are required if you use the Intersolv OLE DB data providerspecified. If your application uses an OLE DB data provider from anothervendor, you must still deploy PBOLE70.DLL as well as the files specified bythe vendor.Optional Help filesHelp (.HLP and .CNT) files need only be deployed if you expect users toperform database administration tasks.NamePBOLE70.DLLGLOSSARY.HLPINODBC.LICIVODBC.LICPBADMIN.CNTPBADMIN.EXEPBADMIN.HLPPBADMINR.DLLPBBAS03.DLLPBBAS04.DLLPBBAS04.HLPPBBAS04R.DLLPBCVT01.DLLPBUTL03.DLLPBUTL04.DLLPBUTL04R.DLLPBINF04.CNTPBINF04.DLLPBINF04.HLPPBINF04R.DLLPBINF04S.DLLRequired forPowerBuilder OLE DB interface required for all OLE DBconnectionsLicense and help files and administration utilities requiredfor all INTERSOLV OLE DB data providersINTERSOLV Informix714 Last updated November 23, 1999

Database connectionsInstalled pathC:\Program Files\Sybase\Shared\PowerBuilderDeployment path Same directory as the application, in a directory on thesystem path, or in the App Path registry key.Registry entries Make sure the CLASSPATH environment variable includesthe PowerBuilder classes.zip file. If you are using the Sun JDS driver, theCLASSPATH environment variable should also include the classes.zip file forthe version of the JDK you are using. For example:[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment]"CLASSPATH"="C:\Program Files\sybase\shared\PowerBuilder\classes.zip;C:\Program Files\sybase\shared\Sun\jdk118\lib\classes.zip;...Notes See "PowerBuilder component on Jaguar server" on page 17 and "WebDataWindow on Jaguar server" on page 21.16 Last updated November 23, 1999

Deployment Files for PowerBuilder, InfoMaker, and the Web DataWindowPowerBuilder component on Jaguar serverThe following files are required on a Jaguar server on which componentsgenerated in PowerBuilder will run.NoteIf PowerBuilder components do not use a feature or database interface listed inthe table, the file does not need to be installed on the Jaguar server.Windows UNIX DescriptionPBVM70.DLL libpbvm70x.ext* PowerBuilder virtual machine (requiredfor all PowerBuilder components)LIBJCC.DLL libjcc.ext Required by PowerBuilder virtualmachinePBDWE70.DLL libpbdwe70x.ext DataStore supportPBJAG70.DLL libpbjag70x.ext, PowerBuilder support in Jaguarpbjag70.extPBRTC70.DLL — RichText supportPBO7370.DLL libpbo7370x.ext Oracle 7.3 database driverPBO8470.DLL libpbo8470x.ext Oracle 8.0.4 and later driverPBODB70.INI pbodb70.ini PowerBuilder ODBC initialization filePBODB70.DLL libpbodb70x.ext PowerBuilder ODBC interfacePBSYJ70.DLL libpbsyj70x.ext Adaptive Server Enterprise nativedatabase interfacePBJDS70.DLL libpbjds70x.ext JDBC database driver for Sun Java VM— libpbwfr70.ext PowerBuilder UNIX extension library— libsmartheap_mt.ext Required for PowerBuilder memorymanagementPBDWR70.PBD pbdwr70.pbd Web DataWindow support (requiresPBDWE)— htmldw.js Web DataWindow supportCLASSES.ZIP classes/PBjdbcname Java classes for PowerBuilder JDBCdrivers (required for JDS)* ext represents the platform specific extension for library names; for example, onSolaris this file is libpbvm70x.so.Last updated November 23, 1999 17

PowerBuilder component on Jaguar serverOn WindowsOn UNIXOn Windows, the files listed in the first column of the table above are installedby default when you select the typical or custom install for Jaguar from theEAStudio or PowerBuilder installation program. If they are not installed on aJaguar server on which you will install PowerBuilder components, you canrerun the Jaguar install and select PowerBuilder Runtime from the Custominstall.Installed pathC:\Program Files\Sybase\Shared\PowerBuilderRegistry entries The location of the PowerBuilder runtime files must be inthe application path for Jagsrv.exe. Add it to the Path string value in thisregistry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\jagsrv.exe.Notes You can use other database drivers with Jaguar components, but youmust use one of the drivers listed in the table above if you want to takeadvantage of Jaguar support for transaction management and instance pooling.If you deploy a PowerBuilder component to a Jaguar server running on UNIX,the component can have neither graphical dependencies nor dependencies onthe Windows application programming interface. The files with an x at the endof the filename listed in the second column of the table above are an alternativeset of PowerBuilder runtime libraries that do not support Windows API calls.They will be used instead of the PowerBuilder development libraries when youdeploy a component to Jaguar.The shared libraries are installed in the Jaguar lib directory when Jaguar isinstalled on UNIX. The Java classes required for PowerBuilder JDBC driversare installed in the Jaguar html/classes/com/sybase/powerbuilder/jdbcdirectory.Connection caches on UNIX PowerBuilder components require thedatabase drivers listed in the table above in order to use connection caches.When a PowerBuilder component uses a connection cache, the appropriatePowerBuilder driver is loaded.To create a connection cache for an Informix or DB2 database, you can use aMerant (formerly Intersolv) 3.5 ODBC driver that is included with Jaguar.After creating an ODBC data source using the file shown in the followingtable, create a Jaguar connection cache to the ODBC data source:NameDatabasePBinf14.ext Informix 5.x, 6.x, 7.x via Informix-Connect 7.3PBinf914.ext Informix 7.x, 9.x via Informix-Client SDK 2.xPBdb214.extDB2 Universal Database (UDB)18 Last updated November 23, 1999

Deployment Files for PowerBuilder, InfoMaker, and the Web DataWindowPowerBuilder COM serversIn addition to the COM server file generated in PowerBuilder, the followingPowerBuilder runtime files should be installed on the computer on which theserver will run if the component uses the feature listed in the table:NamePBVM70.DLLLIBJCC.DLLPBDWE70.DLLPBRTC70.DLLPBODB70.INIPBODB70.DLLDescriptionPowerBuilder virtual machine (required for allPowerBuilder components)Required by PBVM70.DLLRequired if the component uses DataStoresRequired if the component uses Rich TextPowerBuilder ODBC initialization file required for databaseconnectivity in MTSPowerBuilder ODBC interface required for databaseconnectivity in MTSInstalled pathDeployment paththe system path.C:\Program Files\Sybase\Shared\PowerBuilderIn the same directory as the COM server or a directory onRegistry entries The PowerBuilder COM server is self-registering, whichmeans that you can use the REGSVR32 utility to register it on the computer onwhich it will be used.Notes For information about deploying PowerBuilder COM servers to MTSand using them with DCOM, see Application Techniques.Database driversIf your component connects to a database, you must also deploy the appropriatedatabase drivers. You can use any database driver with a COM component, butyou must use ODBC if you want to take advantage of MTS support fortransaction management and connection pooling. If you require support forconnection pooling only, you can use any thread-safe ODBC driver. If you alsorequire support for transactions, you must use a driver that supports theMicrosoft Distributed Transaction Coordinator (DTC), such as the MicrosoftODBC driver for Oracle or the Microsoft ODBC driver for SQL Server.For more information about database drivers, see "Database connections" onpage 6.Last updated November 23, 1999 19

PowerBuilder automation serversPowerBuilder automation serversTo use a PowerBuilder automation server, the following files need to bedeployed:• The PBD or DLL containing the implementation of the automation server• The generated type library file if you chose to create one or, if you built anamed server, the PBAEN70.TLB file that provides type libraryinformation for PowerBuilder.Application• A copy of the registry update (.REG) file generated in the Project painteredited to reference the directory where you will deploy the PBD or DLLand the type library file• The PowerBuilder runtime and database connectivity files required by theserver as described in "PowerBuilder COM servers" on page 19After deploying the files listed above, run the registry update file to register theserver on the target computer. For more information about using automationservers and deploying to MTS, see Application Techniques.20 Last updated November 23, 1999

Deployment Files for PowerBuilder, InfoMaker, and the Web DataWindowWeb DataWindow on Jaguar serverFiles required on theJaguar serverYou can run the Web DataWindow server component on a Jaguar server usingPowerDynamo as the page server.Two types of files are required on the Jaguar server:• The PBLs or PBDs containing the definitions of your DataWindow objectsMake sure they are installed in a directory in the Jaguar server’s path. IfJaguar is running as a service, they must be on the system path or thenames of the PBLs or PBDs must be fully qualified.• PowerBuilder runtime files (including PBVM70.DLL, PBJAG70.DLL,and PBDWE70.DLL on Windows) and PBDWR70.PBD, which containsthe implementation of the DataWindow HTMLGenerator componentOn Windows, these files are installed by default when you select theJaguar typical or custom install from the Enterprise Application Studio orPowerBuilder Enterprise installation program. If they are not installed,you can rerun the Jaguar install and select PowerBuilder Runtime from theCustom install. For more information about required files on Windows andUNIX, see "PowerBuilder component on Jaguar server" on page 17.You also need to create a connection cache for the database the component willaccess. For more information, see "Configuring the Jaguar server to use thePowerSite Web DataWindow server component" in the PowerBuilder onlineHelp or the DataWindow Programmer’s Guide.Custom componentsYou can create a custom version of the DataWindow component and configureits properties for more efficient reuse. For more information, see "Using acustomized server component in Jaguar" in the PowerBuilder online Help orthe DataWindow Programmer’s Guide.Files required on thePowerDynamo serverTo use PowerDynamo as the page server and connect to the Jaguar componentusing Java, the following files are required on the PowerDynamo servercomputer:HTML pages, templates, and scripts These are the files that you created foryour application. If you used PowerSite to generate these files, you can use thePowerSite deployment controller for PowerDynamo to install them. For moreinformation, see the PowerSite documentation.Jaguar client software for JavaPowerDynamo server:The following file is required on theLast updated November 23, 1999 21

346Claire Judde de Larivièremécanique » de négociant au long cours, en jouant précisément sur les mots et sur leursens, de façon à obtenir le statut tant désiré 50 .La domination sociale se voyait formalisée par des statuts, en particulier dedépendance, issus de l’infériorité juridique. L’exercice de certains métiers ou activitésconférait un statut limitatif en terme de droits. La servitude, selon ses degrés et descontextes divers, était au cœur des enjeux de nomination. Sophie Mano le montre pourle cas des femmes esclaves, et Matthieu Scherman pour celui des dépendants dans lasociété trévisane du XVI e siècle. Dans un cas comme dans l’autre, dire son activitécontraignait à faire état de sa dépendance, de sa servitude et de sa soumission, d’où lesstratégies d’évitement mises en place par les acteurs pour dissimuler cette inférioritéjuridique. À Trévise, lors de la rédaction des estimi, certains déclarants cherchaientvisiblement à taire la véritable nature de leur activité professionnelle de façon à ne pasapparaître comme dépendants.De la même façon, le statut pouvait à son tour interdire ou contraindre à la pratiquede certaines activités professionnelles. Le cas des prisonniers de guerre étudiés parJean-Paul Depretto le montre : c’était le statut spécifique de ces prisonniers quidéterminait les activités qu’ils devaient pratiquer. Au-delà de cet exemple, àconsidérer avec précaution compte tenu du contexte spécifique, il est néanmoinscertain que l’interaction entre nomination professionnelle et statut juridique étaitpermanente durant l’Ancien Régime, chacun contribuant à la définition de l’identité,des droits et de la position dans le monde social.Grandeurs, honneur et déshonneurLa nomination professionnelle qualifie et contribue en parallèle à l’expressiond’une position hiérarchique, d’une honorabilité, d’un prestige social. Robert Descimonrappelle que dire l’activité c’est s’inscrire dans une échelle d’honorabilité, et que lesacteurs usent de taxinomies qui manifestent leur « grandeur ». Les entrepreneurs dontMarc Perrenoud nous rapporte les mots le savent bien : leur usage d’un répertoirelinguistique spécifique pour désigner leur propre activité et leur vocabulaire techniqueparticipent d’une stratégie de positionnement. Les acteurs élaborent ainsi des systèmesde justification et de légitimation de l’identité professionnelle, reposant sur unvocabulaire spécifique. Les artisans ici présentés usent, semble-t-il consciemment, determes plutôt que d’autres, afin d’établir des grandeurs relatives – dans l’acception deBoltanski et Thévenot 51 – reposant tout autant sur la compétence professionnellerevendiquée, la nature du travail réalisé et l’identité et le statut des commanditaires destravaux.5051Anna Bellavitis, « “Per cittadini mettere...”. La stratificazione della società veneziana cinquecentescatra norma giuridica e riconoscimento sociale », Quaderni Storici, n. s., 89, fasc. 2, 1995, p. 359-383 ;Andrea Zannini, « Il “pregiudizio meccanico” a Venezia in età moderna. Significato e trasformazioni diuna frontiera sociale », Le regole dei mestieri e delle professioni. Secoli XV-XIX, ed. M. Meriggi etA. Pastore, Milan, Franco Angeli, 2000, p. 36-51.Luc Boltanski, Laurent Thévenot, De la justification. Les économies de la grandeur, Paris, Gallimard,1979.

Deployment Files for PowerBuilder, InfoMaker, and the Web DataWindowWeb DataWindow on MTS or IISFiles required on theMTS or IIS serverYou can run the Web DataWindow server component on a MicrosoftTransaction Server using either PowerDynamo or ASP as the page server. Youcan also run the Web DataWindow on a Microsoft IIS application server.Two types of files are required on the MTS or IIS server:• The PBLs or PBDs containing the definitions of your DataWindow objectsMake sure that they are installed in a directory on the system path.Use the system path and system DSNsBecause MTS and IIS both run as system services, required files must beavailable on the system path and data sources must be defined as systemDSNs. The user path and user DSNs are not referenced by the server.• PowerBuilder runtime files and PBDWR70.DLL, which contains theimplementation of the DataWindow HTMLGenerator componentNamePBVM70.DLLLIBJCC.DLLPBDWE70.DLLPBODB70.DLLPBODB70.INIPBDWR70.DLLDescriptionPowerBuilder virtual machineRequired by PBVM70.DLLDataWindow supportPowerBuilder ODBC interfacePowerBuilder ODBC interface setup fileDataWindow HTMLGenerator componentInstalled path If PowerBuilder is not installed on the MTS or IIS servercomputer, these files must be installed in a directory on the system path on theMTS or IIS server. They can be obtained from theSybase\Shared\PowerBuilder directory on the computer on whichPowerBuilder is installed.Registry entries If PBDWR70.DLL was copied from another computer, itmsu be registered on the MTS or IIS server. You can use the regsvr32 utility toregister it:regsvr32.exe pbdwr70.dllNotes ODBC data sources must be defined as system DSNs. For moreinformation about configuring ODBC, see "Configuring ODBC data sourcesand drivers" on page 12.Last updated November 23, 1999 23

Web DataWindow on MTS or IISFiles required on thePowerDynamo serverFiles required on theASP serverIf MTS is hosting the server component and running on a different computerfrom IIS, you need to create a client install package using MTS Explorer andinstall it on the IIS machine.To use PowerDynamo as the page server and connect to the MTS componentusing ActiveX, the following files are required on the PowerDynamo servercomputer:HTML pages, templates, and scripts These are the files that you created foryour application. If you used PowerSite to generate these files, you can use thePowerSite deployment controller for PowerDynamo to install them. For moreinformation, see the PowerSite documentation.To use ASP as the page server and connect to the MTS or IIS component usingActiveX, the following files are required on the ASP server computer:HTML pages, templates, and scripts These are the files that you created foryour application. If you used PowerSite to generate these files, you can use thePowerSite deployment controller for ASP to install them. For moreinformation, see the PowerSite documentation.24 Last updated November 23, 1999

Deployment Files for PowerBuilder, InfoMaker, and the Web DataWindowDataWindow Web control for ActiveXThe following file must be deployed to your web server if you are using theDataWindow Web control for ActiveX:NamePSDWC70.CABRequired forCAB file containing an Open Software Distribution informationfile, DLLs for the Web ActiveX and the Transaction control, andJava class files for the JDBC driverTo make the Web ActiveX and the Transaction control available to the clientbrowser, code the CODEBASE attribute in the Object element in the deployedHTML page.About the CODEBASE attributeThe CODEBASE attribute identifies the location of a CAB or OCX file so thata browser can download it, unpack it if it is a CAB file, and register it on theuser’s computer. A typical value for CODEBASE uses a relative URL toidentify the location of the CAB or OCX file followed by a # sign and a fourpart version number separated by commas. The version number is the same asthe version number of PowerBuilder. For example:CODEBASE="cabs/psdwc70.cab#7,0,0,5031"For more information see "Deploying the DataWindow Web control" in thePowerBuilder online Help or the DataWindow Programmer’s Guide.Last updated November 23, 1999 25

Plugins and PowerBuilder window ActiveX controlsPlugins and PowerBuilder window ActiveX controlsPluginsThe following files must be deployed to users’ computers if you are usingDataWindow or window plugins:NameNPPBA70.DLLNPPBS70.DLLNPDWE70.DLLRequired forStandard window pluginSecure window pluginDataWindow pluginWindow ActiveXcontrolsInstalled path C:\Program Files\Sybase\PowerBuilder 7.0\InternetTools\PluginsDeployment path Browser plugins directory.Notes All plugins require a browser that supports plugins. Window pluginsalso require the PowerBuilder runtime DLLs on users’ computers. For moreinformation about other files that need to be deployed on the web server andclient computers, see Using the PowerBuilder Internet Tools.The following files must be made available on users’ computers if you areusing the PowerBuilder window ActiveX:NamePBRX70.OCXPBRXS70.OCXRequired forStandard PowerBuilder window ActiveXSecure PowerBuilder window ActiveXInstalled path Windows system directory.Deployment path Windows system directory.Registry entries The PowerBuilder window ActiveX controls can be madeavailable on the client computer by copying them to the computer andregistering them. You can use the REGSVR32 utility to register the files.Alternatively, include the CODEBASE attribute in the Object element in theHTML page on the web server. For more information, see "About theCODEBASE attribute" on page 25.Notes PowerBuilder window ActiveX controls require a browser thatsupports ActiveX controls. They also require that the PowerBuilder runtimeDLLs and the Microsoft files MFC42.DLL, MSVCRT.DLL, URL.DLL, andURLMON.DLL be available on users’ computers. The Microsoft files areusually already installed in the target computer’s Windows system directory. Ifthey are not installed, they can be downloaded as a CAB file from this web site:http://activex.microsoft.com/controls/vc/mfc42.cab.For more information about other files that need to be deployed on the webserver and client computers, see Using the PowerBuilder Internet Tools.26 Last updated November 23, 1999