www.usoft.com To www.usoft.com

Topics started by Rory

116 Topics

R
Rory
published in Delivery Manager actions by name

Export metadata

This article is about the Export metadata Delivery Manager action.Export metadata1. Creates an XML metadata file by exporting all metadata from "Database account" to "Destination folder". Any columns named “CREATED_ON” or “CREATED_BY” are excluded from the export because this prevents problems on re-import if these columns are set to Updatable = No.The output file name is "application.USD.xml".The value of "Application" is only used to compose the filename of the destination file.2. Excludes from the result of Step 1 any columns named “CREATED_ON” or “CREATED_BY”. This prevents problems on re-import in the event that these columns are set to Updatable = No.3. If a value for the optional "Added XSL" parameter is passed, applies to the result of Step 2 the XSL transformation defined as the Custom XSL of that name.If the metadata is large in volume, it is not convenient to apply XSL via the "Added XSL" input parameter. In this case, consider applying the XSL to the result of "Export metad

340
R
1 year ago
R
Rory
published in Delivery Manager actions by name

Export deliverable appdata

This article is about the Export deliverable appdata Delivery Manager action.Export deliverable appdata1. From "Database account", creates an export file containing deliverable appdata for "Application" in "Destination folder".The output file name is "application.xml".2. If a value for the optional "Added XSL" parameter is passed, applies to the result of Step 1 the XSL transformation defined as the Custom XSL of that name.Deliverable appdata is data in tables marked as Deliverable in the Application Tables list for "Application" and "Database account". To view Application Tables lists, choose Define, Application Tables.To read the data, the application is automatically opened from Repository, except when Application = USERVICE (the Service Definer application delivered by USoft), in which case the application is automatically opened from Flat Files.Make sure you export appdata in such a way that you will not have problems re-importing the appdata later. To understand and fix frequent

170
R
1 year ago
R
Rory
published in Delivery Manager actions by name

Create tables

This article is about the Create tables Delivery Manager action.Create tablesCreates application tables for "Application" in "Database account". This operation is equivalent to choosing "Create Tables" from the context menu of a USoft Binder item for "Application" and "Database account".Does NOT perform Drop Existing Tables as a preliminary action.If the optional "Run from repository" flag is set to Y, then the tables information for "Application" is read from repository. Otherwise, it is read from flatfile (from the file called application.con in the \APP subdirectory of the USoft installation directory).ParametersName Type Optional? Application Application No Database account Database account No Run from repository Option flag Yes ErrorsTables information for the predefined USoft applications cannot be read from repository. If you set "Run from repository" = Y and "Application" to 'USD', 'USAUTH', 'USTESTER', 'USERVICE' or 'UDELIVER', it's an error.NotesIf you wan

280
R
1 year ago
R
Rory
published in Delivery Manager actions by name

Clear and import from TDF

This article is about the Clear and import from TDF Delivery Manager action.Clear and import from TDFFor "Application", in "Database account", runs the USoft Benchmark Clear Tables routine, then performs the USoft Benchmark Import routine using "Source file" as the TDF import file.If the optional "Run from repository" flag is set to Y, then "Application" (in the context of which USoft Benchmark is run) is run from repository. Otherwise, "Application" is run from flatfiles.ParametersName Type Optional? Application Application No Database account Database account No Source file Folder or file No Run from repository Option flag Yes ErrorsThe predefined USoft applications cannot be run from repository. If you set "Run from repository" = Y and "Application" to 'USD', 'USAUTH', 'USTESTER', 'USERVICE' or 'UDELIVER', it's an error.

400
R
1 year ago
R
Rory
published in Delivery Manager actions by name

Validate publication object

This article is about the Validate publication object Delivery Manager action.Validate publication object1. Checks that a publication configuration by the name of the Publication Configuration of "Publication Object" exists in "Database account" for the Application that is the Application of "Publication Object".2. If "Publication Object" has a specified Page Set, checks that a page set by the name of the Page Set of "Publication Object" exists in "Database Account" for the Application that is the Application of "Publication Object".If both Step 1 and Step 2 are successful:3. Sets the "Publication folder" of "Publication object" to the current Publish Directory of the Publication Configuration found in Step 1.4. Sets the "Alt folder" of "Publication object" to the current Alt Template Folder of the Publication Configuration found in Step 1.ParametersName Type Optional? Publication object Publication object No Database account Database account No ErrorsYou cannot have a "

