As a developer you need to sign in to application designer a LOT.
Unless you have single signon this means entering your user name and password on a regular basis. Even after installing PeopleTools locally and setting up your own configuration file, you'll still need to enter your password and change databases as required.
Automatic Login Batch Script
Here's an alternative. Create the following batch script in the same folder as pside.exe (usually %PS_HOME%\bin\client\winx86) and call it pside.bat.
If you don't have PeopleTools installed locally, take a look at this article.
@echo off start pside.exe -CT <DBTYPE> -CO <USERNAME> -CP <PASSWORD> -CD %1
Modify this code as follows:
- Replace <DBTYPE> with your database type. Common examples are:
- DB2 UDB
- Replace <USERNAME> with your PeopleSoft user name
- Replace <PASSWORD> with your PeopleSoft password
To run this script, simply call it as follows from the command line:
$ pside.bat <DBNAME>
Or from the run dialog box as:
Remember to replace %PS_HOME% with the local root folder of your PeopleSoft files.
Where DBNAME is the name of the PeopleSoft database you are connecting to (e.g. DMO). If you call it without the <DBNAME> parameter it will simply sign you into the last environment you were in (providing your credentials are correct).
Creating desktop shortcuts for your environments
If you have multiple environments and want to create desktop shortcuts for each one, follow these instructions:
- Create copies of your pside.bat script for each environment. For example you might have
- pside_dmo.bat for demo
- pside_test.bat for test
- pside_prod.bat for production
Note that these MUST exist in the same directory as pside.exe.
- Create a desktop shortcut by dragging each of the scripts to your desktop
- Right click on the properties of each script and in the target box enter the database name in the target box after pside.bat as shown:
Note that if you use different user names and passwords for different environments, simply modify the batch script for each environment and specify the appropriate user name in the -CO parameter and the appropriate password in the -CP parameter.
You could also just hard code the environment instead of %1 in the batch script itself. So replace %1 with DMO for connecting to the demo database.