www.usoft.com To www.usoft.com

Topics started by dara.sami

57 Topics

dara.sami
dara.sami
published in USoft command line syntax

usd.exe

Starts a USoft application, or starts a user application built with USoft.The table below lists the command line options available for use with the usd.exe command.Option Purpose -A Starts the Authorizer. -D   Starts the Definer. Works only in combination with the -ddfile option, because the repository of USoft Developer itself is only presented in a file. -app name Runs USoft Developer on the repository specified by name. USoft Developer will search for the repository in the name.CON file, and for the name resource files. Under X-Windows, these files must all be in the XAPPLRESDIR directory. -d Debug option. -database name Specifies which database is to be used. This parameter is mandatory for SQL Server (OLEDB) and for ODBC, and optional for Oracle, but USoft recommends you specify this parameter also for each Oracle connection. -ddfile Reads the repository from flat files instead of from your RDBMS. If you use this option, yo

1160
dara.sami
1 year ago
dara.sami
dara.sami
published in USoft command line syntax

runbatch.exe

Starts the USoft processor that executes USoft jobs in order to run a named job.The table below lists the command line options available for use with the runbatch.exe command.Option Purpose -app name Specifies the name of the application. -database name Specifies which database is to be used. This parameter is mandatory for SQL Server (OLEDB) and for ODBC, and optional for Oracle, but USoft recommends you specify this parameter also for each Oracle connection. -ddfile Reads the repository from flat files instead of from repository. If you use this option, also use the -app option to specify the application to look for. -ddowner name Specifies that the application must be run on a repository owned by another user than the one under whose name you log in. To be used in combination with the -app option if you are NOT using the -ddfile option. This corresponds to the "Separate Properties for Repository and Application" option of USoft Bi

550
dara.sami
1 year ago
dara.sami
dara.sami
published in USoft command line syntax

rulesservice.exe

Starts a USoft Rules Service under the conditions specified.Syntax 1This syntax uses an equal sign ( = ) between option and value. Each option=value pair requires a separate entry (an entry with its own equal sign):> RulesService.exe -option=value [-option=value ...]Syntax 2This syntax uses a space between option and value. The name of an option with multiple values needs to appear only once:> rulesservice.exe -option value value ... [-option value value ...]OptionsThe table below lists command line options available for use with the rulesservice.exe command.Option Purpose -a port Specifies which port the Rules Service is to use. May be omitted when a filepath is specified with the -f option and the filename ends in -port. -c name Specifies a name for the Rules Service configuration. The name of the configuration file will be name appended with -port.config. -config Specifies that only a Rules Service configuration file is to be created, an

740
dara.sami
1 year ago
dara.sami
dara.sami
published in Installing USoft

Installing Oracle XE 21c for USoft

This article tells you how to install Oracle XE 21c for USoft.This article is for developers who want to create a local USoft sandbox installation on top of a free Oracle version.We have NOT yet tried and tested Oracle 21c for Production environments (as you can see here). In client projects, use Oracle 19c instead.Prerequisites Unset environment variables Remove existing XE installation Ensure you have Administrator privileges Oracle installation Download Oracle 21g Prepare for supplying SYS password Install Oracle 21c Test the XEPDB1 database connect string alias Ensure authentication by NTLM Explore listener process Explore pluggable databases (PDBs) in the container database (CDB) Setting up for USoft Create a database account for USoft in XEPDB1 Set up access to USoft PrerequisitesUnset environment variablesTemporarily unset any ORACLE_HOME and TNS_ADMIN environment variables you may have set. You need to unset these at the system level.Remove existing XE installationTh

21360
dara.sami
2 years ago
dara.sami
dara.sami
published in Upgrading to USoft 10

Upgrading to USoft 9.1

