Codeless Server Administration Manual

Transcription

1 Codeless Server Administration Manual PDF generated using the open source mwlib toolkit. See for more information. PDF generated at: Tue, 12 Aug :37:19 CEST

2 Contents Articles 1. Revisions 1 1. Revisions 1 2. Introduction 2 2. Introduction 2 3. Starting the Administration Page 3 3. Starting the Administration Page 3 4. Server Monitor 4 4. Server Monitor 4 5. Server Options 8 5. Server Options 8 6. Server Information Server Information Server configuration Server configuration Class information Class information Database Management Database Management 14 References Article Sources and Contributors 21 Image Sources, Licenses and Contributors 22

3 1 1. Revisions 1. Revisions Revisions: Version Date Author Modification /09/2011 Veronica Chiritoiu Initial document /09/2011 George Melinte Updated print screens. Added chapters Server Configuration and Class Information /11/2013 Teofil Cobzaru Add Database management chapter /11/2011 Teofil Cobzaru Database management add information about resetting Server after changing persistency.

4 2 2. Introduction 2. Introduction Introduction The following manual is a user guide to Codeless Server Administration. After reading through this manual, the user should be familiar with the Codeless server administration functionality and its usage.

5 3 3. Starting the Administration Page 3. Starting the Administration Page Starting the Administration Page The Administration Page can be started accessed Environment Page. After that the Codeless Admin pages should be open.

6 4 4. Server Monitor 4. Server Monitor Server Monitor Main (Stop, Drain Stop, Start, Reset) Regarding to the Server Monitor some buttons are available with the following functionalities: * Stop through this button the server will be stopped; the button Confirm should be pressed if you want to stop the server; *Drain Stop - trough this button the server takes a break and enters in maintenance mode; *Start - trough this button the server is started; *Reset - trough this button the server is recycled.

7 4. Server Monitor 5 Active Clients when this link is pressed all the active clients for the corresponding environment are shown; When the Select is pressed another page is open, and from here a certain user can be blocked. You can specify the user that will be blocked, the time (in minutes) for which the access is blocked and the message that should be displayed when that user wants to access the application. In order to save the data press the OK button. Blocked Users when this link is pressed all blocked users for the corresponding environment are shown; When the Select is pressed another page is open and from here a user can be unblocked. You can specify the user that will be unblocked and press OK button.

8 4. Server Monitor 6 Active Calls when this link is pressed all active calls for the corresponding environment are shown; For each call will be shown the type of the action (get object, get new object, modify object, add initialized object etc.), the function in which the action will take place, the state of the call, the duration and other specifications. When Select is pressed another page is opened and from here the user can cancel the selected call.

9 4. Server Monitor 7 Completed Calls - when this link is followed, all completed calls for the corresponding environment are shown. For each call, will be shown the type of the action (get object, get new object, modify object, add initialized object etc.), the function in which the action is taking place, the state of the call ( Completed ), duration and other specifications. When Select is pressed another page is opened and from here, the user can see more details about that call.

10 8 5. Server Options 5. Server Options when this link is pressed another page is open, here the user can set some options: the message that should appear when the server is in maintenance mode; enable the profiling; enable the attribute values; the users that are shown on the profiling page; the machine names that are shown on the profiling page; the function Ids that are shown on the profiling page.

11 5. Server Options 9

12 10 6. Server Information 6. Server Information - when this link is pressed another page opens, and from here the user can make some actions like: reset the loaded named users; reset the loaded meta classes; reset the loaded workflow rules; reset the loaded profiler rules; reset the server settings; refresh the version info;

13 11 7. Server configuration 7. Server configuration When this link is pressed a new page opens up in which the server administrator can check the configuration information for the managed server, like server addresses, connection strings, error handling information etc.:

14 12 8. Class information 8. Class information - when this link is pressed all classes for the corresponding environment are shown; For each class, will be shown the Class Id, Name, Model Version, Model Loaded (date time stamp), Model State, MslVersion, Msl Loaded (date time stamp), Msl State and Msl Error. The following actions are available for the server administrator: Reset All Meta When this button is pressed the metadata used by the server will be reset. Load All Meta When this button is pressed, all metadata used by the server will be loaded in the class information list. Compile all MSL By pressing this button all Msl statements used throughout the whole package are re-compiled based on the settings defined in the server configuration. Load all MSL By pressing this button all MSL information is loaded in the class information list.

