Managing Applications and Paths

In this section:

Path management tasks are available from the Applications page, which is accessed by clicking Applications on the Web Console menu bar. The Application Directories tree displays is on the navigation pane. The ribbon and the top of this pane include a set of icons that provide the quickest way to initiate path management tasks.

A single click on one of the following icons is enough to get you started.

Note: You can also right-click the Application Directories folder in both the Web Console and the Data Management Console to access the Application Path option.


Top of page

x
Creating and Mapping Applications

How to:

Applications are designed to group related components.

Applications can be created and mapped in either the Web Console or the Data Management Console.

Application directory names must comply with the following rules:



x
Procedure: How to Create an Application
  1. From the Web Console menu bar, click Applications, or from the Data Management Console, expand the Server node folder.

    On the Web Console, the Applications page opens.

  2. Right-click the Application Directories folder, select New, and then Application Directory.

    The Create New Application page opens.

  3. Use the default Application Type, New Application under APPROOT.
  4. Enter a name in the Application Name field.
  5. Optionally, select the Recreate application if exists check box.

    Warning: Choosing this option will overwrite the existing application and any content in it.

  6. Enter a description in the Description field.
  7. The Add directory to APPPATH option is the default. Optionally, you can decide not to add the directory.
  8. Select a position from the Position in APPPATH drop-down menu. The options are Last and First. The default is Last.
  9. Select a profile from the Profile drop-down menu. For Server Administrators, the default is edasprof. For all other users, the default is the user profile.
  10. Click OK.

The application is added to the Application Directories folder.



x
Procedure: How to Map an Application to a Physical Directory

You can map an application name to a physical directory anywhere in the file system. This application name can be then used in APP commands.

Application mappings can be added and deleted based on profiles from either the Web Console or the DMC.

  1. From the Web Console menu bar, click Applications, or from the Data Management Console, expand the Server node folder.

    On the Web Console, the Applications page opens.

  2. Right-click the Application Directories folder, select New, and then Application Directory.

    The Create New Application page opens.

  3. Select Application Mapping to Disk or SQL Repository from the Application Type drop-down menu.

  4. Enter a name in the Application Name field.
  5. Accept the default Physical location, enter a different location, or click the selector button (...) and navigate to a directory on your file system.

    For platforms other than z/OS HFS Deployment, in addition to using the selector button, you can enter the full path of the physical directory to be mapped, in the format required on your platform. (If there are spaces in the directory you are mapping, you must enclose the entire path in double quotation marks.)

    For z/OS HFS and PDS servers, in addition to using the selector button, you can enter values using the following formats:

    ext=//DD:ddname[;ext2=//DD:ddname2][...][;extn=//DD:ddnamen]

    where extn are file type extensions.

    /dir/subdir

    entered manually or using the selector button.

    For z/OS PDS servers, you can also inform the high-level qualifiers of the data set collection that comprise this application. Here is an example of the format:

    iADMIN.SRV77.MAPAPP

    where the user has the following datasets (not in approot):

    IADMIN.SRV77.MAPAPP.FOCEXEC.DATA
    IADMIN.SRV77.MAPAPP.MASTER.DATA
    IADMIN.SRV77.MAPAPP.ACCESS.DATA
  6. Select New application (directory will be created) from the Map to drop-down menu, as shown in the following image.

  7. Optionally, enter a description in the Description field.
  8. Add directory to APPPATH is the default. Optionally, you can decide not to add the directory.
  9. Select a position from the Position in APPPATH drop-down menu. The options are Last and First. The default is Last.
  10. Select a profile from the Profile drop-down menu.

    For Server Administrators, the default is edasprof. For all other users, the default is the user profile.

  11. Click OK.

The mapping is added to the Application Directories folder.



x
Procedure: How to Delete an Application or the Application Mapping

Applications and application mappings can be deleted from either the Web Console or the DMC.

  1. From the Web Console menu bar, click Applications, or from the Data Management Console, expand the Server node folder.

    On the Web Console, the Applications page opens.

  2. Right-click the application or application mappings and select Delete or Delete Mapping, respectively.

    A confirmation dialog box opens.

  3. Click OK to delete the application or application mapping.