Development EnvironmentTo upgrade your repository tables from USoft 9.0 to USoft 9.1, use the Upgrade tool provided in USoft Binder:In USoft Binder, choose Item, New from the menu and choose Upgrade. Double-click the new Upgrade Tool item. Choose File, Start Upgrade from the menu, or click this icon:Production EnvironmentTo upgrade authorization tables, you can:Use the Upgrade tool in USoft Binder (see previous section in this article), or: Run the ‘Create Tables’ context menu option on the Authorizer item in USoft Binder, or: Execute as DBA or owner the following database script:<SystemDir>/Util/Upgrade/Upgrade_Authorizer_90_To_911_<Database>.sqlOn MS SQL Server, this USoft version no longer uses the TABLE_SEQUENCE_NUMBERS table for the generation of sequence numbers. Instead, SQL Server RDBMS sequences are used.When running against SqlServer you should be aware that as of this version, USoft does not use the TABLE_SEQUENCE_NUMBERS table for the generation of sequence numb

440
dara.sami
2 years ago
dara.sami
dara.sami
published in Installing USoft

Browser requirements

USoft web applicationsUSoft 10.0USoft web applications made with USoft Web Designer 10.0 will run with recent versions of the following browsers:Edge Google Chrome Opera FireFoxUSoft 9.1USoft web applications made with USoft Web Designer 9.1 will run with recent versions of the following browsers:Internet Explorer 11 Edge Google Chrome v66 or higher Opera v53 or higher FireFox v60 or higherUSoft StudioUSoft Studio will run in all popular browsers, but there are limitations especially for the diagramming facility. For details, click Help, About in the top-right corner of the USoft Studio screen.

190
dara.sami
2 years ago
dara.sami
dara.sami
published in Creating a USoft Development environment

Authorising team members for USoft 10.0

This article is about authorising team members in a USoft 10.0 development environment.For the USoft 9.1 situation, click here.Team members play typical roles in a project. Think of developers, architects, analysts and administrators.Developer roles give access to the different USoft tools in Development. USoft has created predefined developer roles for you. All you need to do is to open Authorizer and assign team members to the correct developer roles. The general steps are:In Development, open USoft Authorizer. Find the predefined roles for the tool you want to give access to. Use the “Authorizer names” table below to identify the tool. Assign each team member to the required role.Find more on USD roles in the next section.Find more on USAUTH, UDELIVER, USERVICE, USTESTER roles at the end of this article.Authorizer names for USoft toolsThis is what the USoft tools are called in USoft Authorizer:Authorizer name Tool name USD USoft Definer USoft Web Designer USoft Windows D

970
dara.sami
2 years ago
dara.sami
dara.sami
published in Share your best practices

Syslog logging for audit trails - Part I

With new data breaches being discovered nowadays almost weekly, it becomes ever more important to protect your application data and keep track of which user has accessed what data and any changes he may have made.  Such a chronological record of access to and modification of data is called an audit-trail.  Audit trails are often used as an investigative tool to detect and analyze application and user behavior for data breaches before they have made such a significant impact such as the complete exposure of the entire database of the application. In a properly configured audit trail system events leading to such an exposure are monitored, and as such data breaches can be kept to a minimum impact, if proper action is taken quickly. Audit trails are commonly kept in logs called audit logs, which keep track of:  Every access and changes to sensitive data in detail. This way, any unintended access can be traced directly to the person who viewed this data, or even changed it.  Any successf

2160
dara.sami
2 years ago
dara.sami
dara.sami
published in Understanding USoft

Locating USoft application flatfiles

When a USoft development team creates or deploys an application, a set of application flatfiles is generated that contains the core functionality of the application:application.conapplication.esiapplication.smgapplication.umgwhere application is the name of the USoft application.When a USoft application is run from flatfiles, USoft looks for these application flatfiles on the server's file system using the following steps. Each next step applies only if the previous step was unsuccessful.Step 1: \APP subfolderUSoft attempts to find application flatfiles in the \APP subfolder of the USoft installation directory. The USoft installation directory is indicated by the value of the Destination Path registry key for the installed USoft version.Step 2: FileSearchPathUSoft attempts to find application flatfiles by looking at the value or values of the FileSearchPath registry key for the installed USoft version.FileSearchPath is allowed to have multiple values separated by colons. USoft attempts

830
dara.sami
2 years ago
dara.sami
dara.sami
published in Understanding USoft

USoft registry keys on Windows

