JavaBeans Enterprise
Paso 5: Crear el Fichero ejb-jar
AVEVA Engineering provides capabilities configure more elaborate rules for element matching and updating, in particular key attribute mapping to match multiple pipes against schematic or engineering pipelines. In this worked example AVEVA Engineering data will be compared against data created in AVEVA Design and stored Design database.
‘Th e Advance d Configuration utilize sth e ‘Inte gratorProje ct Configuration Ex p lore r’To illustrate this; Enter AVEVA Engineering-Tags module asPROCENGuser “B” with the following details:
Username:B. PROCENG; Password:B; MDB:A-TAGS
Open ‘Lines list’ list view from Process Lines category.
Click the Compare/Update/Linkbutton located on the ‘Manage’ toolbar to display the secondary buttons, then the ‘Open’ to bring up a dialogue prompt and display a new contextualCompare/Update Actionstab on the ribbon bar.
Compare/Update dialog is then displayed. Clicking the Compare/Updatecontextual tab, displays a ribbon bar with its menu items containing the dedicated ‘Compare/Update’ controls.
Select the ‘Design Database’ from the picklist. An initial (first time) selection of a source database will have a ‘Compare / Update’ information prompt form displayed.
This prompt alerts to apply Filters, Click the ‘NO’ button to eliminate the form, and proceed with the configuration setup.
www.aveva.com
Click the ‘Options’ button in the ‘Configuration’ group, to display the Options form.
Click the ‘Options’ button to Display the ‘Options’ form, and then click on ‘Configuration Explorer…’
button to display the ‘Integrator Project Configuration Explorer’ window.
Select and right click the entry ‘Rule Sets‘, to display its context menu, and click ‘Insert‘ to create a new empty Rule Set.
Type in ‘Design/Engineering RuleSet’ for the ‘Name’. SelectDESIfrom the ‘Source DB type’ picklist, then selectENGI‘Target DB type’ picklist.
Select the newly created Rule Set and insert a new Rule group named: ‘Engineering pipeline rules‘ entry on the explorer, and pick the relevantSource element type(PIPE in this case) from the drop down list.
This defines the source element type.
www.aveva.com
Select the created Rule group, and insert a ‘Create Action’ entry from its context menu as shown. Select the type (:LINETAG in this case) from the picklist.
This specifies the target element type.
Select the created Rule group, and insert an ‘Assign Action’ entry from its context menu.
Type in ‘NAME’ for the name of the target (Engineering) attribute, and type in ‘LNTP of source + ‘-‘ + Dscode of source’ for the source attribute. Fill out the rest of the entries as shown.
This defines the rules for the Compare and Update actions.
Click on ‘File > Save’andexitto save and exit the project configuration explorer.
W ith th e se tup configuration, sh own, e ach tim e an Engine e ring Line tag iscom p are d against a De signClick the ‘OK’ button on the ‘Options’ form to exit the setup options.
For this section, create a new configuration which maps the source element type: ‘PIPE’ (using display name: 3D PIPES) with the Target element type :LINETAG. Map their attributes as shown.
Click the ‘Manage Configuration’ button on the Options form to initiate the first step (Step 1 of 6) ‘Compare / Update Configuration Wizard’.
Select the radio button ‘Create new configuration’, as the required action of the wizard, and then click on the ‘Next’ button to proceed to the next step.
www.aveva.com
(Step 2 of 6) Source Element Type.
Source: Select the entry ‘Design Database’ from the drop down list.
Display Name: Type the text ‘Design Pipeline’ in the text field.
Element Type: Select the radio button to utilise the element type, before selecting the entry ‘PIPE’ from the drop down list.
Name Attribute: Retain the default entry
‘Name’.
Unique Attribute: Retain the default entry
‘RefNo’.
Click on the ‘Next’ button to proceed to the next step.
(Step 3 of 6) Destination Element Type.
Element Type: Select the entry ‘:
LINETAG’from the drop down list.
Display Name: Type the text ‘Engineering Line’ in the text field.
Allow Insertion: Check the checkbox, to allow for the creation of new items in the target database.
Name Prefix: Retain the blank text field.
Create Reverse Configuration: Retain as unchecked.
Click on the ‘Next’ button to proceed to the next step.
(Step 4 of 6) Define Rule Set.
Th isste p isonly ap p licab le if th e Advance d Rule sisin use .Project Configuration File: Select the appropriate “Project Configuration”
(e .g.%TRNDFLTS%\Mode lManage m e nt\Proje ct Configuration.x m l). This is usually the default filename for the project.
Rule Set: Select the appropriate RuleSet e.g.
“Design/Engineering RuleSet” from the pull-down list.
Use Advanced Rules: Select the checkbox.
“In orde r to utilise th e ‘Advance Configuration Rules’for Compare/Update actions, th e ‘Use advanced configuration’ch e ckb ox m ust b e first ch e cke d.
Restrict this Configuration to Admin Users Only: Retain the unchecked checkbox.
Ch e ck “Restrict the Configuration to Admin Users Only”if th e Adm in Use rwant to te st th e configuration b e fore p ub lish ing it forge ne raluse on th e p roje ct.(Step 5 of 6) Define Source Filter(s).
Add Filter: Retain the default blank entries.
This allows for the definition of criteria which limits the sort of source data to be utilised for comparison.
Delete Filter: This button deletes any set filter.
Click on the ‘Next’ button to proceed to the next step.
www.aveva.com
(Step 6 of 6) Define Attribute Mapping(s)
Attributes of the source element types can now be mapped to those of the corresponding target engineering element type. Attribute selection and mapping indicates the attribute values to be obtained and/or compared against.
Click the ‘Finish’ button to exit the attribute mapping form, and save the configuration. Click the ‘OK’ button on the information prompt form, to exit the wizard and return to the ‘Options’ form.
From the ‘Compare/Update’ menu, select the source configuration e.g. ‘Design Pipeline’ which is now available in the group drop down list.
The results of the compare process will be displayed in the grid view. The values of the mapped attributes of a source (Design) item will be compared with the attributes values of any existing and matched corresponding target (Engineering) item.
The ‘Design Database Value’ for the ‘NAME’ attribute can now observed to display the concatenated attribute values as configured within the ‘Integrator Project Configuration Explorer’, hence allowing the their NAME attributes to be similar and no difference reported.
The target database can be updated with ‘new’ Pipe objects if required, as previously described.