210
R
1 year ago
R
Rory
published in Delivery Manager actions by name

Update Oracle sequences

This article is about the Update Oracle sequences Delivery Manager action.Update Oracle sequencesThis action is now deprecated. USoft 9.1 import routines deal with database sequence updates (both on Oracle and SQL Server) automatically. You only ever need this action if, for some reason, you plan to perform INSERTs of records directly against the RDBMS.This action applies only to the Oracle RDBMS. You must have Oracle software installed that allows you to call sqlplus from the command line. Delivery Manager does not offer this facility for SQL Server.1.    Creates an Oracle SQL script for resetting the current value of Oracle sequences used by USoft applications in "Database account" for generating unique numbers. This Oracle SQL script is named:sequences-exec.500.post.rdbms.sqland is placed in the folder indicated by the required "Working directory" parameter.2.    Executes this script in "Database account" if "Execute script" is set to Yes.The purpose of resetting the sequences is to

100
R
1 year ago
R
Rory
published in Delivery Manager actions by name

Synchronise

This article is about the Synchronise Delivery Manager action.SynchronisePerforms the standard "synchronise Internal Interfaces" routine of USoft Definer for consumer "Application" as defined in "Database account", with special behavior in 2 respects:1. Part of this routine is detecting any objects not interface objects before, that will be overwritten by the routine. If such objects exist, instead of presenting an interactive overview (the default synchronise behavior), a blocking error is raised ("Cannot synchronise. There are objects currently not interfaces that would be overwritten on synchronise.")2. Raises an error ("Cannot proceed. There are incorrect interfaces after synchronise.") if incorrect interfaces exist as a result of synchronise. If this error is raised, Step 1 is not undone.This action is available in Delivery Manager only for completeness. Synchronisation is normally a design-time, not a release-time activity. This activity is normally carried out manually after dis

190
R
1 year ago
R
Rory
published in Delivery Manager actions by name

Run SQL command

This article is about the Run SQL command Delivery Manager action.Run SQL commandLogs on to "Application" in "Database account" and executes a SQL statement specified as "SQL command".This action has nothing to do with the SQL Command tool as it is available in the various USoft tools. That tool has a much wider applicability. The sole purpose of the "Run SQL command" Delivery Manager action is to execute a data manipulation statement as part of a Delivery Manager task.If "Metadata" = 'Y', logs on to the USoft Definer, as opposed to the User Application.ParametersName Type Optional? Application Application No Database account Database account No SQL Command SQL Command No Metadata Y/N Option flag No Rules"Application" may not be 'USD' or 'USTESTER'. The "Run SQL command" action is not supported for USoft Definer and USoft Benchmark.Running from flat files or repositoryThe "Run SQL command" action runs automatically from flat files if "Application" is either 'UD

390
R
1 year ago
R
Rory
published in Delivery Manager actions by name

Release server

This article is about the Release server Delivery Manager action.Release serverThis action is the equivalent of running Publish for a server in USoft Service Definer, and then copying the result to a release folder.You can only run this action successfully if you first register the server in Delivery Manager using the Extract servers action. Choose Definer, Extracted Server Objects to see servers registered.1 .Re-executes the Extract servers action for "Database account". Uses the result of this action to check that "Server object" exists in "Database account":If it does, sets the Publication File Path folder for "Server object" as registered in Delivery Manager, to the current Publication File Path for the server in "Database account". If it does not, it's an error.2. Publishes the server referred to by "Server object" from "Database account" to the server's Publication File Path folder. If "Database account" is set to a value different from the Server Object's Database Account as reg

180
R
1 year ago
R
Rory
published in Delivery Manager actions by name

Release scripts