When you install USoft on Windows, key information is stored in the registry editor at:Computer\HKEY_LOCAL_MACHINE\SOFTWARE\USoft\versionwhere version is normally the USoft major release version without dot notation, for example:USoft91While it is customary and recommended to have only a single USoft installation on a server at any one time, it is possible to have several different versions concurrently. In this case you must ensure you are looking at the correct set of registry keys.For each major release version, USoft Setup stores registry information for the most recently (or the only) installed patch under the name of the major version. Here is an example of registry keys for USoft 10.0.BETA:The set of registry keys (on the left) is named:Usd100The letter patch of the USoft installation is listed as the value of the "Product version” key (on the right, highlighted). The USoft installation directory is listed as the value of the "Destination Path” key.As you can see, it is possible

390
dara.sami
2 years ago
dara.sami
dara.sami
asked in Got a Question?

In USoft 9.1, when working with modules and trying to update or populate tables of the main application via the authorizer, an 'Invalid object name' RDBMS error is shown, why? 

The error could be a result of USoft not being able to locate the module flat files. If modules are used as part of your application, then you need to make sure that the conceptual flat file (.con) of the module is locatable. More detailed information about how exactly USoft attempts to find application flatfiles is now available at: A quick test to see if the module flat file cannot be located is to put the module flat files in the APP directory of the USoft installation and try to populate/update the tables again via the Authorizer of the main application. If this resolves the error, then this means the flat files cannot be found in the fileSearchPath or HomeDir as indicated in the above documentation. Note that in USoft 10 Authorizer, the update/populate buttons are replaced with a single button Fill Authorizer Tables. The Update option is still accessible via the Authorizer "Tools" menu. If module flat files are missing, then this will also be indicated when trying to Fill the auth

1
Rob.van.Haarst
3 years ago
dara.sami
dara.sami
published in Maintaining a USoft Production environment

Scaling

What is scaling ?Scaling is making sure that a USoft application has an acceptable performance even at peak periods. You scale an application by extending available resources or by re-organising current resources so that they are used more efficiently (or a combination of both). There are 3 general scaling strategies:Scaling strategy Explanation Applicative scaling Improvements in application-specific characteristics: application design, Rules Service configuration, or Rules Engine configuration. Vertical scaling Improved use of available resources (CPU, RAM or DISK) of existing hardware and software. Horizontal scaling Extension of available processing units or physical nodes through the addition of technical resources: CPU, network bandwidth, RAM size or DISK size. This article first offers an overview Quick Guide of the issues involved.Then, it pays special attention to applicative scaling, taking event-driven, message-intensive USoft solutions as an example.Finally, at

760
dara.sami
3 years ago
dara.sami
dara.sami
published in Installing USoft

Server requirements for USoft Production

This article specifies what software you require for best performance of a Production environment running a USoft 9.1 or USoft 10.0 solution.USoft suggests that you have 2 separate machines, an application server and a database server (or database cloud service).Why 2 machines? USoft delivers data-intensive applications with strong data integrity based on the transaction model of the underlying RDBMS. Scaling options for such applications are limited when you combine the application layer and the database layer on the sameserver, because each application instance requires access to the same database records, unless your application allows for some form of sharding.Application serverOS Windows Server 2012R/2016/2019 Std (virtual) The minimum version is 2012R. Cores 4 RAM 8 to 12 GB Disk 200 GB Database server / Database Cloud ServiceDatabase platform is either Oracle or MS SQL Server.OS Windows Server 2012R/2016/2019 Std The minimum version is 2012R. The dat

1090
dara.sami
3 years ago
dara.sami
dara.sami
published in Uninstalling USoft

Uninstalling USoft Developer

To uninstall USoft Developer using the Control Panel:1. From the Control Panel, choose Programs and Features. The Uninstall or change a program window is now displayed.2. In the list view, select the USoft version you want to uninstall, click the Uninstall button above the list.3. The uninstaller dialog is now displayed. Click Uninstall.All files, folders, registry entries, shortcuts, etc. that are associated with USoft Series products will be removed from your system. All log files and extra files that were made after the initial installation are kept.Silent uninstallTo perform a silent uninstallation, you can add the flag -uninstall.Example.\USDSetup-x64.exe -q -uninstallYou need the exact same version installer to uninstall. If you do not have the executable anymore, you can use a PowerShell script. You also need to indicate the exact dayversion you want to uninstall. See “Versioning of USoft Developer” for details on dayversion names. An example of the PowerShell script for 64-bit

