80 likes | 272 Views
JCOP Framework Installation Tool. Packaging Components and Related Issues Sascha Marc Schmeling FWWG 30.11.2005. fwInstallationInfo.activateManagersDisabled now forcing manager activation is possible fwInstallation_getApplicationSystem (string applicationName, dyn_string &systemNames)
E N D
JCOP Framework Installation Tool Packaging Components and Related Issues Sascha Marc Schmeling FWWG 30.11.2005
fwInstallationInfo.activateManagersDisabled now forcing manager activation is possible fwInstallation_getApplicationSystem(string applicationName, dyn_string &systemNames) find a connected system where a specific component is installed fwInstallation_createDpl(string fileName, dyn_string dataPointNames, dyn_string dataPointTypes = "", string filter = "DAOP") like ASCII manager fwInstallation_getPvssVersion(dyn_string & patches) returns the current PVSS version and the list of installed patches fwInstallation_createXmlfwInstallation_loadXml(string pathName, string componentName, string componentVersion, string componentDate, dyn_string requiredComponents, bool isSubComponent, dyn_string initScripts, dyn_string deleteScripts, dyn_string postInstallScripts, dyn_string postDeleteScripts, dyn_string configFiles, dyn_string asciiFiles, dyn_string panelFiles, dyn_string scriptFiles, dyn_string libraryFiles, dyn_string otherFiles, dyn_string & xmlDesc) create resp. load a component’s xml description file fwInstallation_packNgo(string destinationFolder, dyn_string xmlDesc) retrieve files for the component and copy them together into a folder Installation ToolNew Library Functionality
Installation Tool PackagerSpecific Functionality only displays paths as defined in guidelines open ASCII manager export an FSM tree from the given point in the hierarchy(dpl with types and tree + postInstall script) opens editor to selected script wizard to create an init or postInstall script for manager addition
project bin config dplist help en_US.iso88591 component images msg panels component fwFSMUser component objects component pictures component scripts component libs component scripts (init, postInstall, …) should go into ./scripts not ./config component files should go into sub-directories wherever possible ./help/en_US.iso88591/<comp> ./panels/<comp> ./panels/objects/<comp> ./panels/fwFSMUser/<comp> ./scripts/<comp> ./scripts/libs/<comp> NEW Enforced Paths
Manager Wizard do not just say “PVSS OPC Driver”, rather “PVSS OPC Connection to WIENER” • Tool to define managers for addition and activation
Planned Functionality • fwInstallation_getManagerVersion • retrieve version number of a specific manager • complete path enforcement