How to Set Up the Production Environment

When setting up a USoft production environment, you make a number of decisions depending on the number of end-users, the complexity and use of the application, and on infrastructure and system management standards.

The following overview describes typical steps you need to take when you first deploy a new USoft application in a client/server production environment. For more details please refer to "Deploying Your Application" in the USoft DefinerHelp.. If you want information about deployment in architectures other than the conventional 2-tier client/server, refer to USoft online or printed help topics specific to your runtime architecture.

The purpose of this overview is to give you a general idea of the necessary steps. Many important issues are not covered here. These may include anything from user training and documentation, acceptance and performance testing, and data conversion to batch scheduling procedures.

Set up a production database. Ensure database connectivity for all client machines.

From the USoft development repository, generate flat files for the application. These include a .CON, an .EXT and an .ESI file. In addition, generate batch job files as appropriate, and collect other production files such as bitmap files and ActiveX controls.

Distribute the collected production files to each client machine. If the application relies on third-party components such as ActiveX controls, these may need to be registered and installed on each client machine.

In the production database, assign a database user as the application owner. It is in the account of this user that the application tables are going to reside.

From the USoft development repository, generate an installation script which will create the application tables. Create the application by running this script against the application owner's account.

Authorization for the production environment is set up in the same way as authorization for the development environment. That is:

·	USoft Authorization tables are created for the application owner.

·	Using these tables, end-users are registered and authorized by the application owner. In this way, authorization changes can be made dynamically (i.e. whilst the application is being used).

·	This way of working requires that appropriate end-user access rights to the application owner's are also granted at RDBMS level.

In addition to server-side authorization, you need to give end-users access to the application from their client machine.

·	Make sure that for all USoft Binder files in the production environment, you specify Project Type = "Production".

·	In the (Read) From field in the Application Properties dialog, make sure you specify "Flat Files", NOT "Repository". You also need to specify the application name in this dialog.

·	When specifying username, password and database string, you use the login and connection information of the team member, but in the Owner field you specify the application owner. If you don't, USoft Binder attempts to find the application tables in the end-user's own account.