120
dara.sami
3 years ago
dara.sami
dara.sami
published in Uninstalling USoft

Uninstalling a USoft Rules Service

To uninstall a USoft Rules Service:1. Open the USoft Binder file with which the Rules Service was created.2. Right-mouse click on the Rules Service item and choose Properties.The Property Sheet for the Rules Service appears.3. If the Rules Service is still running, press the Stop button.4. Press the Remove button.5. Press OK, then press the Save icon (or choose File, Save) in the Binder window.The service will now no longer appear in the list view of the Services console in the Control Panel. To see this, if this console was already open, make sure you press the Refresh icon.

90
dara.sami
3 years ago
dara.sami
dara.sami
published in USoft license management

FLEX license management software

USoft Series uses FLEXlm license management software from Acresso Software. FLEXlm delivers high-performance multi-user license checks for features specified in the license file. This is a text file that can be read with any text editor.Do not edit this license file. This makes it unusable.Three-server redundant license serversFLEXlm supports a set of three license servers to be used in a redundant manner. If any two of the three license servers are up and running, the system is functional and hands out its total complement of licenses.The use of two license servers is strongly discouraged, because a set of redundant server nodes with only two server nodes gives you two points of failure. You must always have both server nodes running.When redundant servers are started, they elect a master, which performs all licensing operations. The other two servers are there to provide a secure licensing mechanism in the event of hardware failure, or if the master server node needs to be rebooted.

480
dara.sami
3 years ago
dara.sami
dara.sami
published in USoft license management

Troubleshooting license problems

If the license manager is not functioning properly, you may see one of the following:The USoft Binder can be opened normally but the response time will be slower. When an existing project (*.usb file) is opened in the USoft Binder, all of the icons are shown as broken icons. On startup of the USoft Binder a message may be displayed, stating that the license file could not be found.Most of the problems listed below refer to a license server configuration.A 'space' in the directory name of the license file is not permitted. An underscore should be used instead.License file missingProblem: There is no license file resident on the client. This is shown as a message under the logo on startup of the binder containing your company name.Solution: Copy the LICENSE.DAT file to the installation directory (the directory defined during the installation of USoft).License manager started in wrong directoryProblem: The license manager was started in the wrong directory on the server. The license serve

160
dara.sami
3 years ago
dara.sami
dara.sami
published in USoft license management

Checking the licensed USoft products

A possible cause of license problems is having insufficient license.To determine this, you can query the internal license manager component, and see which USoft products are installed:1. In the Definer, open the SQL Command dialog.2. Type:INVOKE licensemanager.queryWITHSELECT nullDepending on your license, this INVOKE statement must result in a list like the following:Setup80p   31-dec-2050Creapp80p   31-dec-2050Authorizer80p   31-dec-2050Definer80p   31-dec-2050...

140
dara.sami
3 years ago
dara.sami
dara.sami
published in USoft license management

Replacing a license file

USoft license management uses two license files: one on the License Server and one on each client installation. When a new license file has to replace the old one, the license files in both locations should be replaced.Replacing the LICENSE.DAT file on the ClientThe license file for the client installation can be found in the folder where USoft is installed. For a typical installation, this is: C\Program Files\USD8.There is no need to replace the LICENSE.DAT file at the location that was indicated during the installation procedure. Following installation of USoft products, this LICENSE.DAT file is no longer used.Replacing the LICENSE.DAT file for the license serverThe license file for the License Server can be found in the folder that has been indicated as the license server folder.If necessary, you can double-check the name of your License Server by opening the LICENSE.DAT file in a text editor. The name of your License Server is stored in the line that reads: "SERVER". This directory

200
dara.sami
3 years ago
dara.sami
dara.sami
published in USoft license management

Installing an evaluation license