Note: Deleting an application mapping will delete it from any APP PATH commands that reference it, if the APP PATH command is in the same profile as APP MAP.


Top of page

x
Using an SQL Database to Store Application Contents

How to:

In addition to using a physical location, the contents of an application folder can also be stored in an SQL database. To use an SQL database, you must first create a new SQL Repository. After the repository is created, you can create applications mapped to the SQL Repository and store files there.

Warning: It is advisable to create a separate SQL Connection to use in creating an SQL Repository. If an existing SQL Connection is used, only Server Administrators or users with WSCFG privileges will be able to use the synonyms from this SQL connection in the application. This provides protection for the SQL Repository, preventing unauthorized users (without administrator privileges) from accessing the contents of the SQL Repository through a synonym.



x
Procedure: How to Create an SQL Repository to Store Applications

You must have an adapter connection configured to an SQL database.

  1. From the ribbon, click the Manage SQL Repository icon and select Create New, or right-click the Application Directories folder in the navigation pane, select Manage SQL Repository, and then Create New, as shown in the following image.

    The Create New SQL Repository page opens, as shown in the following image.

  2. Select a configured adapter from the Adapter drop-down menu.
  3. Select a connection from the Connection drop-down menu.
  4. Enter a prefix in the Prefix field.
  5. Optionally, select the Overwrite existing repository tables and their synonyms check box.
  6. Click OK.

    A warning message is displayed, as shown in the following image.

  7. Click OK.

    Two SQL Repository catalog tables are created with this connection, as shown in the following image.

    The tables are:

    prefixIOHFILETABLE
    prefixIOHRECORDTABLE

    Two synonyms describing the catalog tables are also created in EDACONF/catalog/IOH.

  8. Optionally, click Create New Application.

    The Create New Application page opens, as shown in the following image.



x
Procedure: How to Create an Application With SQL Content

You must have created an SQL Repository.

  1. From the Applications page, right-click the Application Directories folder in the navigation pane, select New, then Application Directory, as shown in the following image.

    The Create New Application page opens.

  2. Select New Application under repository - DBMS (Connection name) from the Application Type drop-down menu, as shown in the following image.

    Note: The choices will include the repository, adapter type, and connection name. In this example, they are the bks repository, Adapter for Microsoft SQL Server, and CON01 connection.

  3. Enter a name in the Application Name field.
  4. Optionally, select the Recreate application if exists check box.

    Warning: Choosing this option will overwrite the existing application and any content in it.

  5. Optionally, enter a description in the corresponding field.
  6. Optionally, deselect the Add directory to APPPATH check box. The application is added to the APPPATH by default.
  7. Select a position for the application from the Position in APPPATH drop-down menu. The choices are Last or First. The default value is Last.
  8. Select a profile from the Profile drop-down menu. For server administrators, the default value is edaprof. For non-administrators, their user profile is the default value.
  9. Click OK.

The application is added to the navigation tree. You can now use this application to store procedures, synonyms, data files, and other content.


Top of page

x
Nested Application Directories

How to:

A nested application directory is one created within a higher-level application. The server allows five levels of nested application directories by default, except on z/OS under PDS deployment, where applications cannot be nested. The server must be configured for deeper or unlimited levels.

Nested application directories are implicitly added to the application path if the parent directory is on the application path.

For example, the following application tree has a directory named new1 that has a child directory named new2.

The APP PATH command explicitly places new1 on the application path:

APP MAP new1 "C:\ibi\apps\new"
APP PATH baseapp ibisamp new1

However, you can test the path to see all of the implicitly added directories by right-clicking the top level of the Applications Directories tree and selecting Application Path. When the Application Path page opens, click Test:

The effective application path also includes new1/new2:



