Working with server windows

Use server windows to perform most migration tasks. When you open a server window, functions in the main menu applicable to the task you are performing are available. Unavailable functions are either not necessary for the task, or you have not selected the items that activate them.

You can have multiple server windows open in the BMC Remedy Migrator main window.

In this topic:

BMC Remedy Migrator performs the following actions:

Creates cache files by retrieving objects for the server and copying them to your computer. A cache progress window shows the objects that are being retrieved. You can cancel the cache by clicking the Cancel button.
Lists server objects in the left pane of the server window. You can select how objects are viewed by clicking either the Object View or Prefix tabs.
Displays details for a selected object or report. You can view objects by form, by application, or by workspace.

Opening a server window

Perform the following steps to open a server window in BMC Remedy Migrator.

To open a server window

Select File > New Server window.
From the list, select a server.

Opening a new server window

Displaying objects in a server window

When you log on to a server, the objects for that server are displayed in a server window.

Displaying objects in the Object Type view

The Object Type view lists objects by their type. It also lists backup, script, and result files. If no objects exist on the server for an object type, that object type is not listed.

Object Type view

To view objects by type, click the Object Type tab in the left pane of the BMC Remedy Migrator main window. To display all objects of a specific type, select the type from the list. The objects of that type are listed in the right pane.

Displaying objects in the Prefix view

The Prefix view groups objects into folders, based on categories or on naming conventions you define using colon (:) delimiters. For example, all objects named MB objectName appear in a folder called MB. Objects named MB:Sub1: objectName appear in a Sub1 folder under the MB folder. In the Name column, only the objectName portion of the object name is displayed.

Prefix view

To view objects by prefix, click the Prefix tab in the left pane of the BMC Remedy Migrator main window. To view a set of objects, click the folder for the objects you want to view.

Viewing objects by form

You can view the list of objects associated with each form.

Viewing objects by form

To display objects by form

Select View > By Form.
The By Forms dialog box appears. By default, All Forms is the selected view option, and the list of available forms is disabled.
In the View Option area, click the option button for the types of forms you want to view, and click OK.
- If you select Forms with Prefix, the Prefix field becomes enabled. Enter a prefix.
- If you select Selected Forms, use the Add, Remove, Add All, or Remove All buttons to create a list of the forms you want to view. To select more than one form, hold down the Ctrl or Shift key as you make your selections.
In the left pane of the server window, click Forms to display the forms you selected.
BMC Remedy Migrator displays the forms according to the view options, and all the objects related to those forms.

Viewing form details

You can double-click a form to view its details (or click once and press Enter).

In addition, you can view the details of forms (fields, views, and data) by right-clicking a form in the right pane and then choosing Form Details. This action displays the Form Detail tree view.

Form detail list showing field details

To display the details of a selected form

In the left pane of the server window, under BMC Remedy AR System Objects, click Forms.
In the right pane of the server window, select a form.
Select View > Form Details.
The details for the selected form appear in the right pane of the BMC Remedy Migrator window. The header bar shows the name of the form and the number of objects being viewed for that form.
From the Form Detail window, you can migrate fields, views, data, and other objects related to that form.
Note

When dragging an active link, filter, escalation, and so on from a Form Detail window to another Form Detail window, the name of the form to which the object is linked is not changed to the destination form name. Only fields and views are created on the destination form. Also, data with fields and views are the only objects migrated to the destination Form Detail view.

Viewing objects by application

You can view the list of objects pertaining to an application.

To view objects by application

Select View > View by Application.

View by Applications dialog box
In the By Application dialog box, select a local or deployable application.
For more information about local and deployable applications, see Deployable applications.
The objects for the selected application are listed in the right pane of the server window.

Viewing objects by workspace

A workspace allows you to limit the objects displayed in a window to only those objects that are associated with a particular packing list or application. When you create new objects in the context of the workspace, the objects are added to the packing list or application. For more information about workspaces, see Starting and logging on to Remedy Developer Studio.

