• Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

Security Server problem

Hi, this is my first post here. I have just joined the JDE Oneworld
community and will probably be asking the most silly questions for a while.
I do have a problem at the moment though with our security server.

I am running:

Ent: Sun e450 running Solaris 2.7
2Gb RAM
Lots of disk space
2 procs
Oracle 8.1.6

Dep Compaq ML530
Specs not important for this problem

I have a situation where the QB7332 queues do not start up when I run
./RunOneWorld.sh
It does start the kernel, network and scheduler at this point.
We have a workaround where the JDE.INI is edited on the server. The
security server='ent server name' has the name of the server removed, then
the ./RunOneWorld.sh script is run - the queues all come up, but no clients
can attach until the ent server name is put back into the JDE.INI
This is very scary as we are going live in the next two days.
The workaround is fine unless the box needs a reboot, at that point the
workaround needs to be reapplied

Now, the only thing I can think of that would have had an effect on this is
the I changed the JDE login into OneWorld about two weeks ago (For security
reasons)
This does not effect the JDE login into oracle as that has not been changed,
so I cant think of anything that RunOneWorld calls that needs a OneWorld
login as opposed to an Oracle login.
And no, I havent changed it back yet to test that theory as it cannot be put
in that state as users would be able to cause havoc if that was the case

Has anybody seen this before?

Ken Newman
JDE CNC Technical Support
Spectrasite Transco Communications Ltd
Cellphone: 0777 902 8804


________________________________________________________________________
This message has been checked for all known viruses, by Star Internet,
delivered through the MessageLabs Virus Control Centre.
For further information visit:
http://www.star.net.uk/stats.asp
 

MSiebenschuh

Well Known Member
Hey Ken,
Welcome to the list. Sure sounds like your JDE login is indeed the
problem. I know that when I changed mine many moons ago it took quite a
while to get it just right. There have been some great posts about changing
the JDE user/pass lately so you might want to search the archives and make
sure you hit all the right tables. Since you aren't live yet I would do a
quick test and reverse the change. At least that will let you know if you
are heading down the right path. Also are you getting anything in your
JDE.LOG/JDEDEBUG.LOG when you start up. It should be relatively short and
sweet basically a line or two ea. for the JDENET_N, JDENET_K and each queue.

Mark Siebenschuh
HP9000/Oracle 8.0.5/JDEB733 Base
 
<html><DIV>


Hi Ken,</P>


Check the account that are used to start the JDEQUE service has been setup correctly and supplied with the correct password.</P>


Also double check JDE documentation on changing the JDE password to check you have followed all the steps.</P>


Also check that you have setup dependencies on JDENET and JDEQUE services, as JDEQUE sometimes may not start correctlyautomatically on boot if this is not setup. </P>


If need more info then email me.</P>


Regards</P>


John</P>


NT4/SQL7/B7332/SP10.1</P></DIV>
<DIV></DIV>
<DIV></DIV>>From: Ken Newman <KEN.NEWMAN@SSTUK.COM>
<DIV></DIV>>Reply-To: jdelist@jdelist.com
<DIV></DIV>>To: jdelistml@jdelist.com
<DIV></DIV>>Subject: Security Server problem ~~0:3547
<DIV></DIV>>Date: Tue, 9 Jan 2001 02:56:24 -0800 (PST)
<DIV></DIV>>
<DIV></DIV>>Hi, this is my first post here. I have just joined the JDE Oneworld
<DIV></DIV>>community and will probably be asking the most silly questions for a while.
<DIV></DIV>>I do have a problem at the moment though with our security server.
<DIV></DIV>>
<DIV></DIV>>I am running:
<DIV></DIV>>
<DIV></DIV>>Ent: Sun e450 running Solaris 2.7
<DIV></DIV>> 2Gb RAM
<DIV></DIV>> Lots of disk space
<DIV></DIV>> 2 procs
<DIV></DIV>> Oracle 8.1.6
<DIV></DIV>>
<DIV></DIV>>Dep Compaq ML530
<DIV></DIV>> Specs not important for this problem
<DIV></DIV>>
<DIV></DIV>>I have a situation where the QB7332 queues do not start up when I run
<DIV></DIV>>./RunOneWorld.sh
<DIV></DIV>>It does start the kernel, network and scheduler at this point.
<DIV></DIV>>We have a workaround where the JDE.INI is edited on the server. The
<DIV></DIV>>security server='ent server name' has the name of the server removed, then
<DIV></DIV>>the ./RunOneWorld.sh script is run - the queues all come up, but no clients
<DIV></DIV>>can attach until the ent server name is put back into the JDE.INI
<DIV></DIV>>This is very scary as we are going live in the next two days.
<DIV></DIV>>The workaround is fine unless the box needs a reboot, at that point the
<DIV></DIV>>workaround needs to be reapplied
<DIV></DIV>>
<DIV></DIV>>Now, the only thing I can think of that would have had an effect on this is
<DIV></DIV>>the I changed the JDE login into OneWorld about two weeks ago (For security
<DIV></DIV>>reasons)
<DIV></DIV>>This does not effect the JDE login into oracle as that has not been changed,
<DIV></DIV>>so I cant think of anything that RunOneWorld calls that needs a OneWorld
<DIV></DIV>>login as opposed to an Oracle login.
<DIV></DIV>>And no, I havent changed it back yet to test that theory as it cannot be put
<DIV></DIV>>in that state as users would be able to cause havoc if that was the case
<DIV></DIV>>
<DIV></DIV>>Has anybody seen this before?
<DIV></DIV>>
<DIV></DIV>>Ken Newman
<DIV></DIV>>JDE CNC Technical Support
<DIV></DIV>>Spectrasite Transco Communications Ltd
<DIV></DIV>>Cellphone: 0777 902 8804
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>________________________________________________________________________
<DIV></DIV>>This message has been checked for all known viruses, by Star Internet,
<DIV></DIV>>delivered through the MessageLabs Virus Control Centre.
<DIV></DIV>>For further information visit:
<DIV></DIV>>http://www.star.net.uk/stats.asp
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>--------------------------
<DIV></DIV>>To view this thread, visit the JDEList forum at:
<DIV></DIV>>http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=3547
<DIV></DIV>>*************************************************************
<DIV></DIV>>This is the JDEList One World / XE Mailing List.
<DIV></DIV>>Archives and information on how to SUBSCRIBE, and
<DIV></DIV>>UNSUBSCRIBE can be found at http://www.JDELIST.com
<DIV></DIV>>*************************************************************
<DIV></DIV>>
<DIV></DIV><br clear=all><hr>Get your FREE download of MSN Explorer at http://explorer.msn.com
</p></html>
 

Larry_Jones

Legendary Poster
Ken,

Congratulations on an imaginative work-around!

But since you don't want to keep on running this way, check your RunOneWorld.sh script for the lines that contain runque.sh. The runque.sh script is what starts the queue processes and takes 3 or 6 arguments on its command line. If you see 6 arguments then the first 3 are the OW User, OW password, and Default environment. If only 3 are passed or the first 3 are blank then the values will be read from the [NETWORK QUEUE SETTINGS] section of the JDE.INI file (QUser, QPassword, and QEnv).

I suspect what is happening is that runque.sh is being passed the old JDE password which you will need to change (either in RunOneWorld.sh or in the JDE.INI file). Depending on what version you have of RunOneWorld.sh all of this is explained in comments at the beginning of the script (if you have the long version).

Hope this helps,

Larry Jones
ljones@wagstaff.com
OneWorld B733.1, SP 11.3
HPUX 11, Oracle SE 8.1.6
 
Top