Setting up Queues

[Kari_1]

This may sound like a basic question but can anyone give me the instructions on how to set up multiple queues on the server? Is there a maximum number of queues we can have?

In addition to this, we have our scheduler server running on the enterprise server currently. Eventually all jobs will be processed on the batch server. Does this mean that the scheduler server must run on that server? Or can I leave it as is and make the change through OCMs?

Thanks

Kari
B7332 SP11, Intel NT4, SQL 7 SP1

 

[Bernd_Schade]

AW: Setting up Queues

Hi Kari.

change your JDE.INI settings for the amount of UBE's at the Enterprise
Server
like this one

[NETWORK QUEUE SETTINGS]
QEnv=CRP733
QUser=JDE
QPassword=
QueueDelay=5
UBEPriority=5
JDENETTimeout=60
UBEQueues=8
UBEQueue1=QB7331
UBEQueue2=test1
UBEQueue3=test2
UBEQueue4=test3
UBEQueue5=test4
UBEQueue6=test5

About the Scheduler:

All the UBE's will run at this Server which you have describe as your
Schedule Server

Bernd
-----Ursprungliche Nachricht-----
Von: Kari_1 [mailto:[email protected]]
Gesendet: Freitag, 12. Januar 2001 18:35
An: [email protected]
Betreff: Setting up Queues ~~0:3885


This may sound like a basic question but can anyone give me the instructions
on how to set up multiple queues on the server? Is there a maximum number of
queues we can have?

In addition to this, we have our scheduler server running on the enterprise
server currently. Eventually all jobs will be processed on the batch server.
Does this mean that the scheduler server must run on that server? Or can I
leave it as is and make the change through OCMs?

Thanks

Kari


--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OW&Number=3
885
*************************************************************
This is the JDEList One World / XE Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************

 

[scott_zuke]

Re: AW: Setting up Queues

This may have already been touched upon, but setting up multiple queues on a
Unix-based Enterprise Server is a little different.

You must modify your "RunOneWorld.sh" script to reflect the new queues.

This is what your script would look like in order to make QBATCH into a
multi-threaded queue capable of running 10 jobs at once. The new queue, QTEST
is shown after QBATCH. In this example, QTEST is single-threaded.

$SYSTEM/bin32/runque.sh JDE JDE PRODB732 QBATCH UBE 5 > runque1.log >2>&1 &
$SYSTEM/bin32/runque.sh JDE JDE PRODB732 QBATCH UBE 5 > runque2.log >2>&1 &
$SYSTEM/bin32/runque.sh JDE JDE PRODB732 QBATCH UBE 5 > runque3.log >2>&1 &
$SYSTEM/bin32/runque.sh JDE JDE PRODB732 QBATCH UBE 5 > runque4.log >2>&1 &
$SYSTEM/bin32/runque.sh JDE JDE PRODB732 QBATCH UBE 5 > runque5.log >2>&1 &
$SYSTEM/bin32/runque.sh JDE JDE PRODB732 QBATCH UBE 5 > runque6.log >2>&1 &
$SYSTEM/bin32/runque.sh JDE JDE PRODB732 QBATCH UBE 5 > runque7.log >2>&1 &
$SYSTEM/bin32/runque.sh JDE JDE PRODB732 QBATCH UBE 5 > runque8.log >2>&1 &
$SYSTEM/bin32/runque.sh JDE JDE PRODB732 QBATCH UBE 5 > runque9.log >2>&1 &
$SYSTEM/bin32/runque.sh JDE JDE PRODB732 QBATCH UBE 5 > runque10.log >2>&1 &

$SYSTEM/bin32/runque.sh JDE JDE PRODB732 QTEST UBE 5 > runque11.log >2>&1 &


QTEST is defined at the beginning of the script, simply copy the QBATCH line and
change it accordingly.

You also need to modiify the server JDE.INI file to support multiple UBEs. The
JDE.INI file should be changed to increase the maximum kernel jobs and by adding
more Kernel Type 2 processes.


Scott Zuke

 

[sf_woo]

RE: AW: Setting up Queues

Hi,

In our RunOneWorld.sh, we have the following :

echo "Starting OneWorld batch queues...\c"
$SYSTEM/bin32/runque.sh JDE jehovah PRODB732 QBATCH UBE 5 > runque1.log 2>&1
&
$SYSTEM/bin32/runque.sh JDE jehovah PRODB732 QBATCH UBE 5 > runque2.log 2>&1
&
echo "Starting package queue..."
$SYSTEM/bin32/runque.sh JDE jehovah PRODB732 QBATCH PKG 5 > bldo.log 2>&1 &
$SYSTEM/bin32/runque.sh JDE jehovah PRODB732 PBATCH UBE 5 > runque3.log 2>&1
&
echo "OneWorld startup finished!"
exit 0

and in JDE.INI on our HP-UX ES as follows :
[JDENET]
maxNetProcesses=1
maxKernelProcesses=6