This article is about the Release scripts Delivery Manager action.Release scripts1.    (Re-)checks all upgrade scripts (if any) that are associated with the current release version of "Application".2.    If Step 1. is successful, copies the scripts to the "scripts" subfolder of the current release folder.3.    If "Include physical tables upgrade script" = Yes, the Release create-tables script action is called as part of the routine. This causes the create-tables script to be (re-)compiled and written to the \scripts folder. The create-tables script is named "application.200.upg.rdbms.sql".In Step 3, data for this create-tables script is read from the Database Account that is set as the "Source for Post-upgrade Check" property of "Application".In Step 3, the set of tables included in the create-tables script depends on the list of Application Tables in Delivery Manager with Skip = No (the default). But this list is not automatically brought up-to-date. To bring it up-to-date, you must c

270
R
1 year ago
R
Rory
published in Delivery Manager actions by name

Release Rules Service

This article is about the Release Rules Service Delivery Manager action.Release Rules ServicePlaces in the \rulesservices directory of the current release folder a copy of a Rules Service .config file that you indicate as the source file, for example:c:\usd100\bin64\RulesService-7777.configParametersName Type Optional? Source file Folder or file No AttachmentsWhen you call this action, if the current release has "Include attachments" = Yes, attachments for the "rulesservices" section (if any are defined) are copied to the specified subfolder of the "rulesservices" section folder. This happens only to attachments that have Blocked = No (the default). If a Custom XSL transformation is defined for the attachment, this transformation is applied to the output.This way, you can load and use USoft's deploy sample "deploy.xml" for Rules Services. Running this "deploy.xml" script on a target machine will configure-and-deploy target .config files if you add RulesService elements of the

320
R
1 year ago
R
Rory
published in Delivery Manager actions by name

Release publication

This article is about the Release publication Delivery Manager action.Release publicationYou can only call this action for the "Database account" that is the database account of the "Publication Object".1.Validates "Publication object". For details of this step, see the description for the “Validate publication object” action.2.For the application named by "Publication object", publishes either the Application or a specified Page Set against the Publication Configuration defined in "Database account" that is named by "Publication object".This step is the same as the “Publish publication object” action. Its output is written to the Publication Configuration's Publication folder.3.Releases the result of Step 2 to the \publications section of the current release folder, in a subfolder by the name of "Publication object", excluding any folders and files marked as Blocked at the level of the Publication Object.When you call this action, if the current release has "Include attachments" = Yes

180
R
1 year ago
R
Rory
published in Delivery Manager actions by name

Release modules

This article is about the Release modules Delivery Manager action.Release modulesGiven that "Application" is the application being released, for modules consumed by "Application", copies specified versions of module deliverables to the application's release folders.For this to work, you must first declare module versions manually. The module versions copied are those module versions that you have declared in Delivery Manager for "Application". To declare module versions, from the Delivery Manager menu, choose Define, Applications, and in the record for "Application", click the Modules tab.This action operates at file system level only. The module deliverables you want to copy must already be present on the file system in their own release directory. The recommended way of working is to produce module deliverables by releasing them through their own instance of Delivery Manager.This action first removes any copies made by a previous run and then makes fresh copies.ParametersName Type

230
R
1 year ago
R
Rory
published in Delivery Manager actions by name

Release metadata

This article is about the Release metadata Delivery Manager action.Release metadata1. Places in the \metadata directory of the current release folder an XML export file that describes the metadata of application "For application".The output file name is "application.USD.xml" where application is the value of the "For application" parameter.2. Creates, in the same \metadata folder, a diff file that compares the XML export file created in step 1 with the XML export file of the same name found in the \metadata folder of the previous release frame. The output file name is "application.USD.diff.xml". For more details on this file, see the "Diff file format" section below.ParametersName Type Optional? For application Application No Database account Database account No Initial comparison (Step 2)If the current release has Initial = Yes, an initialization file is created in addition. The name of this file is "application.USD.initial.xml". The initialization file contains only th

90
R
1 year ago
R
Rory
published in Delivery Manager actions by name

Release flat files

