Oracle eMail Server Administrator's Guide Release 5.2 A86653-01 |
|
To send e-mail to coworkers, schedule rooms and equipment, create e-mail distribution lists, and assign user aliases, you must have a comprehensive and accurate directory. Tasks for managing directory information include adding and modifying directory entries.
You should add, modify, and delete directory entries in the eMail Server Directory, rather than in Oracle Internet Directory, or any other LDAP directory. The eMail Server Directory is synchronized with Oracle Internet Directory (or other LDAP directory) by the LDAP server processes.
The following topics describe how to manage the eMail Server Directory:
See Also:
You can display any entry in your eMail Server Directory to verify information or determine whether information should be updated. You can display one item, selected items of a certain type, or all items of a certain type. The Administration Tool and OOMGR always display the information for all of the entries that meet your specifications.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
The results of the search appear in the lower portion of the right pane.
IOFCMGR>fetch <class
> <attribute
>=<value
>;
IOFCMGR>fetch person username=bhayden;
To create an e-mail account for an eMail Server user, you must insert a person
entry in the directory. Refer to "Creating a User for a Foreign E-mail System" or "Creating a User Without E-mail" for instructions on creating accounts for people who are not eMail Server users. The user's INBOX and other standard folders are created automatically on the node you specify as the user's home node (the uanode
attribute).
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
See Also:
"Guidelines for Creating an eMail Server User Account" for more information about performing this task |
IOFCMGR>insert person username=<username
> 2>lastname=<last_name
> firstname=<first_name
> password=<password
> 3>employeeID=<employee_id
> workphone="<work_phone
>" 4>office=<work_location
> homeaddress="<home_address
>" 5>homecity="<home_city
>" homestate=<home_state
> 6>homezip=<home_zip
> homecountry=<home_country
> homephone="<home_phone
>" 7>birthday=<birth_date
> language=<language
> mailstop=<work_mailstop
> 8>manager=<manager_username
> primaryrole="<role
>" 9>primaryorg=<org
> osname=<os_username
> uanode=<home_node
>;
This command displays a portion of the available attributes.
To create an eMail Server account for Amy Johnson with an e-mail account on hq_unix
, enter the following command:
IOFCMGR>insert person username=ajohnson 2>lastname=johnson firstname=amy password=changethis 3>employeeID=1887 workphone="415.555.3232" 4>office=HQ_Bldg homeaddress="456 Delmonico Circle" 5>homecity="San Francisco" homestate=California 6>homezip=94335 homecountry=US homephone="415.555.6755" 7>birthday=8/12/64 language=English mailstop=600 8>manager=bhayden primaryrole="Project Manager" 9>primaryorg=Design osname=ajohnson uanode=hq_unix;
kind
(default is Oracle
)
status
(default is open
)
quota
(default is the quota value established for the node; refer to "Manually Initializing a Node" for instructions for changing this quota)
location
entries before you can enter the work location for the office
attribute. Refer to "Creating a Location" for instructions.
To create an account for a user who uses a foreign e-mail system other than eMail Server, you can insert a person
entry in the directory. This means that your eMail Server users can exchange messages with the foreign users. You can define the same information for your foreign users as you do for your eMail Server users.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
See Also:
"Guidelines for Creating a User for a Foreign E-mail System" for more information about performing this task |
IOFCMGR>insert person username=<username
> 2>foreignstring=<qualified_foreign_username
> 3>lastname=<last_name
> firstname=<first_name
> 4>homephone="<home_phone
>" homefax="<home_fax
>" 5>workphone="<work_phone
>";
This command displays a portion of the available attributes.
See Also:
"Person Class Attributes" for a complete list of the person attributes and their descriptions |
IOFCMGR>insert person username=gnewell 2>foreignString=UNIX:newell@designco.com 3>lastname=newell firstname=glen 4>homephone="415.555.8564" homefax="415.555.2341" 5>workphone="415.555.2121";
location
entries before you can enter the location
attribute. Refer to "Creating a Location" for instructions.
To create an account for someone who does not use e-mail, you can insert a person
entry in the directory. This is useful if you want to include someone without e-mail in a meeting invitation, or if you want to make the names and phone numbers of outside contacts available in your directory.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
See Also:
"Guidelines for Creating a User Without E-mail" for more information about performing this task |
IOFCMGR>insert person username=<username
> homephone="<home_phone
>";
This command displays a portion of the available attributes.
See Also:
"Person Class Attributes" for a complete list of the person attributes and their descriptions |
To add Frank Lawson, the local representative for your company's health plan who does not use e-mail, enter the following command:
IOFCMGR>insert person username=flawson homephone="650.555.3172";
username
attribute is required. You can also enter values for logical attributes, such as homecity
and workphone
.
You can set or change users' passwords if they forget them, or if the password needs to be change for security reasons.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
See Also:
"Guidelines for Setting a User's Password" for more information about performing this task |
IOFCMGR>setpwd user name=<username
>
You must set a user's password on the user's home node.
You can create location
entries for places within your company. For example, the headquarters building for Global Business Services, Inc. could be a location. Users can use the location
entries to send messages to all users in a particular location.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
IOFCMGR>insert location name="<location_name
>" 2>administrator=<admin_username
> 3>description="<description
>";
This command displays a portion of the available attributes.
See Also:
"Location Class Attributes" for a complete list of the |
IOFCMGR>insert location name="HQ Bldg" 2>administrator=lsennett 3>description="headquarters building in Minneapolis";
name
attribute is required.
parent
attribute to specify a parent location.
location
entries before you can enter the location
attributes in the person
, room
, and equipment
entries.
You can create room
entries for designated areas within a location. For example, an office, conference room, or lab could be represented by a room
entry.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
IOFCMGR>insert room name="<room_name
>" 2>administrator=<admin_username
> type="<room_type
>" 3>location=<location> capacity=<capacity
> 4>description="<description
>" 5>uanode=<home_node
>;
This command displays a portion of the available attributes.
IOFCMGR>insert room name="Concourse Room" 2>administrator=lshea type="conference room" 3>location=ER_Bldg capacity=12 4>description="Eastern Region Meeting Room" 5>uanode=ny_unix;
name
attribute is required.
uanode
attribute.
location
entries before you can enter the location
attribute. Refer to "Creating a Location" for instructions.
You can create an organization
entry to group people within your system. Organizations differ from locations because they do not represent physical regions. For example, a Sales Organization may have locations throughout the world.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
See Also:
"Guidelines for Creating an Organization Entry" for more information about performing this task |
IOFCMGR>insert organization name=<organization_name
> parent=<parent_org
> 2>manager=<mgr_username
> administrator=<admin_username
> 3>costcenter=<cost_center
> mailstop=<work_mailstop
> 4>description="<description
>" 5>address="<address
>" city="<city
>" 6>state=<state
> zip=<zip_code
> country=<country
> 7>phone="<phone_number
>" faxnumber="<fax_number
>";
This command displays a portion of the available attributes.
See Also:
"Organization Class Attributes" for a complete list of the organization attributes and their descriptions |
IOFCMGR>insert organization name=Design parent=HN_Groups 2>manager=ajohnson administrator=lsennett costcenter=123 3>mailstop=600 description="Headquarters Design group" 4>address="111 Commerce Avenue" city="Houston" 5>state=California zip=78632 country=US 6>phone="888.555.2222" faxnumber="888.555.1111";
name
attribute is required.
You can create role
entries to group people who perform a certain function within the enterprise. For example, Manager and Lead Designer are two roles in the Global Business Services Inc. system. You can use roles as another means of identifying users and to create dynamic distribution lists.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
IOFCMGR>insert role name="<role_name
>" 2>description="<description
>";
This command displays a portion of the available attributes.
IOFCMGR>insert role name="Project Manager" 2>description="A Project Manager leads the product 3>development, and supervises one or more people.";
You can create an equipment
entry to define any resource, such as a projector, that the people in your enterprise can share. Once a piece of equipment is defined in the eMail Server Directory, your users can use eMail Server to schedule the use of the equipment.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
See Also:
"Guidelines for Creating an Equipment Entry" for more information about performing this task |
IOFCMGR>insert equipment name=<equipment_name
> 2>location="<location
>" administrator=<admin_username
> 3>type="<equipment_type
>" 4>movable={yes | no} uanode=<home_node
>;
This command displays a portion of the available attributes.
See Also:
"Equipment Class Attributes" for a complete list of the equipment attributes and their descriptions |
To enter data about a projector at the Houston office of Global Business Services, Inc., enter the following command:
IOFCMGR>insert equipment name=projector_1 2>location="WR_Bldg" administrator=lsennett 3>type="slide projector" 4>movable=yes uanode=HQSUN1;
name
attribute is required.
uanode
attribute).
location
entries before you can enter the location
attribute. Refer to "Creating a Location" for instructions.
You can create public aliases as short identifiers for people or other entries in the directory. You can use aliases to make it easier for your users to find other users and resources, such as rooms or equipment, and address messages to them. You can also use a public alias to temporarily reroute e-mail for a person whose account is being moved from one node to another.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
IOFCMGR>insert alias name=<alias_name
> 2>address=<actual_address
> description="<description
>";
This command displays a portion of the available attributes.
See Also:
"Public Alias Class Attributes" for a complete list of the public alias attributes and their descriptions |
To add a public alias for the fourth floor conference room in the 400HQ building, enter the following command:
IOFCMGR>insert alias name=Blue_Room 2>address=400HQ description="Name used by fourth-floor 3>users for the blue conference room on the fourth floor.";
address
and name
attributes are required.
address
attribute must be the name of an entry or account that currently exists in this domain. Therefore, you cannot add an address that contains a gateway (for example, ckent@acme.com
). If you want to create an alias for a user that contains a gateway, then you must create a foreign user account. Refer to "Creating a User for a Foreign E-mail System" for instructions.
equipment
, location
, organization
, person
, public distribution list, role
, and room
entries.
You can create a public distribution list for a list of users who should logically receive the same e-mail messages. A public distribution list has the same advantages that a role or an organization has because one message can be delivered to an entire group without having to specify individual user names. You can also use public distribution lists to replicate shared folders.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
See Also:
"Guidelines for Creating a Public Distribution List" for more information about performing this task |
"Public Distribution List Class Attributes" for more information about the values to enter
See Also:
IOFCMGR>insert dl name=<list_name
> 2>member=<item1
>, <item2
>, <item3
>, ... ;
This command displays a portion of the available attributes.
See Also:
"Public Distribution List Class Attributes" for a complete list of the public distribution list attributes and their descriptions |
IOFCMGR>insert dl name=HK_all 2>member=rgraham, pwong, jho, gchan, dwalden, 3>ccharles, amurray, bnash, jshu, lshipley;
name
attribute is required.
equipment
, location
, organization
, person
, public alias, role
, and room
entries.
You can create a public template to use as the electronic equivalent of a printed form. Users can use public templates to request information and services in a consistent manner.
The first step in creating a public template is to create a private template. To create a private template, you must have a client that supports creating server-side templates.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
See Also:
"Guidelines for Creating a Public Template" for more information about performing this task |
IOFCMGR>publish template owner=<username
> 2>oldname=<private_template_name
> 3>[newname=<new_template_name
>];
All users with clients that support creating templates can create their own private templates for personal use. Only the system administrator can convert a private template to a public template, making it available to all users.
You can display the access privileges of users, organizations, and roles, to determine what kind of administrative or other system-use privileges they have.
This task can only be performed through the OOMGR command-line interface.
To check the privileges that the user llane
has for the ckent
directory entry, enter the following command:
IOFCMGR>check user=llane item=ckent
The following results appear:
Privileges Grantee Class Item ---------- ------- ------ ----- LSS----- llane person ckent l may list objects in directory browser s may address message to object s may save listing of object from directory browser a has administrative privileges over domain d may discover folder hierarchy from client v may view folder contents m has moderator privileges on folder c may create child folders Lower case characters indicate inherited privileges. Upper case characters indicate explicit privileges.
The first line of the results contains the following information:
You can grant privileges to any directory entry such as a person
or an organization
, providing that entry with certain administrative or other system-use abilities.
This task can only be performed through the OOMGR command-line interface.
See Also:
"Guidelines for Granting Access Privileges" for more information about performing this task |
See Also:
|
You can grant the following access privileges:
child
privilege, and you grant that user the discover
privilege, the user still has the child
privilege. If you want to restrict access to certain folders for a user, you should first revoke that user's current privileges and then grant the privileges that you want the user to have.
admin
privileges to any eMail Server account.
admin
privileges, keep the following in mind:
admin
privileges to an account on another node.
person
object.
admin
privilege to a user causes the new privilege to mask out the default privileges so that the user no longer has access to the subfolders. To work around this issue, grant the user's admin privileges before creating the subfolders.
You can revoke privileges to users, organizations, and roles, taking away their administrative or other system-use abilities.
This task can only be performed through the OOMGR command-line interface.
See Also:
"Guidelines for Revoking Access Privileges" for more information about performing this task |
See Also:
|
send
privilege for the person will not prevent the user from sending to the list. To prevent the user from sending to the list, the send
privilege must be revoked from the user's role, or the user's role must be changed.
child
privilege, and you grant that user the discover
privilege, the user still has the child
privilege. If you want to restrict access to certain folders for a user, you should first revoke that user's current privileges and then grant the privileges that you want the user to have.
You can delete any entry that you no longer want to appear in your eMail Server Directory.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
IOFCMGR>delete <class
> <key_attribute
>=<value
>
IOFCMGR>delete person username=rlindberg;
You can move a directory account (users, rooms, or equipment) from one node to another, or from one domain to another. For example, you might want to move a group of user accounts to another home node if the node they are on is getting full. Or, if a user moves from a US office to a European office, you might need to move the user from us.acme.com
to eu.acme.com
. You can also change both the user's node and domain.
When you migrate accounts using the Administration Tool, eMail Server automatically creates accounts on the new node or domain using the same usernames as the old accounts. Then it renames the accounts on the old node or domain to username_old
. When using OOMGR to migrate accounts, you must create and rename accounts manually.
This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.
The Migration wizard appears. You can use this wizard to move one or more directory accounts to a new node or domain.
This procedure explains how to use OOMGR to move a directory entry to another node in the same domain.
_old
to the existing directory entry that you want to move.
Enter the following command at the OOMGR prompt:
IOFCMGR>update <class
> <key_attribute
>=<value
> 2>to <key_attribute
>=<value_old
>;
uanode
attribute. Enter the new home node for the uanode
parameter.
Enter the following command at the OOMGR prompt:
IOFCMGR>insert <class
> <key_attribute
>=<value
> 2>uanode=<new_node
>
Info
to the file.
Enter the following command at the OOMGR prompt:
IOFCMGR>export <filename
>Info; IOFCMGR>fetch person username=<value_old
>; IOFCMGR>export end;
Enter the following command at the OOMGR prompt:
IOFCMGR>import filename=<filename
> owner=<value
>;
To move Bill Hayden's account from sf_unix1
to sf_unix2
, use the following procedure:
sf_unix1
node, rename Bill Hayden's account to bhayden_old
:
IOFCMGR>update person username=bhayden to username=bhayden_old;
bhayden
with the new home node called sf_unix2
:
IOFCMGR>insert person username=bhayden uanode=sf_unix2
sf_unix1
node, export his old information to a file:
IOFCMGR>export bhaydenInfo; IOFCMGR>fetch person username=bhayden_old; IOFCMGR>export end;
IOFCMGR>import filename=bhaydenInfo owner=bhayden;
|
Copyright © 2001 Oracle Corporation. All Rights Reserved. |
|