To view objects by workspace

Click in the server or file window whose workspace objects you want to display.
Make sure that All Forms is selected in the By Form dialog box; otherwise, the menu option is disabled.
Select View > By Workspace.
The By Workspace dialog box appears. If no workspace has been created on this server, the message "No current record" appears.
Select an application or packing list from the list, and click OK.
In the server window, the object category reflects the options selected in the By Workspace dialog box. For more information about applications, see Developing an application.

Types of object details

The right pane of the server or file window (the following figure) displays columns of objects and details about each object listed. The following sections list the items listed for each object type.

Details for selected objects
(Click the image to expand it.)

Forms

The following table contains the items listed for forms.

Items listed for forms

Item	Description
Form Name	The name of the object.
Type	For forms, the type of form, such as Join or Regular.
Access Point	Whether an access point is available for the object. You can identify specific forms and guides in deployable applications as access points, or points of integration, for use with other deployable applications. For more information about deployable applications, see Deployable applications.
New Entry Point	Whether any new entry points are available for the object. A new entry point can be clicked to start a task, such as creating a request. Entry points are listed in the Application List field on the home page. For more information about home pages, see Home page components.
Search Entry Point	Whether any search entry points are available for the object. A search entry point can be clicked to start a search.
Owner	The name of the user who created the object.
Timestamp	The date and time on which the object was created or changed.
Last Changed	The name of the user who last updated the object.
Lock State	The locked state of the object. Locking allows application developers to protect workflow objects that are not designed for or intended to be customized, by preventing them from being modified or even viewed. An object can have one of the following locked states: None — Allows users to view and modify the object. Read-only — Prevents users from modifying the object, but allows them to view its details. Hidden — More restrictive lock that prevents users from viewing details of a locked object, including in BMC Remedy Migrator differences and dependency reports.
Archive	Whether archiving is enabled or disabled for a form. You can use the data archiving feature in BMC Remedy AR System to set up options for backing up of data in forms. Archive forms can be migrated if they exist on the destination. For more information about data archiving, see Archiving data.
Views, Fields, Data Fields, Trim Fields, Control Fields, Page Fields, Table Fields	The number of fields of each type included in the form.
Member A, Member B, and so on	If this is a join form, the names of the member forms.

Active links, filters, and escalations

The following table contains the items listed for active links, filters, and escalations.

Items listed for active links, filters, and escalations

Item	Description
Name	The name of the active link, filter, or escalation.
Primary Form	The name of the form that appears in BMC Remedy Mid Tier when the application opens.
Forms Referenced	The number of forms referenced.
Enabled	Whether this object is enabled.
Order	The execution order for this object.
Execute On	The action on which this object executes.
If Actions	The number of if actions included.
Else Actions	The number of else actions included.
Owner	The name of the user who created this object.
Timestamp	The date and time on which this object was last changed.
Last Changed	The name of the user who last changed this object.
Lock State	The locked state of the object. Locking allows application developers to protect workflow objects that are not designed for or intended to be customized, by preventing them from being modified or even viewed. An object can have one of the following locked states: None — Allows users to view and modify the object. Read-only — Prevents users from modifying the object, but allows them to view its details.
Control Field (active links only)	Typically a menu field or a button, which fires an active link when selected.
Focus Field (active links only)	A field on which an active link fires when the field gains focus.
Qualification	The text of any qualification created for this object.

Active link guides and filter guides

The following table contains the items listed for active links, filters, and escalations.

Items listed for active link guides and filter guides