This article is about the Release flat files Delivery Manager action.Release flat filesIf "Database account" is specified, creates flatfiles for "Application" from "Database account"  in the \flatfiles subdirectory of the current release folder.If "Database account" is left empty, copies an already existing set of flatfiles to the \flatfiles subdirectory of the current release folder.ParametersName Type Optional? Application Application No Database account Database account No NotesThe output file names are application.file extension, for example, "MYAPP.CON". A flatfile is produced for "Application" for each of the following file extensions: .CON, .ESI, .SMG, .UMG. Any files/folders in the \flatfiles subdirectory other than these output files remain unaffected.When you call this action, if the current release has "Include attachments" = Yes, attachments for the "flatfiles" section (if any are defined) are copied to the specified subfolder of the "flatfiles" section folde

170
R
1 year ago
R
Rory
published in Delivery Manager actions by name

Release deliverable appdata

This article is about the Release deliverable appdata Delivery Manager action.Release deliverable appdata1. Creates a file containing deliverable application data of "Application" by exporting from "Database account" to the \appdata folder of the current release folder. The resulting file is called "application.xml".2. If a value for the optional "Added XSL" parameter is passed, applies to the result of Step 1 the XSL transformation defined as the Custom XSL of that name.3. Creates, in the same \appdata folder written to in Step 1, a diff file that compares the export file created in Step 1 with the export file of the same name found in the \appdata folder of the previous release frame. The output file name is "application.diff.xml". For more details on this file, see the "Diff file format" section below.To read the data, this action automatically opens the application from Repository, except when Application = USERVICE (the Service Definer application delivered by USoft), in which cas

160
R
1 year ago
R
Rory
published in Delivery Manager actions by name

Release custom folder

This article is about the Release custom folder Delivery Manager action.Release custom folderCopies all files and, recursively, folders contained in "Source folder" to "Destination folder" which is a location in the "custom" section of the release tree.If "Overwrite" = 'Y', any existing contents of "Destination folder" are first removed.When you call this action, if the current release has "Include attachments" = Yes, attachments for the "custom" section (if any are defined) are copied to the specified subfolder of the "custom" section folder. This happens only to attachments that have Blocked = No (the default) and only to attachments associated with "Destination folder" or with a descendant folder of "Destination Folder". If a Custom XSL transformation is defined for the attachment, this transformation is applied to the output.ParametersName Type Optional? Source folder Folder or file No Destination folder Folder or file No Overwrite Option flag No ErrorsThe input

160
R
1 year ago
R
Rory
published in Delivery Manager actions by name

Release create-tables script

This article is about the Release create-tables script Delivery Manager action.Release create-tables scriptReleases the create-tables script for changes in physical tables of "Application", as defined in "Database account", since the previous release.The output file name is "application.200.upg.rdbms.sql".The output file is placed in the \scripts directory of the current release folder.The set of tables included in the create-tables script depends on the list of Application Tables in Delivery Manager. See "Which tables are included?" below for details.ParametersName Type Optional? Application Application No Database account Database account No Which tables are included?Only changed tablesThe resulting script refers only to tables that have changed compared to the previous release. If there is no previous release (ie., if the current release is initial), then all tables are considered "changed".Only consumer tables, not consumed module tablesThe list of tables for a consu

410
R
1 year ago
R
Rory
published in Delivery Manager actions by name

Publish server

This article is about the Publish server Delivery Manager action.Publish serverThis action is the equivalent of running Publish for a server in USoft Service Definer.You can only run this action successfully if you first register the server in Delivery Manager using the “Extract servers” action. Choose Definer, Extracted Server Objects to see servers registered.1. Re-executes the Extract servers action for "Database account". Uses the result of this action to check that "Server object" exists in "Database account":If it does, sets the Publication File Path folder for "Server object" as registered in Delivery Manager, to the current Publication File Path for the server in "Database account". If it does not, it's an error.2. Publishes the server referred to by "Server object" from "Database account" to the server's Publication File Path folder. If "Database account" is set to a value different from the Server Object's Database Account as registered in the list of Extracted Server Objects

140
R
1 year ago
R
Rory
published in Delivery Manager actions by name

Publish publication object

This article is about the Publish publication object Delivery Manager action.Publish publication objectFor the application named by "Publication object", publishes either the Application or a specified Page Set against the Publication Configuration defined in "Database account" that is named by "Publication object".As a preparatory step, checks the validity of "Publication Object" in the same way as the “Validate publication object” action. During this step, the "Publication folder" of "Publication object" in Delivery Manager is set to the current Publish Folder of the Publication Configuration that will be published against.Writes the output to the Publication Configuration's Publication folder, as per the standard Web Designer procedure.To release this output to the release tree, use the “Release publication” action instead.ParametersName Type Optional? Database account Database account No Publication object Publication object No ErrorsYou cannot have a "Publish public

