Using the Caché %Installer Class - InterSystems Documentation

Adding Users and Passwords}}ClassMethod setup(ByRef pVars, pLogLevel As %Integer, pInstaller As%Installer.Installer) As %Status [ CodeMode = objectgenerator,Internal ]{#; Let XGL document generate code for this method.Quit ##class(%Installer.Manifest).%Generate(%compiledclass,%code, "MyInstall")}Important:The %occInclude include file, which includes methods required by the %Installer class, must be specifiedat the beginning of every %Installer class you create.The name of the XData block (MyInstall) is used by the MyPackage.MyInstaller.setup method to generate the code forthat manifest, which is passed as the third argument of the %Installer.Manifest.%Generate() method.Note:Referencing XMLNamespace = INSTALLER provides Studio Assist capability while authoring your %Installerclass.The outer-most xml tag, , contains all the information for code generation. There can be as many tags as needed within the tag to define namespaces in the manifest.A tag, which is located inside a tag, is required only if databases and/or mappingsare being defined. There must be as many tags within the tag as are needed to definethe namespace. In addition, following each tag, you can add , ,and tags as required. The tag activates the defined mappings.Within the context of a tag — after the databases and their mappings have been defined — globals can beloaded, and routines and classes can be loaded and compiled using tag. Class methods can be invoked usingthe tag. Invoked class methods can execute routines and access globals that have been imported.Optionally, you can define variable pairs with the tag; each variable must specify a name and value. When the valuefor the is needed, the name is referenced by the ${NameAssigned} syntax.2 Adding Users and PasswordsYou can add users (including their roles and passwords) with the System Management Portal, or you can use the Security.Usersclass on a staging instance of Caché or Ensemble as follows:1. Export the user information by using the Security.Users.Export() method.2. Import the user information by adding the following at the beginning of your %Installer class (in the %SYS namespace):where PathToExportedUserInformation is the location of the output file specified in the Security.Users.Export()method.3 %Installer TagsFollowing are descriptions of the tags (in alphabetical order) you can use in your %Installer class.Note:Values shown in italics are the defaults used if the setting is not specified explicitly.2 Using the Caché %Installer Class