[JDENET_KERNEL_DEF2]
maxNumberOfProcesses=1

I know something is definitely not right with the 2nd one. Was working with
JDE RL and changed the following :
- maxNetProcesses=2
- maxKernelProcesses=15
- maxNumberOfProcesses=10

and right after that, execution of business functions failed with error
inidicating the oracle listener could not start new /
addtional server process. All these while we had not even a single problem
with oracle at all. Reverted the change ever since
and no listener problem.

We do have weird problems with server jobs.

I'm still working at setting the JDE.INI right but I can't compromise on
stability / data integrity so I have to be sure that it works well. What are
the other related settings to look out for ie Unix kernel settings ? Believe
the problem we had is OS related - insufficient kernel processes, setting
for NProc is 2580.

Thanks.
Sook Fun
B7322 SP12.2, HP UX 11.0, Oracle 8.0.4
ES - single processor, 1 GB memory, approx. 40 users
Cognos, Impromptu 3rd party reporting tool - DSS

 

[Larry_Jones]

Re: RE: AW: Setting up Queues

Hey Scott and Sook,

do you really want to tell the World an ID and Password with substantial privileges on your UNIX server?

Anyway Sook, I think you're on the right track re the nproc kernel setting. Ours is set high @ 1024 and the max number of processes rarely reaches 400. We have a very similiar configuration but w/approx 80 concurrent users average.

[JDENET]
MaxNetProcesses - with your number of users 2 is a good number.
MaxKernelProcesses - should = SUM([JDENET_KERNEL_DEF*].maxNumberOfProcesses) + 1 (or more if BSFNs are mapped to the server)

[JDENET_KERNEL_DEF2]
maxNumberOfProcesses - doesn't need to = the number of batch queues - value may be higher or lower. I would suggest 3 on your server unless BSFNs are mapped to run on the enterprise server.

Below is our JDE.INI settings.

[JDENET]
netPgmName=jdenet_n
krnlPgmName=jdenet_k
serviceNameListen=6009
serviceNameConnect=6009
maxNetProcesses=5
maxNetConnections=400
maxKernelProcesses=29
maxKernelRanges=12
maxLenInlineData=1024
maxLenFixedData=4096
maxFixedDataPackets=1024
connectTimeout=5
singleProcess=0
netTrace=1
enableMsgPriority=0
enableGDMsgs=0
gdmRetryInterval=1000
newProcessThresholdConnects=0
netAdministrator=0
kernelDelay=0
krnlCoreDump=1

[JDENET_KERNEL_DEF1]
dispatchDLLName=libjdenet.sl
dispatchDLLFunction=JDENET_DispatchMessage
maxNumberOfProcesses=1
beginningMsgTypeRange=0
endingMsgTypeRange=255
newProcessThresholdRequests=0
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF2]
dispatchDLLName=libjdeknet.sl
dispatchDLLFunction=JDEK_DispatchUBEMessage
maxNumberOfProcesses=2
beginningMsgTypeRange=256
endingMsgTypeRange=511
newProcessThresholdRequests=0
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF3]
dispatchDLLName=libjderepl.sl
dispatchDLLFunction=DispatchRepMessage
maxNumberOfProcesses=1
beginningMsgTypeRange=512
endingMsgTypeRange=550
newProcessThresholdRequests=0
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF4]
dispatchDLLName=libjdeknet.sl
dispatchDLLFunction=JDEK_DispatchSecurity
maxNumberOfProcesses=4
beginningMsgTypeRange=551
endingMsgTypeRange=580
newProcessThresholdRequests=0
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF5]
dispatchDLLName=libtransmon.sl
dispatchDLLFunction=TM_DispatchTransactionManager
maxNumberOfProcesses=1
beginningMsgTypeRange=601
endingMsgTypeRange=650
newProcessThresholdRequests=0
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF6]
dispatchDLLName=libjdeknet.sl
dispatchDLLFunction=JDEK_DispatchCallObjectMessage
maxNumberOfProcesses=10
beginningMsgTypeRange=901
endingMsgTypeRange=1156
newProcessThresholdRequests=0
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF7]
dispatchDLLName=libjdeknet.sl
dispatchDLLFunction=JDEK_DispatchJDBNETMessage
maxNumberOfProcesses=4
beginningMsgTypeRange=1201
endingMsgTypeRange=1456
newProcessThresholdRequests=0
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF8]
dispatchDLLName=libjdeknet.sl
dispatchDLLFunction=JDEK_DispatchPkgInstallMessage
maxNumberOfProcesses=1
beginningMsgTypeRange=1501
endingMsgTypeRange=1756
newProcessThresholdRequests=0
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF9]
dispatchDLLName=libjdesaw.sl
dispatchDLLFunction=JDEK_DispatchSAWMessage
maxNumberOfProcesses=1
beginningMsgTypeRange=2000
endingMsgTypeRange=2256
newProcessThresholdRequests=0
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF10]
dispatchDLLName=libjdeschr.sl
dispatchDLLFunction=JDEK_DispatchScheduler
maxNumberOfProcesses=1
beginningMsgTypeRange=2501
endingMsgTypeRange=2756
newProcessThresholdRequests=0
numberOfAutoStartProcesses=1