x
Procedure: How to Set the Level of Nested Application Directories
  1. From the menu bar, select Applications.
  2. From the ribbon, click the Application Settings icon, or right-click the Applications folder, and select Application Settings.

    The Application Settings page opens.

  3. Enter the level of nested applications in the nested_app field or select y from the drop-down menu. The default value is 5. Selecting y allows unlimited levels of nested applications.

    Note: For z/OS servers, this setting is only applicable to directory-style applications. It is not applicable to PDS-style applications or to applications mapped as a collection of ddnames.

  4. Click the Save and Restart Server button.

    After the server restarts, you can create a new application subdirectory by right-clicking an application folder and selecting New and then Application Directory from the context menu.

Note: Nested applications must be in effect in order to create user home application directories.



x
Procedure: How to Create a Nested Application Directory
  1. From the Web Console menu bar, click Applications, or from the Data Management Console, expand the Server node folder.

    On the Web Console, the Applications page opens.

  2. Right-click an application, select New, and then Application Directory.

    The Create New Application Directory page opens.

  3. Enter a name in the Application Name field.
  4. Optionally, enter a description in the Description field.
  5. Click OK.

The nested application is added to the application tree under its parent application folder.


Top of page

x
Home Application Directories for Users

How to:

You can configure the server to allow each user to have a home application directory. Providing a user home application directory gives each user a directory where he has full control to create, change, and run his applications.

The home application for any user who is not a server administrator appears in two places on the Web Console application tree. Both of these applications point to the same physical location, so that that they can be referenced in two ways. The two applications are:

Server administrator users have the myhome application prepended and the homeapps application appended to APPPATH, The homeapps folder can be expanded to show the home applications for all users.

The following image shows both the myhome application and the homeapps application for user pgmtst1:

The files created in home applications can be referenced in procedures as myhome/procname.fex and homeapps/pgmtst1/procname.fex

The first type of reference can be ported easily to any user. It enables you to create a common application that utilizes data stored in the home applications of users as myhome/data, so that each user can run the same procedure but get a report based on the data stored in the home application of that user.

The second type of reference enables you to run applications specific to a user, referring to the data and procedure for each user as homeapps/pgmtst1/proc1.fex and homeapps/pgmtst1/data. This type of reference can be used for testing applications before moving them to common application folders.

Home application directories should be enabled only on secured servers. If the server runs with security OFF, all users have total control of files in all applications, and the home directories will not work as designed. Nested applications must be enabled in order to create user home application directories.

The Server Administrator can monitor and manage home application directories for all users and, therefore, all user home directories are visible and in the path on the Web Console application tree when the connected user has Server Administrator privileges.

When the server is enabled for home applications, user home application directories are not created automatically. Users can create them from the Web Console Application page, or ask their server admin to create them.

Home applications can also be stored in an SQL Repository. You must first create an SQL Repository and configure the application settings homeapps parameter to point to the SQL Repository, as described in Using an SQL Database to Store Application Contents.

After a home application directory is created for a user:

Note: This feature is available only for customers that are licensed for Managed Reporting or DataMigrator.



x
Procedure: How to Manage Home Application Directories

In order to set up home directories for individual users, nested applications must be enabled. They are enabled to five levels by default. The home directory under which user application directories will be created is set during installation. The default is homeapps. The homeapps directory can be changed to a different physical location on the Application Setting page. All user home directories will be nested under the home directory.

  1. From the menu bar, select Applications.
  2. From the ribbon, click the Application Settings icon, or right-click the Applications folder, and select Application Settings.

    The Application Settings page opens.

  3. Check the location of the homeapps directory. You can set the homeapps parameter to point to a physical directory or to an existing SQL Repository.
  4. Click the Save and Restart Server button to implement these changes.

    When the server restarts, go to the Applications menu. For a user with Server Administrator privileges, a users home folder will appear under the Application Directories tree and will have all of the user home directories.

    Users who do not have server administrator privileges can see their home directory under application myhome, which is prepended to APPPATH.

    Server administrator users have the myhome application prepended and the homeapps application appended to APPPATH, The homeapps folder can be expanded to show the home applications for all users.

    The following image shows both the myhome application and the homeapps application for user pgmtst1:

    The files created in home applications can be referenced in procedures as myhome/procname.fex and homeapps/pgmtst1/procname.fex

    The first type of reference can be ported easily to any user. It enables the server administrator to create a common application that utilizes data stored in the home applications of users as myhome/data, so that each user can run the same procedure but get a report based on the data stored in the home application of that user.

    The second type of reference enables the server administrator to run applications specific to a user, referring to the data and procedure for each user as homeapps/pgmtst1/proc1.fex and homeapps/pgmtst1/data. This type of reference can be used for testing applications before moving them to common application folders.