Item	Description
Name	The name of the active link guide or filter guide that appears in the server window the BMC Remedy System Administration Console.
Form Name	The name of the form to which the guide applies.
Type	The type of form to which the guide applies, for example, a regular form.
Label	The name of the guide that appears in the Open dialog box in BMC Remedy Mid Tier.
Owner	The name of the user who created the guide.
Timestamp	The date and time on which the guide was last changed.
Last Changed	The name of the user who last changed the guide.
Lock State	The locked state of the object. Locking allows application developers to protect workflow objects that are not designed for or intended to be customized, by preventing them from being modified or even viewed. An object can have one of the following locked states: None — Allows users to view and modify the object. Read-only — Prevents users from modifying the object, but allows them to view its details. Hidden — More restrictive lock that prevents users from viewing details of a locked object, including in BMC Remedy Migrator differences and dependency reports.
Description	A description of the guide's function.

Applications

The following table contains the items listed for applications.

Items listed for applications

Item	Description
Application Name	The name for the application.
Application Label	The name for the application that appears in the Open dialog box in BMC Remedy Mid Tier, and in the application title bar.
Primary Form	The form that appears when the application is opened in BMC Remedy Mid Tier.
Primary View	The view of the form that appears when the form is opened.
Owner	The name of the user who created the application.
Timestamp	The date and time on which the application was last changed.
Last Changed	The name of the user who last changed the application.
Lock State	The locked state of the object. Locking allows application developers to protect workflow objects that are not designed for or intended to be customized, by preventing them from being modified or even viewed. An object can have one of the following locked states: None — Allows users to view and modify the object. Read-only — Prevents users from modifying the object, but allows them to view its details.
Application State	The current production state of the application, for example, Maintenance or Test.
Type	The type of application, either local or deployable. Deployable applications use permissions based on roles that are specific to the application, rather than groups that are specific to the server.
Description	A description of what the application does or other pertinent information.

Packing lists

The following table contains the items listed for packing lists.

Items listed for packing lists

Item	Description
Packing List Name	The name of the packing list.
Packing List Label	The label used, if any, for the packing list.
Owner	The name of the user who created the packing list.
Timestamp	The date and time on which the packing list was last changed.
Last Changed	The name of the user who last changed the packing list.
Lock State	The locked state of the object. Locking allows application developers to protect workflow objects that are not designed for or intended to be customized, by preventing them from being modified or even viewed. An object can have one of the following locked states: None — Allows users to view and modify the object. Read-only — Prevents users from modifying the object, but allows them to view its details.
Description	A description of the packing list's function.

Web Services

The following table contains the items listed for web services.

Items listed for web services

Item	Description
Web Services Name	The name of the web service.
Form Name	The form used as the access for the web service.
Web Services Label	The name that is displayed to users.
Owner	The name of the user who created the web service.
Timestamp	The date and time on which the web service was last changed.
Last Changed	The name of the user who last changed the web service.
Lock State	The locked state of the object. Locking allows application developers to protect workflow objects that are not designed for or intended to be customized, by preventing them from being modified or even viewed. An object can have one of the following locked states: None — Allows users to view and modify the object. Read-only — Prevents users from modifying the object, but allows them to view its details.
Description	A description of the web service's function.

Menus

The following table contains the items listed for menus.

Items listed for menus

Item	Description
Menu Name	The name of the menu.
Type	The type of menu, either Character, File, Search, SQL, or Data Dictionary.
Refresh	The condition on which the menu is refreshed, either On Connect, On Open, or on 15 Minute Interval.
Timestamp	The date and time on which the menu was last changed.
Owner	The name of the user who created the menu.
Last Changed	The date and time on which the menu was last changed.
Lock State	The locked state of the object. Locking allows application developers to protect workflow objects that are not designed for or intended to be customized, by preventing them from being modified or even viewed. An object can have one of the following locked states: None — Allows users to view and modify the object. Read-only — Prevents users from modifying the object, but allows them to view its details.

Groups

The following table contains the items listed for groups.

Items listed for groups

