[WebSphere] Mapped network drives in Windows are not visible to WebSphere Application Server

윈도우 서버에서 네트워크 드라이브를 사용할때 주의사항
WebSphere만 해당되는 문제가 아니라 OS 특성에 의한 문제이니 참고바랍니다.

Mapped network drives in Windows are not visible to WebSphere Application Server

Problem(Abstract)

IBM® WebSphere® Application Server might not be able to locate mapped network drives in Microsoft® Windows® under certain circumstances.

Cause

Due to how permissions are assigned to mapped network drives, not all users are able to access these drives by way of the drive letters. Only the services owned by the Local System Account can map network drives that can be seen by all other accounts.

Resolving the problem

This problem is described in Microsoft Support article 180362:

http://support.microsoft.com/default.aspx/kb/180362/

Normal user accounts, including Administrators, can create mapped drives and assign them drive letters (Z:\); however, they will be the only user to see these drives. Processes started by this user will be able to see this mapped drive.

However, if that same user starts a Windows Service, that service will be unable to see the mapped drive. Only services owned by the Local System Account can map network drives that can be seen by all other accounts.

WebSphere Application Server as a non-service​​

If WebSphere Application Server is set up to run as a non-service, such as from the command line, the user starting the server (or the user who started the nodeagent) must be the same user who mapped the network drive.

Example:​​ Two user accounts are created, named ​​admin ​​and ​​wasuser​​. ​​ WebSphere Application Server is not configured to run as a service.​​ ​​ admin​​ is an Administrator. ​​ He creates a mapped network drive ​​Z:\​​ and points it to ​​\\network\folder\​​ ​​ ​​wasuser ​​is a Power User. ​​ He has permissions to launch WebSphere Application Server from the command line.​​ ​​ ​​ If any application on the server connects directly to drive ​​Z:\​​, it will not be found. ​​wasuser ​​ did not map drive ​​Z:\​​.​​

Either method below can be used to resolve this issue:

1. Use the Universal Naming Convention (UNC) path in the application to access the shared network location.
   • In the example above, the application connects to \\network\folder\ instead of Z:\
     
2. Map the drives so that they are associated with the user account that starts WebSphere Application Server.
   • In the example above, wasuser would need to map drive Z:\ to \\network\folder\ in order for that drive to become available.

WebSphere Application Server as a Windows Service​​

On Windows, normally WebSphere Application Server is created as a Windows Service. A service that is configured to run under a specific user account will always create a new log-on session to launch the service. Any mapped drives created by the same user account will be unavailable as they are not mapped during the same log-on session as the service. The solution in this case is to stop using mapped network drives and use UNC paths.

If using UNC paths is not possible, either disable or remove the Windows Service:

To disable the service:

1. Click on Start > Run...
2. Type the command services.msc and click OK.
3. Locate the service associated with the application server (or nodeagent) and double-click the entry.
4. Under the Startup Type drop-down box, choose Disabled.
5. Click OK.

To remove the service:

1. Stop the server.
2. Open a command prompt and navigate to the install_root/bin directory.
3. Run the following command:
   
   

   WASService.exe -remove [SERVICE_NAME]​​

   Where ​​[SERVICE_NAME]​​ is the name of the Windows Service.​​

4. Start the server.

WebSphere Application Server V6.1 does not support the use of drive letter numbers in Windows 2003 for mapped drives

Technote (troubleshooting)

Problem(Abstract)

Due to the existing limitation in Windows 2003, WebSphere Application Server V6.1 does not support the use of drive letter numbers in Windows 2003 for mapped drives. This applies to any component running in WebSphere Application Server or WebSphere Process Server V6.1 on Windows 2003, but in case of the WebSphere Adapters it primarily affects the WebSphere Adapter for Flat Files.

Symptom

You will receive an error indicating that the drive is not accessible in the runtime logs while running the WebSphere Adapter for Flat Files.

Resolving the problem

You must use the full Universal Naming Convention (UNC). The location needs to be accessible to the operating system user name used by the adapter. For example:

X:\sharefolder

should be listed as \\computername\sharedfolder

Note: This directory should also have complete access privileges for the user name of the operating system used by the adapter. If complete access is not provided to the mapped folder, it will result in similar error messages.