x
Procedure: How to Store Home Applications in an SQL Repository

You must first create an SQL Repository. For information, see How to Create an SQL Repository to Store Applications.

  1. From the ribbon, click the Application Settings icon, or right-click the Application Directories folder in the navigation pane, and select Application Settings, as shown in the following image.

    The Application Settings page open, as shown in the following image.

  2. Click the selector button (...) next to the homeapps field.

    The Select physical location dialog box opens.

  3. Select SQL Repository, as shown in the following image.

  4. Select a subfolder, and click OK.

    The subfolder is entered in the homeapps field, as shown in the following image.

  5. Click Save and restart Server.

Home applications that are created will now be stored in the SQL database.


Top of page

x
Configuring the Application Path

How to:

The applications available for inclusion in the search path are identified by name, type, and physical location. If the Add directory to APPPATH check box was selected when the application was created, it was automatically added to the search path. If not, you must explicitly add it to your search path.

Note: You can also create profiles from the Application Path page. Profiles are the locations in which the search path is saved.



x
Procedure: How to Configure the Application Path

You can configure the Application Path to add or remove applications or mappings from either the Web Console or the DMC.

  1. From the Web Console menu bar, click Applications, or from the Data Management Console, expand the Server node folder.

    On the Web Console, the Applications page opens.

  2. From the ribbon, click the Application Path icon, or right-click the Application Directories folder in the navigation pane, and select Application Path.

    The Application Path page opens.

  3. Select a profile from the Profile drop-down menu. The default is edaprof.
  4. Select the check box in the In Path column for the application or mapping.

  5. Optionally, you can reorder applications in the APP PATH, using the Up and Down icons at the right. The top and bottom buttons move the application to the start or end of the APP Path. The center buttons move the application up or down one position.

  6. To remove an application, deselect the check box in the In Path column.
  7. Optionally, click Test to test modifications to the search path. A Test Application Path pane opens.

    The Test Application Path pane shows:

    • Executed profiles. This depends on the level of the profile you selected.
    • Executed commands. These are the APP commands executed for the profile you selected. The commands can include APP PATH, APP MAP, APP APPENDPATH, or APP PREPENDPATH.
    • Effective APP PATH. This is the effective application tree that will result from all the executed profiles, including the selected profile level. The execution sequence is: server profile (edasprof.prf), service profile, role profile, group profile, and user profile.
  8. Click Save.

The navigation pane is updated.

Note: You can also create a new profile from the Application Path page.



x
Procedure: How to Configure the Application Path in a User, Group, or Role Profile

The Application Path can be configured from either the Web Console or the DMC.

  1. From the Web Console menu bar, click Applications, or from the Data Management Console, expand the Server node folder.

    On the Web Console, the Applications page opens.

  2. From the ribbon, click the Application Path icon, or right-click the Application Directories folder in the navigation pane, and select Application Path .

    The Application Path page opens.

  3. From the Profile drop-down menu, select New Profile.

  4. Enter a name in the New Profile Name field.
  5. Select an option from the Application Path drop-down menu.

    The options are:

    • Inherit from previously executed profiles
    • Override previously executed profiles
    • Prepend previously executed profiles
    • Append to previously executed profiles
  6. Optionally, click Preview to see the profile.

  7. Click Save.


x
Procedure: How to Edit a Profile
  1. From the menu bar, select Workspace.
  2. On the navigation pane, open the Configuration Files and User/Group Profiles folders.
  3. Right-click the profile and select Edit.

    The profile opens in a text editor with its current path displayed.

  4. Edit the path information and click the Save icon.

Tip: You can also edit a profile search path by selecting and saving configuration options. Follow instructions for configuring the application path.


Top of page

x
Filtering the Application Tree

How to:

