Configuring Auto Spec Generation
To configure auto-generating of serialized objects:
In Server Manager, select the HTML/JAS server that you wish to enable auto-generating serialized objects.
- Navigate to Configuration > Advanced > Miscellaneous > Automatic Spec Generation Settings
- Complete the following fields:
- Automatic Spec Generation
Set this to true to enable automatic pre-generation of serialized objects.
The default value is false.
- Max thread pool size
Enter a value to specify the thread pool size to pre-generate serialized objects concurrently using automatic spec generation. Valid values are from 1 to 30, where the default value is 10.
- Generate Spec For Frequently Used Object (Release 9.2.8.2)
Select the Generate Spec For Frequently Used Object check box to generate specs for the previously accessed objects. Frequently used objects are determined based on the data available in the Object Usage Tracking table (F98911). These specs will be generated when the server starts.
- Language Preference (Release 9.2.8.2)
Select the Language Preference for serialized object. Select NONE if only the default English language serialized objects are required. You can select multiple languages to generate specs for different languages. NONE must not be selected along with other languages.
- Applications To Generate
The default value is blank (no specific applications will be pre-generated).
Optionally you can list a specific application, list of applications, or all applications to be automatically pre-generated. Multiple application names must be specified with comma separators. To pre-generate specs for all applications, use the * character.
For example, any of these are valid values:
- P01012 (single application)
- P01012, P4210, P0911, P40G30 (multiple applications)
- * (all applications)
- Reports To Generate
The default value is blank (no specific reports will be pre-generated).
Optionally you can list a specific report, list of reports, or all reports to be automatically pre-generated. Multiple report names must be specified with comma separators. To pre-generate specs for all reports, use the * character.
For example, any of these are valid values:
- R0008P (single report)
- R0008P, R0010P (multiple reports)
- * (all reports)
- NERs To Generate
The default value is blank (no specific NERs will be pre-generated).
Optionally you can list a specific NER, list of NERs, or all NERs to be automatically pre-generated. Multiple NER names must be specified with comma separators. To pre-generate specs for all NERs, use the * character.
For example, FetchUBEMapping.
- Business Views To Generate
The default value is blank (no business views will be pre-generated).
Optionally you can list a specific business view, list of business views, or all business view to be automatically pre-generated. Multiple business view names must be specified with comma separators. To pre-generate specs for all business views, use the * character.
For example, any of these are valid values:
- V9001B (single business view)
- V9001B, V0101E (multiple business views)
- * (all business views)
- Tables To Generate
The default value is blank (no tables will be pre-generated).
Optionally you can list a specific tables, list of tables, or all tables to be automatically pre-generated. Multiple table names must be specified with comma separators. To pre-generate specs for all tables, use the * character.
For example, any of these are valid values:
- F9860 (single table)
- F9860, F9210 (multiple tables)
- * (all tables)
- Data Dictionaries To Generate
The default value is blank (no data dictionaries will be pre-generated).
Optionally you can list a data dictionary, list of data dictionaries, or all data dictionaries to be automatically pre-generated. Multiple data dictionaries names must be specified with comma separators. To pre-generate specs for all tables, use the * character.
- Product Code Specific Objects To Generate (Release 9.2.8.2)
The default value is blank (no product code specific objects will be pre-generated).
Optionally, you can list product codes for which specs must be generated. Multiple product code names must be specified with comma separators.
For example, any of the following are valid values:
- 01 (single product code)
- 02, 03 (multiple product codes)
Note: The * character does not apply to this field.
- Automatic Spec Generation
