In this section: |
When the server accesses a data source, it needs to know how to interpret the data stored there. For each data source the server will access, you create a synonym that describes the structure of the data source and the server mapping of the Lotus Notes data types.
How to: Reference: |
Synonyms define unique names (or aliases) for each Lotus Notes object that is accessible from the server. Synonyms are useful because they hide the underlying data source location and identity from client applications. They also provide support for extended metadata features of the server, such as virtual fields and additional security mechanisms.
Using synonyms allows an object to be moved or renamed while allowing client applications to continue functioning without modification. The only modification required is a redefinition of the synonym on the server. The result of creating a synonym is a Master File and an Access File, which represent the server metadata.
For the adapter to be able to create synonyms, Lotus Notes documents and data must be accessible to the HTTP client.
To create a synonym, you must have previously configured the adapter. You can create a synonym from the Web Console or the Data Management Console.
or
From the Data Management Console, right-click an application directory, then select New, and then Synonym.
The Select adapter to configure or Select connection to create synonym pane opens.
The first of a series of synonym creation panes opens.
The Status pane indicates that the synonym was created successfully.
The synonym is created and added under the specified application directory.
Note: When creating a synonym, if you choose the Validate check box, the server adjusts special characters and checks for reserved words. For more information, see Validation for Special Characters and Reserved Words.
The following list describes the parameters for which you will need to supply values, and related tasks you will need to complete in order to create a synonym for the adapter. These options may appear on multiple panes. To advance from pane to pane, click the buttons provided, ending with the Create Synonym button, which generates the synonym based on your entries.
Step 1
Your previously specified connection information appears at the top of the pane. Notice that Domino Server host is indicated as <local>.
In the Local Database Full Name box, enter the name of the database you wish to use.
Complete Step 1 by clicking the Next button.
Step 2: Synonym field name processing options
Select options from this pane as needed.
Select the Validate check box if you wish to convert all special characters to underscores and perform a name check to prevent the use of reserved names. (This is accomplished by adding numbers to the names.) This parameter ensures that names adhere to specifications. See Validation for Special Characters and Reserved Words for more information.
When the Validate option is unchecked, only the following characters are converted to underscores: '-'; ' '; ' \'; '/'; ','; '$'. No checking is performed for names.
Select the Make unique check box if you wish to set the scope for field and group names to the entire synonym. This ensures that no duplicate names are used, even in different segments of the synonym. When this option is unchecked, the scope is the segment.
Select an application directory. The default value is baseapp.
If you have tables with identical table names, assign a prefix or a suffix to distinguish them. For example, if you have identically named human resources and payroll tables, assign the prefix HR to distinguish the synonyms for the human resources tables. Note that the resulting synonym name cannot exceed 64 characters.
If all tables and views have unique names, leave the prefix and suffix fields blank.
To specify that this synonym should overwrite any earlier synonym with the same fully qualified name, select the Overwrite existing synonyms check box.
Note: The connected user must have operating system write privileges in order to recreate a synonym.
Step 2 (continued): The objects retrieved from the database you selected in Step 1 are listed in the table at the bottom of the pane. You can now select objects to create synonym(s).
This column displays the name that will be assigned to each synonym. To assign a different name, replace the displayed value.
If this box is checked, all Lotus alpha fields are created as An, where n is specified in the Alpha Field Size column.
If this box is unchecked, all Lotus alpha fields are created as AnV (the default), where n is specified in Alpha Field Size column.
Displays the length of the alpha fields. The default length is 127. You can change this value. The generated Master File will reflect the chosen field length.
Displays the name of the database that contains the selected objects.
Lists the names of the objects for which you can generate synonyms. (The default synonym name is the same as the object name.)
Indicates whether the object is a form, view, folder, or calendar.
Select objects for which you wish to create synonyms:
From the Web Console or the Data Management Console, right-click the configured Lotus Notes connection and choose Create Synonym from the menu. The first synonym creation pane opens:
The synonym is created and added under the specified application directory (baseapp is the default).
A status window displays the message: Created successfully
Generated Master File for Mail_Events form in the local log.nsf database
FILENAME=MAIL_EVENTS, SUFFIX=LOTUS , $
SEGMENT=MAIL_EVENTS, SEGTYPE=S0, $
FIELDNAME=UNID, ALIAS=UNID_KEY, USAGE=A32, ACTUAL=A32, $
FIELDNAME=BODY, ALIAS=Body, USAGE=A127V, ACTUAL=A127V,
MISSING=ON, $
FIELDNAME=FINISHTIME, ALIAS=FinishTime, USAGE=HYYMDs, ACTUAL=A17,
MISSING=ON, $
FIELDNAME=STARTTIME, ALIAS=StartTime, USAGE=HYYMDs, ACTUAL=A17,
MISSING=ON, $
FIELDNAME=SERVER, ALIAS=Server, USAGE=A127V, ACTUAL=A127V,
MISSING=ON, $
Generated Access File
SEGNAME=MAIL_EVENTS, CONNECTION=CON3,DATABASE=log.nsf,OBJECT=Mail Events, OBJTYPE=FORM, KEYNAME=UNID_KEY, $
The following list describes the parameters for which you will need to supply values, and related tasks you will need to complete in order to create a synonym for the adapter. These options may appear on multiple panes. To advance from pane to pane, click the buttons provided, ending with the Create Synonym button, which generates the synonym based on your entries.
Step 1
Your previously specified connection information appears at the top of the pane: Domino Server, port, and user ID. You can now specify the databases you want to retrieve from the remote Domino server.
Complete Step 1 by clicking the Next button.
Step 2
Your database filtering criterion appears at the top of the pane, and the list of databases that meet the criterion appears in a drop-down list at the bottom. In this step you specify a particular database and request retrieval of one, all, or a filtered list of the objects it contains.
Complete Step 2 by clicking the Next button.
Synonym field name processing options (Step 3)
Select options from this pane, as needed.
Select the Validate check box if you wish to convert all special characters to underscores and perform a name check to prevent the use of reserved names. (This is accomplished by adding numbers to the names.) This parameter ensures that names adhere to specifications. See Validation for Special Characters and Reserved Words for more information.
When the Validate option is unchecked, only the following characters are converted to underscores: '-'; ' '; ' \'; '/'; ','; '$'. No checking is performed for names.
Select the Make unique check box if you wish to set the scope for field and group names to the entire synonym. This ensures that no duplicate names are used, even in different segments of the synonym. When this option is unchecked, the scope is the segment.
Select an application directory. The default value is baseapp.
If you have tables with identical table names, assign a prefix or a suffix to distinguish them. For example, if you have identically named human resources and payroll tables, assign the prefix HR to distinguish the synonyms for the human resources tables. Note that the resulting synonym name cannot exceed 64 characters.
If all tables and views have unique names, leave the prefix and suffix fields blank.
To specify that this synonym should overwrite any earlier synonym with the same fully qualified name, select the Overwrite existing synonyms check box.
Note: The connected user must have operating system write privileges in order to recreate a synonym.
(Step 3 continued) The objects retrieved from the database you selected previously (either in step1 or step 2) are listed in the table at the bottom of the pane. You can now select objects to create synonym(s).
This column displays the name that will be assigned to each synonym. To assign a different name, replace the displayed value.
If this box is checked, all Lotus alpha fields are created as An, where n is specified in the Alpha Field Size column.
If this box is unchecked, all Lotus alpha fields are created as AnV (the default), where n is specified in Alpha Field Size column.
Displays the length of the alpha fields. The default length is 127. You can change this value when a synonym is created. The generated Master File will reflect the chosen field length.
Displays the name of the database that contains the selected objects.
Lists the names of the objects for which you can generate synonyms. (The default synonym name is the same as the object name.)
Indicates whether the object is a form, view, folder, or calendar.
Select objects for which you wish to create synonyms:
From the Web Console or the Data Management Console, right-click the configured Lotus Notes connection and choose Create Synonym from the menu. The first synonym creation pane opens:
The synonym is created and added under the specified application directory (baseapp is the default).
A status window displays the message: Created successfully
Generated Master File for the By _User_Name view in the certlog.nsf database
FILENAME=BY_USER_NAME, SUFFIX=LOTUS , $
SEGMENT=BY_USER_NAME, SEGTYPE=S0, $
FIELDNAME=USER_NAME, ALIAS=1, USAGE=A127V, ACTUAL=A127V,
MISSING=ON, $
FIELDNAME=LICENSE, ALIAS=2, USAGE=A127V, ACTUAL=A127V,
MISSING=ON, $
FIELDNAME=NOT_VALID_BEFORE, ALIAS=3, USAGE=A127V, ACTUAL=A127V,
MISSING=ON, $
FIELDNAME=CERTIFIER, ALIAS=4, USAGE=A127V, ACTUAL=A127V,
MISSING=ON, $
FIELDNAME=NOT_VALID_AFTER, ALIAS=5, USAGE=A127V, ACTUAL=A127V,
MISSING=ON, $
Generated Access File
SEGNAME=BY__USER_NAME, CONNECTION=CON1, DATABASE=certlog.nsf, OBJECT=By_User Name, OBJTYPE=VIEW, $
A UNID field is automatically added to Master Files generated for Forms.
The Universal Note ID (UNID) identifies all copies of a note, regardless of location or time.
As a result, every replica of the note has the same UNID, which does not change when a note is modified.
(This field is illustrated in Creating a Synonym for a Form in a Local Lotus Notes Database.)
Once you have created a synonym, you can right-click the synonym name in the Adapter navigation pane of either the Web Console or the Data Management Console to access the following options.
Option |
Description |
---|---|
Open |
Opens the Master File for viewing and editing using a graphical interface. If an Access file is used it will be also available. |
Edit as Text |
Enables you to view and manually edit the Master File synonym. Note: To update the synonym, it is strongly recommended that you use the graphical interface provided by the Open option, rather than manually editing the Master File. |
Edit Access File as Text |
Enables you to view and manually edit the Access File synonym. Note: This option is available only when an Access File is created as part of the synonym. |
Sample Data |
Retrieves up to 20 rows from the associated data source. |
Data Profiling |
Data Profiling provides the data characteristics for synonym columns. Alphanumeric columns provide the count of distinct values, total count, maximum, minimum, average length, and number of nulls. Numeric columns provide the count of distinct values, total count, maximum, minimum, average value, and number of nulls. |
Refresh Synonym (if applicable) |
Regenerates the synonym. Use this option if the underlying object has been altered. |
Data Management |
Followed by these options, if applicable: Recreate DBMS Table. Recreates the data source table. You are asked to confirm this selection before the table is regenerated. (Note that the table will be dropped and recreated. During the process, data may be lost.) Delete All Data. Deletes all existing data. You are asked to confirm this selection before the data is deleted. Insert Sample Data. Inserts specified number of sample records, populating all fields with counter values. Reorganize. Recreates the data source table preserving original data. Note: This option is not available in the Web Console. |
Impact Analysis |
Generates reports on procedures, synonyms, and columns that provide information on the flows/stored procedures available on a particular server, and the synonyms and columns they use. These reports enable you to evaluate changes before they are made by showing which components will be affected. See the Server Administration for UNIX, Windows, OpenVMS, IBM i, and z/OS manual for details about Impact Analysis Reports. |
Copy |
Copies the synonym to clipboard. |
Delete |
Deletes the synonym. You are asked to confirm this selection before the synonym is deleted. |
Cut |
Deletes the synonym and places it in clipboard. |
Properties |
Displays the properties of the synonym, including physical location, last modified date, description, and privileges. |
Keyword |
Description |
---|---|
SEGNAME |
Value must be identical to the SEGNAME value in the Master File. |
CONNECTION |
Indicates access to the previously declared connection. The syntax is: CONNECTION=connection |
DATABASE |
Identifies the Lotus Notes database file. |
OBJECT |
Specifies the name of a Lotus Notes object. |
OBJTYPE |
Indicates the type of Lotus Notes object: FORM, VIEW, FOLDER, or CALENDAR. |
The following table indicates how the server maps Lotus Notes data types.
Lotus Notes Data Type |
USAGE |
ACTUAL |
Remarks |
---|---|---|---|
Text Dialog List Checkbox Radio Button List Box Combo Box Authors Names Readers Password Formula
|
AnV | An |
AnV | An |
n is specified by user (default is 127). |
Date/Time |
HYYMDs |
A17 |
|
Number |
D16 |
D8 |
|
Rich Text |
|
|
BLOB (Binary Large Object) format is supported as a component of the Rich Text data type, which is used to distribute e-mail attachments. The attachment portion uses the BLOB format in the Master File. BLOB format is supported through the Reporting Server API. For an illustration, see Mapping the Rich Text Data Type. |
Rich text fields are used for large amounts of text or to embed or attach objects. For example, the Body field on a mail form is a rich text field that is mapped to three fields in the following Master File
FIELDNAME=BODY_ATTACHMENT, ALIAS=Body_ATTACHMENT, USAGE=BLOB, ACTUAL=BLOB, MISSING=ON, $ FIELDNAME=BODY_FNAME, ALIAS=Body_IZHBOPIA, USAGE=A256, ACTUAL=A256, MISSING=ON, $ FIELDNAME=BODY, ALIAS=Body, USAGE=A25V, ACTUAL=A25V,MISSING=ON, $
where:
Is a BLOB field used to store the attachment. BLOB format is supported through the Reporting Server API.
Is the file name of the original attachment.
Is the text in the field. For large amounts of text, you can manually modify the USAGE and ACTUAL lengths in the Master File.
Note: Formatted text, another common use of the rich text data type, is not currently supported by the adapter.
iWay Software |