15 8. Class information 13 Refresh - When this button is pressed the whole page is refreshed. Whenever the class information list is loaded or any of the actions from above are executed, each Class and Msl statement will be marked in a proper manner in the Class information list: Red if it generates an error, Green if it is ok Purple if the msl is ok but it was re-compiled a long time ago, so it is outdated. Each entry present in the class information list can be further analyzed by pressing the Select button, for the corresponding object. This will open up the following window in which the Class Details are displayed. Eventually the error messages are displayed either they are related to Compilation or Execution:

16 14 9. Database Management 9. Database Management Database Management The Database Management functionality replaces the older Database Checker stand-alone application. Using Database Management you can create/edit/delete class groups. Class groups are saved as xml files under Server Files\Class Groups folder, for easy migration between environments. Once a class group is selected, several actions become available: - Check if the classes require synchronization - Perform synchronization step - Change persistency level - Copy/Move/Delete data Database Management can be accesed from the Administrator page, by clicking on the corresponding link. Creating class groups On the Database Management page, you have the option of adding a new group. You must provide a name for the group, and select the classes you want to include in it. A list of all classes in the system will be available to select from.

17 9. Database Management 15 You can add/remove classes to group either individually, all classes at once or by specifying a range of class ids. A group has a name, a number of classes included and a persistency level. If all classes have the same persistency, the class group will have the same persistency level, otherwise its persistency level will be Various. You can also edit and delete already created groups.

18 9. Database Management 16 Performing actions on class groups Check classes This function checks if the database structures for the classes included in the group are synchronized with the classes metadata. This includes checking the table structure, views structure, permissions on stored procedures, Unicode support (see Unicode support), etc. everything that the Database Synchronizer checks during a normal Package Update. If a class requires synchronization, this will be indicated in the Needs sync column. Repair classes If at least one class needs synchronization, the Repair button will be enabled. You can use it to fix the classes that are out of sync. Change persistency This feature is available only for class groups with Concern or Company persistency. If the group s persistency is Company, using the Change persistency to CONCERN button will change the persistency to Concern. No further input is required.

19 9. Database Management 17 If the group s persistency is Concern, pressing the Change persistency to COMPANY button will lead to a page where you can associate run units with the company you want the data to be related to. After you made the selection, use the Apply button to perform the operation. After changing persistency, you must reset the Codeless Server (see section Server Monitor - Main (Stop, Drain Stop, Start, Reset))

20 9. Database Management 18 Copy/Move data This feature is available only for class groups with Concern or Company persistency. You can copy/move data between distinct run units and/or companies using the Copy/Move data button. If the group s persistency is Concern, you can copy/move data between different run units. You must select the source and target run units, and press Apply. You cannot copy or move data from and to the same run unit. If the group s persistency is Company, you can either copy/move data between two distinct companies from the same run unit, or between distinct run units and companies.

21 9. Database Management 19 Delete data This functionality is not available for groups with Various persistency. Use the Delete Data button. This will lead to a page where you can select what you want to delete. You can either delete all data (from all run units and companies), or select a specific run unit. If the group s persistency is Company, you can additionally select a specific company to delete data from. Unicode support Starting with version 3.2, Codeless supports Unicode data. In order to enable this feature, the setting SupportsUnicode must be set to 1 in the Environment database, T000Setting table.

22 9. Database Management 20 Once this change is done, you can use the Database Management to convert classes to Unicode. This operation is performed by checking and then repairing the classes. During the check, if a class has not yet been converted to Unicode and Unicode support is enabled, that class is detected as out of sync. You can synchronize it (thus converting it to Unicode) by pressing the Repair button (see section Repair classes). Known limitations Conversion to Unicode has several limitations: 1. If a class has too many attributes in the model, it is possible that the class cannot be converted to Unicode (due to SQL Server restrictions). You can test whether a class can be converted to Unicode or not by using the Check classes functionality (described in section Check classes) and opting to check if conversion to Unicode is possible. If a class cannot be converted to Unicode, you may have to make changes to the model in order to reduce its size (in terms of total attributes length). 2. If you have a lot of data in your system, you will require a considerable amount of disk space for Unicode conversion (this is related to how SQL Server operates). Also, some versions of SQL Server (like SQL Server Express) will not be supported in this case.

