by PT 8.61+
Randall Groncki
Summary
As a PeopleSoft Developer, a PeopleSoft PUM should be a critical piece of your own home lab.
Besides delivering the latest PeopleSoft Application and PeopleTools, we get our own personal research and development environment for our personal continued education and exploration.
Critical to developers is to download and install the latest PeopleTools version included in the PUM. Often, this is our first chance to test drive a new PeopleTools version.
MOS Support Doc
Accessing PUM Shares Prompts User to “Enter network credentials” (Doc ID 3026118.1)
Scope
This post will show how to connect to the delivered tools_client directory on a VirtualBox PUM installation using a Windows 11 or later machine.
The Environment
This post assumes you have a VirtualBox PUM with PeopleTools 8.61 or later installed and currently running on your windows machine. I often install a PUM on an older Windows machine on my home network. This way, most of that machine’s resources are dedicated to running the VirtualBox PUM.
For this demonstration, I am going to use “S” as the mapped drive letter. Use whatever drive letter is appropriate to your environment.
Prior to PeopleTools 8.61
Prior to PUMs with PeopleTools 8.61, the VirtualBox Linux environments used Samba to share out the /tools_client/ directory.
Mapping to the directory required the “Net Use” command from a command prompt window.
Net use S: \\192.168.50.23\tools_clientThis no longer works.
PeopleTools 8.61 and later
Starting with the PeopleTools 8.61 PUMs, Oracle is now using the NFS file system to share out the tools client folder.
Before attempting to map the drive, ping the VirtualBox IP address and hosts name to ensure you have a current connection.
Ping [VB IP Address]
Ping [VB IP host name]
Use “mount.exe” to map the tools_client directory
If you have your hosts file correctly configured to the new PeopleSoft server, you may be able to map the tools client using the host name.
mount.exe -o anon \\hrdemo.gronkware.com\opt\oracle\psft\pt\tools_client S:
Even if the host is correctly mapped in your hosts file, the mount command may generate errors attempting to map the drive using the host name. In this case, just use the IP address version of the command.
mount.exe -o anon \\192.168.50.23\opt\oracle\psft\pt\tools_client S:
You may need to install NFS on your local windows machine
If the mount command generates errors of the “unknown” command flavor, you may have to install the NFS file system on your local Windows Machine.
Open a PowerShell window in Administrator mode
Paste and execute the following command
Enable-WindowsOptionalFeature -FeatureName ServicesForNFS-ClientOnly, ClientForNFS-Infrastructure -Online -NoRestartAfter this command has completed, reattempt the “mount.exe” command above.
Success? What you should see
If you successfully mapped the drive, you should see it in your File Explorer
Good Stuff on the Mapped Drive
There’s a lot there to use once you have your drive mapped:
- readme.txt – quick instructions on installing PeopleTools on your machine
- tnsnames.ora – this is the TNS mapping to the Oracle Database running on the PUM. You need this to run App Designer and any SQL Client against your database.
- Source.properties – a starter file for the PeopleTools Configuration Manager once you have it installed. You still will have several items to update. If you are a regular PeopleTools user, this is not anything new.
- SetupPTClient.bat – windows batch file to setup PeopleTools on your local machine. Review the readme.txt first.
Disconnecting the mapping
After you have installed PeopleTools, updated your TNSNames file and have PeopleTools configured, disconnect the mapped drive from your PC.
Open a Command Prompt window in Administrator mode and type in the following command:
net use S: /delete