Filtering enables you to customize the file listings on the Application tree, displaying only the files you choose. It can be based on file name, location, statistics, type, or any combination of items matching a number of criteria.



x
Procedure: How to Filter Items on the Application Tree

You can customize the items that display on the Application Tree by filtering. Your filtering selections apply to all applications displayed in the navigation pane.

  1. From the Web Console menu bar, click Applications.
  2. Click the Filter icon above the navigation pane, and select Procedures, Synonyms, or Advanced, as shown in the following image.

    1. If you choose Procedures, you can display all procedures or only scheduled ones.
    2. If you choose Synonyms, you can display all synonyms or only cluster or business views.
    3. If you choose Advanced, The Filter Applications Tree page opens

    Using the File Name section, you can filter by name, extension, description and content, as shown in the following image. To filter the name, you can use the percent sign (%) as a wildcard character. Specifying e% displays all files whose name begins with the letter e.

  3. Using the File Location section, you can filter by Application Directory, Application Path, Mapped Applications, and Applications under APPROOT, as shown in the following image.

  4. Using the File Statistics section, you can filter by file size and modified date, as shown in the following image.

  5. Using the File Type section, you can filter by type of file to be included.

  6. Optionally, select an adapter from the Adapters drop-down menu. Only synonyms created with that adapter that match the filtering criteria will appear in the tree.
  7. Click Set Filter. The Filter Status page confirms that the filter was set.

When a filter is applied, the Application Directories tree label includes (Filtered), as shown in the following image.

Note: You can remove the filter by clicking the Clear Filter button.

You can see the filter results by clicking Show Report, as shown in the following image.


Top of page

x
Searching for Files

How to:

The Search Files tool provides a search function on the Application Tree. It can search for files using a variety of criteria, including file name, location, description, contents, statistics, and type, in an application directory or across the entire server.

To view the file search page, click the Search Files button on the Applications page ribbon, or right-click the Application Directories folder and select Search Files on the context menu.

The Search Files page opens, as shown in the following image.

Enter your search criteria, and click Search.

The report returned allows you to open procedures, Master Files, and displayable data in the editor.



x
Procedure: How to Search for Files

The Search Files page provides a wide range of search criteria.

  1. From the Web Console menu bar, click Applications.
  2. Click the Search Files icon.

    The Search Files page opens.

  3. Select the search criteria from the File Name, File Location, File Statistics, and File Type sections.
  4. Click the Search button.

The Search Results are displayed, as shown in the following image.


Top of page

x
Sorting the Application Tree

How to:

Sorting enables you to change the order in which items are listed on the application tree.



x
Procedure: How to Sort the Application Tree
  1. From the Web Console menu bar, click Applications.

    The Applications page opens.

  2. From the ribbon, click the Sort by icon, and select a sort method, as shown in the following image.

    You can sort by Name, Size, Type, or Modified date. Type is the default.


Top of page

x
Managing Application Files

How to:

You can copy and move files between applications, delete them from applications, and refresh synonyms in applications. You can also copy, move, or delete subfolders from one application to another. The subfolders will be copied, moved, or deleted with all of its files and all of its own subfolders.



x
Procedure: How to Manage Application Files
  1. From the Web Console menu bar, click Applications.
  2. Right-click an application folder and select Manage Files.

    The Manage Files page opens.

  3. Select the check box next to one or more files. To select all files, click Select All.
  4. Enter an application folder in the Current Application field.

    The selector (...) button opens the Select current application dialog box which allows you to navigate to the application, as shown in the following image.

  5. Enter an application folder in the To Application field or click the selector button (...) and navigate to one.
  6. Click Copy or Move.

    The file(s) are copied or moved to the selected application.

  7. To delete files, select their check boxes and click Delete.


x
Procedure: How to Refresh Synonyms in an Application
  1. From the Web Console menu bar, click Applications.
  2. Right-click an application folder and select Manage Files.

    The Manage Files page opens.

  3. Select the check box next to one or more synonyms.

    To refresh all listed synonyms in the selected application, click Select All.

  4. Click Refresh Synonym.

iWay Software