To install an Evaluation license (without License Server), copy the LICENSE.DAT file to a directory on your client (or to a PC in your network) and indicate the location of the file when the USoft Installation program asks for this information. The installation program will then copy the license file from this location to the USoft installation directory. Once installation is complete the original location of the license file does not influence USoft functions, or the license manager.When the LICENSE.DAT file expires (or is renewed), you must replace the old license file with a new license file. You do not need to reinstall USoft Developer.

140
dara.sami
3 years ago
dara.sami
dara.sami
published in USoft license management

Installing a server-based license

To install a server-based license:You will first need to obtain the license server software and a valid server based license. Contact USoft Customer Support to obtain the license server software and a valid server based license (license.dat). On the machine that will be used as a license server, copy the obtained license.dat and extract the license server software to the same install directory. Make sure that the license.dat file is in the same directory as the usoft.exe file.The license directory can be customized in the license.dat at the line that reads DAEMON, e.g if the chosen install directory is C:\license, the license.dat should have the following line: DAEMON usoft C:\license\usoft.exe You can freely modify the license directory and port number usage (e.g the lines that contain TCP:xxxx or port=xxxxxxx) in the license file. Please do not edit any other details in the license file. Modifying the license file incorrectly can result in a corrupt license whe

900
dara.sami
3 years ago
dara.sami
dara.sami
published in USoft license management

Terminology used in license management

License DaemonThis is a program that runs on the License Server and maintains a count of the number of concurrent users of each USoft component. It is only required for counted licenses.License ServerThis is only required for counted licenses. You must assign a computer on your network as the license server and install and run the license daemon on this computer before using USoft Series products.Concurrent userOne user, working on one client will be counted as one user, regardless of the number of USoft components they are starting.What are Features?A feature represents a USoft Component. For example: User Application, Definer. It can also represent an RDMI component.The version number follows the feature name. For example: Definer80p is USoft Developer version 8 production.When issuing a new release, new feature names will be introduced. As a result, your old LICENSE.DAT file will not function in this new release and you will need a new LICENSE.DAT file.

80
dara.sami
3 years ago
dara.sami
dara.sami
published in USoft license management

USoft license management

Before you can install or use USoft products on your system, you must have a valid LICENSE.DAT file installed. During the setup procedure, you will be asked to provide the location of this license file.License management has been incorporated into the USoft product suite to ensure that use of USoft software components remains within the scope of license agreements.licenses can be requested by contacting the USoft service Desk (support@usoft.com).This file contains in an encrypted form the information supplied by you, and confirmed by USoft license registration. Please note that the name of the server and the installation directory of the license daemon are necessary for generating a license file for the server.There are two types of license available. The type of license that you need depends upon how you will be using the software.Server based license (with license server)This type of license requires a license server, which checks the use of USoft components. This type of license is

390
dara.sami
3 years ago
dara.sami
dara.sami
published in Creating a USoft Production environment

Running applications in the Production environment

This topic offers some guidelines for speeding up startup times for the application, and for increasing performance of the application itself.For optimum performance, applications should be run from flat files in the production environment. Make sure that the "-ddfile" option, and the application name are specified on the command line that starts the application.It is important that the Windows Designer is NOT enabled when starting the application in the production environment. Make sure that the "-wd" option (normally used to enable the Windows Designer) is NOT specified on the command line that starts the application. To run your application from flat files on Windows, the .CON and (if any) .ESI files for the application must be in your <install_dir>\APP directory. Performance will suffer if you run an application on a central server, especially if you use network drivers that are also running on the server. Best performance will result from running client versions of network d

280
dara.sami
3 years ago
dara.sami
dara.sami
published in Creating a USoft Production environment

Installing your application on a server

Once you have completely developed your business application with USoft Developer, you may wish to deploy the application by installing the flat files for the application on an application server. To do this, you need to install USoft Production on the server, and provide each client with a shortcut to the USoft Developer executable. The Target property for the shortcut on each of the client PCs must specify the following command line:path\usd.exe -ddfile -app applicationWhere path is the path to the directory on the server machine where the USoft Developer executable (USD.EXE) is located.Note that the flat files for the application must be installed in the APP subdirectory of the USoft Production installation tree.

320
dara.sami
3 years ago

Badge winners

Show all badges
Terms & ConditionsCookie settings