Re: How to Change One World password \"JDE\"
If you are trying to "lock down" your system by taking the jde/jde sign-on out of it, here is my solution.
1 - Don't remove jde/jde until you have implemented and tested everything else I put here.
2 - Decide on a completely new system sign-on (ADMIN/XYZ) that you want to use.
3 - Create network login for ADMIN. Copy the JDE sign-on to get all the permissions the same.
4 - Create database login for ADMIN on all databases. Again, copy the JDE login to get identical access.
5 - Create a OneWorld signon for ADMIN by copying JDE.
6 - It's a good idea to add a row in the OneWorld security app to grant ADMIN the right to run everything. (I always add this for the administrator in case I accidently lock *PUBLIC out of too much. This lets me get in to fix it.)
Start testing with a single OW user (USER1). In the security setup for USER1, change the system user and password to ADMIN/XYZ. Then try to sign on as USER1. Test getting in to applications, submitting UBEs to run on the server, etc...basic surface testing. Try to hit all the datasources for each environment. This will let you know that you got the database logins right.
Continue with a few more tests and remove JDE/JDE along the way...
7 - Sign on the the enterprise server as ADMIN/XYZ. Can you stop and start services with this sign-on?
8 - Change the jde.ini on the enterprise server to use ADMIN/XYZ instead of JDE/JDE. Can you still stop and start services? Submit jobs to run on the server?
9 - Run the OneWorld password application. Change the system user/password for all users (there is a checkbox) to ADMIN/XYZ. Test a few more signons and surface test.
10 - Remove jde/jde machine and network logins. Can users still signon and run in oneworld? Can ADMIN start and stop all services successfully? Does porttest run on enterprise server?
11 - Remove jde/jde database logins. Retest everything in #4 above.
I believe that is all. I'm sure someone will write and correct me if not. I strongly recommend this gradual change and test approach as it can be very time consuming to figure out what you missed if you try to do it all at once and miss something. Note that if after step #9, your users have any issues, you quickly change the system user back while you troubleshoot.
good luck...
owguru (at least I'm trying
>all versions
>all platforms