User Access

User access to workspaces

IBM® AD workspaces that are created in IBM AD Configuration Server contain IBM AD projects. When a workspace is created in IBM AD Configuration Server, by default, it is public. Configuring user access to workspaces can restrict user access to projects from IBM AD Analyze Client and IBM AD Build Client. To configure the user access to this workspace, add the credentials of only the users who must have access to its projects. User names are case-sensitive in IBM AD Configuration Server.
Note: IBM AD workspaces are defined within an environment in IBM AD Configuration Server. For any given environment, the workspace set as the default is the workspace where projects are published automatically at build time. Only one IBM AD workspace at a time can be set to be the default for a given environment.

For more information about user access to workspaces, see Managing workspaces' access rights.

Windows service access and User access to folders

The following table shows the required access to folders by different IBM AD server and client components. The access type of write, where specified, implies being able to also delete and create files.

By default on Windows, IBM AD server components, which run as Windows services, are configured to run using the credentials of the Windows Local System account ID of the machine on which they are installed. If any folder locations that are defined in your environment and listed in the following table as requiring access by a server component are not accessible to the IBM AD server's Local System account ID, you can go to the Properties dialog box of one or more of the IBM AD server services, and then configure the services to run using the credentials of a different ID that does have appropriate access to the necessary folder locations. Additionally, when using such a non-default service ID to run IBM AD services, on the server machine, the service ID must be granted the Log on as a batch job and Log on as a service local rights.

For IBM AD Analyze Client and IBM AD Build Client, grant access to the logged on Windows user that is running the component.

Important: When configuring and using IBM AD components, not only the folder locations, but also the format or nomenclature of how those folder locations are written is important. In most situations, the format of how a folder's location is specified in IBM AD Build Client when creating and updating a project is the same format that is used by other components when trying to access that project folder and the folders and files within it. Similarly, when using z/OS® connections and retrieving source assets from a z/OS system by using IBM AD Connect for Mainframe, the format of how the path for the retrieved members is specified in the IBM AD configuration process is used when components access source code and other assets that have been retrieved from z/OS.

Example

An IBM AD server machine has a hostname of addiserver5.companyabc.com, an IP address of 10.1.2.5, and a projects folder. The projects folder is shared so that it can be referenced in your network by a UNC name of either \\10.1.2.5\Projects or \\addiserver5.companyabc.com\Projects. This shared folder is also mapped by other Windows machines as drive P:. When creating and modifying a project using IBM AD Build Client, whichever of those UNC names is used also needs to be configured or used by most IBM AD server components and IBM AD Analyze Clients.

Therefore, if \\10.1.2.5\Projects is the format of the shared projects folder path used when creating projects in IBM AD Build Client, to assure that all IBM AD components, both those running on the server and those that might be running remotely such as IBM AD Analyze Client and IBM AD Build Client, can successfully access the IBM AD projects, their sources, and other project and analysis assets, use the same format, which is not \\addiserver5.companyabc.com\Projects or P:, when configuring IBM AD and creating remote mappings in the configuration information of IBM AD to refer to that folder location. Similarly, consistently use the same format when configuring source code locations, Index locations, and other IBM AD folder locations.

The default projects path value is listed in IBM AD Configuration Server and is used as the default value in IBM AD Build Client when creating a new project. To confirm the default projects path value, browse to the IBM Application Discovery Configuration Servers Admin page at http://localhost:8080, and then click localhost:2181>Install Configurations>IBM Application Discovery Build Client. The value is in the Default projects path field.

If a project is created by using a non-default value for its project path, to confirm the path value, browse to the IBM Application Discovery Configuration Servers Admin page at http://localhost:8080, and then click localhost:2181>Environments>environment_name>Projects>project_name>Information. The value is in the Local project path field on the Info tab.

Component Folder Required access Note
IBM AD Analyze Client IBM AD Analyze Client user's Eclipse installation folders Read and write  
IBM AD Analyze Client user's Eclipse workspace folders Read and write  
IBM AD Analyze Server (Optional) IBM AD Analyze Server installation folders Read and write The write access is required for the user under which the Windows service or Linux® process runs.
The shared folder for shared Java™ projects Read and write A shared folder for shared Java projects must be created and be referenced in the IBM AD Analyze Server manager.
IBM AD Build Client Project folders Read and write  
Configuration folders for z/OS connections Read and write  
Source code folders Read and write  
IBM AD Batch Server The Indexes folder Read and write  
IBM AD Batch Server installation folder Read and write  
Project and source folders Read and write  
IBM AD File Service The source file folders that are specified through local parameters in conf.yaml Read  
IBM AD Manual Resolutions Service The folder of journal files that is specified in conf.yaml Read and write  
IBM AD Search Service The folder of index files that is specified in conf.yaml Read  
The following image shows a best practice example of the IBM AD installation folder structure. However, you can customize the structure based on your particular needs.
This image shows an example folder structure.