This software introduces a revolutionary concept of "Hot" Deployment of OneWorld®/EnterpriseOne® Software.

This means, that a qualifying Update can be deployed transparently to all active clients in your network, without interrupting anyone, from a single script - in fact, a single command, in minutes. Alternatively, HotDeploy command can be scheduled on any number of computers to run a few times a day to transparently and automatically maintain the latest versions of all specified Objects and Versions.

By running this utility, as an example, on a Terminal / Citrix Server, you can install most OW software Updates without the need to bring the Server off-line. This process simplifies and speeds up the Deployment, as well as leaves the servers on-line during the Deployment.

100% up time is now an available option for Terminal / Citrix Server and Fat Client users, plus each License of this software will pay off in just one time you use it, delivering pure savings afterwards:

It can be used to distribute new or modified software updates, including Data Selection and Data Sequencing changes in Versions or Vocabulary Override changes.

Objects, such as UBE, UBEVER (including Data Selections), APPL (including Vocabulary Overrides), DSTR, TBLE (except triggers), BSVW or GT can be "hot" deployed with this tool.

Technical details: NER (including TER) and C Business Functions cannot be deployed with this tool, because the DLL files are locked, when in use, and cannot be replaced on-line. In such cases, you will need to continue using the standard approach with Full or Update Packages, which you can still automate and speed up with our TSE Commander and PKGBUILD software.

All you need to do is to add any Objects, to be Deployed this way, to an OMW Project and let the Hot Deploy finish the job.

Technical details: Logistically, this can be a pre-defined Project name, if the Hot Deploy runs through Windows® Task Scheduler with the same command line, or any Project name, if Hot Deploy is executed manually for this specific Project or Projects. The Objects do not need to be modified in this Project, nor do they need to be checked out or have Tokens. The Objects can be dragged-and-dropped into such a Project and then back, after the Hot Deploy tool has been run. The Project is only used as a group reference to the actual Object names.

Note, that to use this tool, there is no need to Define, Build, Schedule and Deploy any Client Packages, saving you time.

This new software deployment process can be easily scheduled, or executed remotely with freeware PsExec tool, which we can help you script.

It can also be used on Fat Clients, even if there are active users logged-in and using OneWorld/EnterpriseOne® at the same time. Even if the OW login ID, supplied on the Hot Deploy command line, is different to the ones used by the interactive users on the target Fat Clients, it will still deploy the updates correctly.

Corresponding Server Packages may be required in some cases (e.g.: to update UBE Templates), but Server Packages can be deployed online, the build can be scheduled to run unattended with our PKGBUILD software, plus such Deployment can easily be automated with our AUTODEPLOY software, using our freeware UBE Commander.

For Interactive Application and Batch Version Updates, Data Selection changes or Version Queue Name overrides, a Server Package is not required. All you will need to do, to deploy such updates to the Fat Clients and Terminal / Citrix Servers, is to run Hot Deploy.

The tool is very easy to use: it accepts only 5 parameters: USER_NAME, PASSWORD, ENVIRONMENT for the sign-on, plus the PROJECT_NAME and, optionally, SOURCE_ENVIRONMENT. The result of this operation is a refresh / update of the local specs in the specified ENVIRONMENT for all qualified Objects from the specified Project.

Technical details: The specs will be read from the specified SOURCE_ENVIRONMENT (or ENVIRONMENT, if the SOURCE_ENVIRONMENT parameter is omitted) Central Objects database and will refresh the local TAM files in the ENVIRONMENT, which is equivalent to the OMW "Advanced Get" operation, so you must ensure that all the necessary specs exist in the Central Objects database in the specified SOURCE_ENVIRONMENT and are up to date. The Project should be at the status level of 21, as this is the status which has all of the default OMW rules defined for; a different status may be or may need to be used, depending on the OMW configuration. The PROJECT_NAME parameter can be case-sensitive, if your DB server is case-sensitive. This tool should not be used on the Deployment Server, as most versions of OW have a bug, where if an Object, that contains any C source or include files, is checked out from any Environment into itself (as opposed to performing an Advanced Get from a different Environment) on the Deployment Server, the source files in question are deleted from the target PathCode.

All OMW-enabled releases - XE through to E811 are supported.

This tool reports success or error, by setting the Windows® environment variable %ERRORLEVEL% for scripting support. We can help you create scripts, to be used with this software, to suit your specific requirements.

You can see some user responses here, you are also welcome to post your own experiences with our software to the same forum. Reference sites are available.

Technical details: A Limited Trial version is available upon request, that can only run on a single non-TSE Fat Client computer with a pre-defined name, which makes it unsuitable for production use, but allows to test the functionality of the product.