110
R
1 year ago
R
Rory
published in Delivery Manager actions by name

Populate tables list

This article is about the Populate tables list Delivery Manager action.Populate tables listIn Delivery Manager, in "Application Tables", creates or updates a list of database tables and interface tables defined for "Application".The list of tables is read from repository if "Database account" is specified. It is read from a metadata file if "Database account" is left empty. For details, see Parameters below.The purpose of this list is that you can specify :which of these application tables are deliverable, which must be skipped in create-tables scripts, and for which an ALTER TABLE statement must be generated for it in the create-tables script, as opposed to the default CREATE TABLE statement (the Upgrade Hint setting).If you re-run "Populate tables list", any previous Deliverable, Skipped, and Upgrade Hint settings remain unaffected.In the case of the USAUTH application, a first-time suggestion for deliverable tables is made by USoft.To read the table names, the application is automat

150
R
1 year ago
R
Rory
published in Delivery Manager actions by name

Mark up XML attribute

This article is about the Mark up XML attribute Delivery Manager action.Mark up XML attributeCreates, in an XML data file designated by "Replacement file", one or more placeholders for a target variable. An example of such a placeholder is:${Application}The placeholders are created by replacing one or more designated XML attribute values by "Replacement".The required "Replacement" must be a string that consists of at least one variable placeholder, or contains at least one. The other parameter values must not contain variable placeholders."Target element", "Target attribute", "Key name", "Key value", "Key ancestor" and "Key descendant" are strings that together determine the XML attribute(s) where the replacement takes place:The required Target element is the name of the XML element(s) where the replacement takes place. The required Target attribute is the name of the XML attribute(s) where the replacement takes place. Key name and Key value must both be passed, or both be omitted. If

50
R
1 year ago
R
Rory
published in Delivery Manager actions by name

Mark up text file

This article is about the Mark up text file Delivery Manager action.Mark up text fileCreates, in a text file that has a non-XML format, such as HTML, JSON, CSS, or flat text, one or more placeholders for a target variable. An example of such a placeholder is:${Application}The required "Replacement file" identifies the text file to be marked up.The placeholders are created by replacing all occurrences of "String" in "Replacement file" by "Replacement".The required "String" must not contain variable placeholders.The required "Replacement" must be a string that consists of at least one variable placeholder, or contains at least one.The primary purpose of calling this action is to make released deliverable files configurable to specific target computers. See the "Mark up XML attribute” action for creating variable placeholders in deliverables that are XML data files rather than text files.ParametersName Type Optional? Replacement file Folder or file No String String No Repla

80
R
1 year ago
R
Rory
published in Delivery Manager actions by name

Import metadata

This article is about the Import metadata Delivery Manager action.Import metadataImports into "Database account" the metadata that are contained in "Source file".Typically the source file name is "application.USD.xml".During this import, constraints and relationship checks are deactivated if "Disable rules" = 'Y'.To understand and fix frequent problems with XML imports, read the Known Problems section for the XML.Import() method.ParametersName Type Optional? Database account Database account No Source file Folder or file No Disable rules Option flag No  

170
R
1 year ago
R
Rory
published in Delivery Manager actions by name

Import appdata

This article is about the Import appdata Delivery Manager action.Import appdataImports into "Database account" the data for "Application" that are contained in "Source file".Typically, the source file name is "application.xml".During this import, constraints and relationship checks are deactivated if "Disable rules" = 'Y'.The input file may have been produced by running any of the following routines: "Export deliverable appdata", "Export all appdata", or "Release deliverable appdata".To understand and fix frequent problems with XML imports, read the Known Problems section for the XML.Import() method.ParametersName Type Optional? Application Application No Database account Database account No Source file Folder or file No Disable rules Option flag No  

100
R
1 year ago

Badge winners

Show all badges
Terms & ConditionsCookie settings