23 Article Sources and Contributors 21 Article Sources and Contributors 1. Revisions Source: Contributors: DanielPopescu 2. Introduction Source: Contributors: AnaTurcan, DanielPopescu 3. Starting the Administration Page Source: Contributors: AnaTurcan, DanielPopescu 4. Server Monitor Source: Contributors: AnaTurcan, DanielPopescu 5. Server Options Source: Contributors: AnaTurcan, DanielPopescu 6. Server Information Source: Contributors: AnaTurcan, DanielPopescu 7. Server configuration Source: Contributors: AnaTurcan, DanielPopescu 8. Class information Source: Contributors: AnaTurcan, DanielPopescu 9. Database Management Source: Contributors: AnaTurcan, DanielPopescu

24 Image Sources, Licenses and Contributors 22 Image Sources, Licenses and Contributors File:Server Admin1.png Source: License: unknown Contributors: AnaTurcan File:Server Admin2.png Source: License: unknown Contributors: AnaTurcan File:Server Admin3.png Source: License: unknown Contributors: AnaTurcan File:Server Admin4.png Source: License: unknown Contributors: AnaTurcan File:Server Admin7.png Source: License: unknown Contributors: AnaTurcan File:Server Admin5.png Source: License: unknown Contributors: AnaTurcan File:Server Admin6.png Source: License: unknown Contributors: AnaTurcan File:Server Admin8.png Source: License: unknown Contributors: AnaTurcan File:Server Admin9.png Source: License: unknown Contributors: AnaTurcan File:Server Admin10.png Source: License: unknown Contributors: AnaTurcan File:Server Admin11.png Source: License: unknown Contributors: AnaTurcan File:Server Admin12.png Source: License: unknown Contributors: AnaTurcan File:Server Admin13.png Source: License: unknown Contributors: AnaTurcan File:Server Admin14.png Source: License: unknown Contributors: AnaTurcan File:Server Admin15.png Source: License: unknown Contributors: AnaTurcan File:Server Admin16.png Source: License: unknown Contributors: AnaTurcan File:Server Admin17.png Source: License: unknown Contributors: AnaTurcan File:Server Admin18.png Source: License: unknown Contributors: AnaTurcan File:Server Admin19.png Source: License: unknown Contributors: AnaTurcan File:Server Admin20.png Source: License: unknown Contributors: AnaTurcan File:Server Admin21.png Source: License: unknown Contributors: AnaTurcan File:Server Admin 100.png Source: License: unknown Contributors: AnaTurcan File:Server Admin 101.png Source: License: unknown Contributors: AnaTurcan File:Server Admin 102.png Source: License: unknown Contributors: AnaTurcan File:Server Admin 103.png Source: License: unknown Contributors: AnaTurcan File:Server Admin 104.png Source: License: unknown Contributors: AnaTurcan File:Server Admin 105.png Source: License: unknown Contributors: AnaTurcan File:Server Admin 106.png Source: License: unknown Contributors: AnaTurcan File:Server Admin 107.png Source: License: unknown Contributors: AnaTurcan File:Server Admin 108.png Source: License: unknown Contributors: AnaTurcan File:Server Admin 109.png Source: License: unknown Contributors: AnaTurcan File:Server Admin 110.png Source: License: unknown Contributors: AnaTurcan File:Server Admin 111.png Source: License: unknown Contributors: AnaTurcan File:Server Admin 112.png Source: License: unknown Contributors: AnaTurcan File:Server Admin 113.png Source: License: unknown Contributors: AnaTurcan File:Server Admin 114.png Source: License: unknown Contributors: AnaTurcan File:Server Admin 115.png Source: License: unknown Contributors: AnaTurcan File:Server Admin 116.png Source: License: unknown Contributors: AnaTurcan File:Server Admin 117.png Source: License: unknown Contributors: AnaTurcan File:Server Admin 118.png Source: License: unknown Contributors: AnaTurcan File:Server Admin 119.png Source: License: unknown Contributors: AnaTurcan File:Server Admin 120.png Source: License: unknown Contributors: AnaTurcan