Item	Description
Group ID	The unique ID for the group
Group Name	The name of the group.
Group Type	The permission type for the group, either None, View, or Change.
Category	The category of group, either Regular, Computed, or Dynamic. Regular groups are explicit groups that you create and to which you assign a specific list of users. Computed groups are explicit groups that you create and to which users are assigned based on a comparison of users belonging to other explicit groups. For example, you can create a computed group that includes the list of users who are members of both groups A and B, or members of group C, but not members of group D. Dynamic groups use the contents of special fields to determine group membership. For more information about groups, see Creating and managing groups.

Flashboard

The following table contains the items listed for Flashboards.

Items listed for Flashboards

Item	Description
Flashboards	A tool for representing data visually from BMC Remedy BMC Remedy AR System forms.
Flashboards alarms	Tools that enable sending of notifications to specific users based on a threshold value.
Flashboards variables	Specify the information you want to monitor from a single form. In Flashboards, a variable represents data, such as a slice of a pie graph, a bar in a bar graph, or a line in a line graph.

Plug-ins

The following table contains the items listed for plug-ins.

Items listed for plug-ins

Item	Description
Plug-in modules	The names of plug-in modules. Plug-in modules are used with the arplugin process, which is a companion process to the AR System server. It loads configured plus-in modules to interface with external data.
Plug-in definitions	Definitions for selected plug-ins.

Roles

The following table contains the items listed for roles.

Items listed for roles

Item	Description
Role ID	The unique identifier for this role.
Role Name	The name of the role.
Application	The application to which this role belongs.

Images

The following table contains the items listed for images.

Item	Description
Name	The name of the image.
Type	The type of the image. For example, jpeg, gif, png, etc.
Checksum	This is short data which added to the image for the purpose of detecting errors which may be introduced during its migration, transmission or storage.
Owner	The name of the user who created the image.
Timestamp	The date and time on which the image was created or changed.
Last Changed	The name of the user who last updated the image.
Description	A description about the image.
Lock State	The locked state of the image. Locking allows application developers to protect workflow objects that are not designed for or intended to be customized, by preventing them from being modified or even viewed. An image can have one of the following locked states: None — Allows users to view and modify the object. Read-only — Prevents users from modifying the object, but allows them to view its details. Hidden — More restrictive lock that prevents users from viewing details of a locked object, including in BMC Remedy Migrator differences and dependency reports.

Associations

The following table contains the items listed for associations.

Item	Description
Name	The name of the association.
Enabled	Whether this object is enabled.
Type	The type of association. There are two types of associations which you can create in BMC Remedy Developer Studio: Direct associations Indirect associations For more information, see Associations overview.
Primary Schema	The name of the primary form used in the association.
Secondary Schema	The name of the secondary form used in the association.
Owner	The name of the user who created the association.
Timestamp	The date and time on which the association was created or changed.
Last Changed	The name of the user who last updated the association.

Deleting objects from servers or files

Although you typically delete objects from within Developer Studio before you migrate, you can delete objects, including locked objects, from servers or files using BMC Remedy Migrator. To make sure that nothing is affected by the deletion, BMC Remedy Migrator runs a check on the object that you want to delete.

Note

Locked objects can be deleted only in blocks. Deleting one object that belongs to a locked group deletes the entire group. Deleting a locked form that is part of a join deletes the join form.

To delete objects

In the right pane of the server or file window, select the objects you want to delete.
BMC Remedy Migrator cannot delete DSO (Distributed Server Option) Map-related forms, User and Group forms, and BMC Remedy AR System-specific forms, such as the User Preference form. Also, BMC Remedy Migrator does not support deletion of data in .migrator forms.
Select Edit > Delete.
If other objects are affected by the deletion, those objects are listed. If no other objects are affected, a confirmation message appears.

Deleting objects — impact warning message
Confirm that you want to delete the objects:

Click Yes to delete the specified selection and continue to the next object.
Click No to skip the specified selection.
Click Yes to All to delete all the selected objects.
Click No to All to stop the deletion.

Warning

If you select Yes to All, BMC Remedy Migrator deletes every object without checking the impact of the deletion on the links to other objects.