| # Components definitions The next step is the definition of components you want to use throughout the modeling process. A component is a collection of applications, or just one application, and their related data that is needed to interact with other applications. A component is a shell that accommodates the applications that can be linked to activities in business processes to define the work and sequence of work that must be carried out. The definition of the applications is important in the component procedure, because the definition of the applications determines the operations that must be completed. Components (tgbrg5157m000) To create and maintain components, use the Components (tgbrg5157m000) session. If you define one of the LN releases as a component, and therefore all the LN sessions of that release as applications, you must select the correct release in the Component Type field. The information in this field is used in the Application Conversion procedure to provide the Fill Conversion of Applications (tgbrg5250m000) session with data to carry out a conversion according to coding standards. The conversion procedure lets you reuse applications from older Baan releases in your current component release. To define a component, complete the following steps: Click the New In the Component field, specify the name of the component. In the Component Release field, specify the release, which is the identification of the issue of a component. In the Component Icon (16x16) field, select an icon that represents the component in the Process View, Enterprise Modeler Editor, and Process Browser. In the Process View, and the EME, the icon will be placed next to the activity of type application so you can distinguish the component to which the application belongs. In the Component Type field, select the identification for the component for application conversion purposes. Select the correct ERP release in the case of an ERP component. In case of a non-ERP component, select Other In the Client/Server field, select whether the component is installed on the server or on a client. In the Interface field, select the interface needed by the component, COM or Command line. In the Executable field, specify the executable in case of a command line interface. See the example. Specify the program ID in the Program ID field that is needed by Com to identify the component. The program identification is in the COM interface specification of the component release. If you use more than one LN component in your business processes, you must define an executable for every component, except the running LN component. Example Components: Executable LN Running ERP component ERP Baan 5.0b `C:\ProgramFiles\Baan\Bw4\bin\bwGrieg.exe` ERP Baan IVc `C:\Program Files\Baan\Bw4\bin\bw4.exe` For more information about the options you can use when creating or modifying a component, see the following table:
Key fields for the Components (tgbrg5157m000) session
Field | Description
--- | ---
Running ERP Component | If this check box is selected, the component is the LN component that provides the LN sessions at run time. For more information, see the DEM Parameters (tgbrg0135s000) session.
Applications defined in the running LN component are started directly and need no interface defined in the Runtime Details groupbox. On the Support for tab of the Components (tgbrg5157m000) session, you can select Authorizations, such as display and print. This is only applicable for the Running LN component, because it is meant for specifying the limitations to the authorization types during modeling later on. |