Fundamentación disciplinar más profunda

In order to use the subsystem model files, load the appropriate model file into Developer.

ROC and Ad Hoc Files

These model files are intended to be loaded into Developer as individual Business Segments. This means you need to load the required file only once and can create a consistent look across all the relevant screens to be accessed by your runtime

ROC-A ROC-N ROC-T ROC-H ROC-O ROC-W ROC-I ROC-P ROC-X ROC-M ROC-S

ROC-A ROC-L ROC-R ROC-C ROC-M ROC-T ROC-F ROC-N ROC-W ROC-H ROC-O ROC-X ROC-I ROC-P

ADH-A ADH-F ADH-K ADH-B ADH-G ADH-L ADH-C ADH-H ADH-M ADH-D ADH-I ADH-S ADH-E ADH-J

The ROC files also include a number of Insertable Global Logics containing one or more painted items. They may be used in several Components or several times in the same Component.

Note: If you delete fields from a screen it will not work correctly.

You can use Builder to perform a Component Enabler Bundle generate of the required screens. This requires you to have Component Enabler installed on your machine. See your Enterprise Application Builder Guide for further details.

Builder generates only the graphical screens for the Ispecs. You cannot perform a full System generate of a subsystem Business Segment. This means that adding logic to or changing options of objects has no impact on the generated product.

Note: You must have a ROC-capable runtime system deployed on the host in order to use the model files to add ROC screens to your system. You must also have generated Bundles for the runtime system for use with the Presentation Client. See your Enterprise Application Component Enabler Developer’s Guide for information on the Presentation Client.

Java based generators are removed from the Client Tools AB Suite release. The EAE Developer is modified to invoke the C# generator dll's instead of the Java generators. The clients supported by AB Suite Client Tools cannot be generated using Java based Generators any more. The EAE Developer will still support bundle generate using customized Java Generators developed by users. When the User Defined View Generator property is blank or unspecified, as default:

• The Presentation Client view generator for C# version, GenerateForm.dll is invoked.

• To invoke the customized Java based Generator, the Jave Class name needs to be specified with fully qualified name.

To use a ROC or Ad Hoc file:

1. Load the required file into Developer. A Business Segment is added to the model.

2. Optionally, use Developer Painter to paint the desired Ispec screens.

3. In the Systems directory, add a new System selecting the Business Segment containing the painted ROC or Ad hoc Ispecs.

Create a Generate Set for the System with the appropriate host type.

4. Double-click the Business Segment node of the newly created System, to display the Business Segment options dialog box.

5. On the Component Enabler tab, check the Component Enabler Capable check box.

6. For MCP, Windows, and UNIX hosts; specify the same Application Name,

Package Prefix, and Output Directory as you specified for the runtime system.

For OS 2200 hosts; specify the same Package Prefix and Output Directory as you specified for the runtime system. For the Application Name, specify the ROC system name for the host environment (see your system administrator for the system name under which ROC has been installed).

7. Create a Component Enabler Bundle containing the required Ispecs.

You must use the same name as used for the Bundle in the runtime system. 8. Perform a Bundle generate. The graphical screens for the Ispecs in the Bundle are

generated.

9. Copy the generated .CLASS and .ASP files to the location wfrom here the IIS server will use them.

Note: The generated SelectIspec.asp file should NOT be copied because the newly generated file contains only the roc screens.

Note: On ClearPath OS 2200, ROC is a separate Enterprise Application Environment system. This means that when ROC is invoked it is "switched to", and when you exit (BY) ROC you are switching back to the original system.

As part of the switch, the name of the application being switched to is passed to the client used to access the correct Component Enabler components.

When switching to and from ROC, the application name sent is the name the system was deployed as on the host.

For switching to work correctly, the application name used to generate the

Component Enabler components must be the same as the name used to deploy the system.

The SEC-T File

The SECTOS2200.mdl file is different from the other subsystems in that it must be included as part of a system. The file is a partial extract file so you can load it into an existing Business Segment. This enables you to paint a different graphical screen for each system in which it is included.