PSFT user id setup on the Deployment Server

The Upgrade Manual states you must set the password for id PSFT to PSFT. Has anyone set this to another value, say matching a company's security rules, and been successful?

I am assming the PSFT id is the same as the JDE id just in a newer version and we have changed it.

You have to change it everywhere so in the INI files and any DB ids.

Nick

So what you are saying is I can use whatever pwd I want but I need to update the server jde.ini file and the jde.ini file that is deployed to client workstations when initially loaded. I don't worry about packages and updates, correct?

Thanks for the reply.

That is what works in our environment.
The client INI's do not need this password. In our environment we set it in four places.

1) JDE User DB User
2) iSeries
3) JDE.INI on both enterprise servers
4) SQL Server (Central Objects)

Thanks,

Nick

Does this mean that the jde user (network, database and EnterpriseOne) won't work while doing the upgrade?

Patty

Which upgrade was fatherp talking about? He failed to clue us in . . .

That is corrrect, the JDE user is no more in 8.10. PSFT takes its
place.

Be absolutely sure that the row and column security is not in effect
when doing the table conversions for 8.10. Relying on the fact that
'JDE has access to everything' will not cut it, as PSFT is actually used
to perform the upgrades.

fatherp, if you are referring to the PSFT Windows profile on the
deployment server, used to initiate the ftp of the iSeries ini file
during the host code installation, this can be set to whatever standards
a customer deems suitable. It is not used, in an iSeries environment,
after the upgrade effort is done, and the host code installation process
also you to type in the appropriate password. Be sure to disable the
ftp service on the deployment server when finished.

Brent Marxhausen
DBT, Inc.
Independent CNC
EMail: [email protected]

REcently completed an upgrade to 8.10 and has no issues