[JDENET_KERNEL_DEF11]
dispatchDLLName=libjdeknet.sl
dispatchDLLFunction=JDEK_DispatchPkgBuildMessage
maxNumberOfProcesses=1
beginningMsgTypeRange=3001
endingMsgTypeRange=3256
newProcessThresholdRequests=0
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF12]
dispatchDLLName=libjdeknet.sl
dispatchDLLFunction=JDEK_DispatchUBESBSMessage
maxNumberOfProcesses=1
beginningMsgTypeRange=3501
endingMsgTypeRange=3756
newProcessThresholdRequests=0
numberOfAutoStartProcesses=0


FWIW

Larry Jones
[email protected]
OneWorld B733.1, SP 11.3
HPUX 11, Oracle SE 8.1.6

 

[scott_zuke]

Re: RE: AW: Setting up Queues

Larry,

The example that I relayed was not from my UNIX server. It was actually the
example that JD Edwards uses in their documentation. Do you have an issue with
using example data to properly clarify a situation?

If any customer has their ID and Password set to these values, then they have
larger issues than simply setting up queues.

Scott Zuke

 

[sf_woo]

RE: RE: AW: Setting up Queues

Larry,

Thanks for the reminder ! I'd take special note the next time.

1. For the MaxKernelProcesses, you mentioned + 1 (or more if BSFNs are
mapped to the server).
- How many should be added ie any formula ? Plan to map only a
couple of BSFNs - for SOP and Inventory.
- Do you have BSFNs mapped to the ES ?

2. [JDENET_KERNEL_DEF2] for maxNumberOfProcesses, suggested 3 and if
I'd like to do the above, how do I go about
getting the right figure.
- There's a document on 'Setting Up Multiple Batch Queues'
which states a suggested
value of 10 when defining multiple queues for ...DEF2. In
that sample given, UBEQUEUES=3 and each queue name is
defined as well under [NETWORK QUEUE SETTINGS]. What do you think of this ?
How many queues do you have ?

3. I have 2 additional entries in the [JDENET] section - maxNetJobs=4
and maxKernelJobs=4
- Any ideas ? Looked through the system admin manual, did not
find this in the sample JDE.INI.


Regards,

Sook Fun, Woo
Shriro (Malaysia) Sdn Bhd
OneWorld B732.2, SP 12.2
HP UX 11.0, Oracle 8.0.4

 

[Larry_Jones]

Re: RE: RE: AW: Setting up Queues

Sook,

1. We don't (currently) map BSFNs to the E.S. So I don't have any experience to lend you there.

2. I've seen the document 'Setting Up Multiple Batch Queues' and haven't given too much weight to a general number of 10.

Your questions have forced me to research this area and shed some light on my mis-information. Here's an quick summary of my current understanding of this area - I hope others with more knowledge will weigh-in where needed:

[JDENET]
maxNetProcesses - number of jdenet_n processes
maxNetConnections - max number of connections per jdenet_n process

jdenet_n processes may be 1 or more. They handle messaging between clients and server processes. A single jdenet_n process can potentially handle communications for hundreds of client connections without user's being aware of any delays. Having more than 1 jdenet_n process allows for load balancing in heavy traffic situations as well as increasing to total number of connections (maxNetProcesses * maxNetConnections)

jdenet_k processes serve multiple functions. There are jdenet_k processes that are dedicated to very specific functions (Security, Transaction Manager, etc) as well as undedicated processes that may be used for CallOBJ (server mapped BSFNs). The maximum number of jdenet_k processes is controlled by maxKernelProcesses setting.

As previously discussed the maxKernelProcesses value must be >= the sum of the maxNumberofProcesses values in each [JDENET_KERNEL_DEFx] section. Only kernel section 2 relates to application UBEs. The value here (maxNumberofProcesses) does NOT restrict the number of batch UBE jobs that may be running simultaneously. It simply defines how many UBE specific jdenet_k processes can run to handle batch requests passed from the jdenet_n process(es). After setup processing occurs and the job request is written to the F986110 table (polled by the JDEQUEUE processes) then jdenet_k is available to process the next request. If you have a high volume of UBE jobs submitted to the server (thousands an hour as some do) then this should be a significant number. Otherwise a relatively low setting may be used.

So really Sook, you can set the [JDE_KERNEL_DEF2].maxNumberofProcesses to 1 or 2 and still be good.

Now, I'm not clear on how the jdenet_k proccesses handle BSFN calls, the impression I receive from the documentation is that its 1 process per called object, but that's not real clear. Maybe someone else can tell us.

Well, this was real interesting for me - thx for the questions.


Larry Jones
[email protected]
OneWorld B733.1, SP 11.3
HPUX 11, Oracle SE 8.1.6