About Me

My photo
I work for Fusion5 Australia . Connect with me on linked in here . I'm raising money for a good cause at the moment, follow donate to leukemia foundation

Wednesday, 18 April 2018

Using orchestration recorder (Service Request Recorder) in tools

make sure that you have the UDC’s correct
Access the Feature Security application thru P00950 and add the following UDC values:


KY = RECORDER DL01 = Process Recorder SPHD = 1 HRDC = N


KY = RECORDER DL01 = Process Recorder SPHD = 1000 HRDC = N

Then proceed to activate the feature to be used in EnterpriseOne applications.

Here is a video to assist – my first vlog!

Tuesday, 17 April 2018

Install WLS on Linux

get a xterm or vnc session to the machine




next next next..


takes about 1 minute


Take note of where the logs are for later

Ensure that you launch the config assistant


and rename it to what you want – this might be helpful in SM

Note that I like e1apps and then release




I keep username default

dev mode, because I love boot.properties


choose all 3 because you need a machine


I’m already using 7001 and 2 so..


Node manager per domain


Leave clusters, but add a machine


Assign servers to machine


3 seconds later, done




job done


register with SM


Then choose 12c


Then enter the details of your install


don’t use any ‘.’s in the name


create instance!


interestingly I’m getting this in the console logs


Looks like the weblogic password is not being saved in SM properly

click on your domain name in SM, then add a server


Note that this password problem seems to the the cause of all my issues at the moment, as SM cannot talk to the admin server because the password is not saving.

This problem was silly me!!  The username was saved in the console as “weblogic “ there was a space at the end of the username, therefore when I saved the password it’d error out each time with a red error.  Eventually the system would lock out WLS.

I had to have the username as weblogic no space and use the save button (as below)


And then restart AdminServer at the command line, then save the password in SM – and it finally took!

I was then able to create my additional server easily


And now install JAS to it


Note that I have a 9201 running, so I’m going to take that down to avoid locking.




it seems that you can create without a node manager.

But you cannot start or synchronize the content without a nodeManager

Now my JDE works, I do not get the stuck thread issues that I was with is released, so let’s upgrade WLS to–or NOT

MTR’s say that we are good to go:


Nice to put on the latest, but…

Then I find:




As of WebLogic Server 12.1.2, Oracle no longer provides upgrade installers. You must install WebLogic Server to a new directory location. You cannot install it over an existing installation.

Doh!  I thought that there might be a nice little (or big) opatch that I could apply – but it seems that things are a little more difficult than that.

I’m trying to solve an issue with and WLS on OEL that is not allowing me to login to JDE, getting stuck threads on the login page:

####<Apr 17, 2018, 1:11:22,535 PM AEST> <Error> <WebLogicServer> <ip-10-10-1-235.ap-southeast-2.compute.internal> <IOT_AISWEB_9201> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <00c06b7e-0c5a-4892-b8bb-79a54660fc84-0000001e> <1523934682535> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000337> <[STUCK] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "708" seconds working on the request "Http Request Information: weblogic.servlet.internal.ServletRequestImpl@5d9d6b3e[POST /jde/E1Menu.maf]
", which is more than the configured time (StuckThreadMaxTime) of "600" seconds in "server-failure-trigger". Stack trace:
         sun.nio.ch.EPollArrayWrapper.epollWait(Native Method)

Yet when I install this on – all works fine.

I’ve applied a bunch of patches to try and get it working (including 26860993), oh after removing others

/Oracle_Home/OPatch/opatch rollback -id 26485996

/Oracle_Home/OPatch/opatch rollback -id 24521759

but still no logging into JDE – stuck during login.

So, I may try more patching or a new instance at and see if I can login to JAS

Let me know if you have the same issue.

Monday, 16 April 2018

JDE920 and JDE910 batch job performance summary for AS/400 SQL

The following SQL will give you a summary of all batch jobs and how long they’ve taken to run (in seconds) on average on an AS/400 – note that this is specific syntax for the 400.  The date arithmetic is also quite specific for the AS/400.

   count(1) as INNERCOUNT,
   Avg((DAYS(jcetdtim) - DAYS(jcstdtim)) * 86400 + (MIDNIGHT_SECONDS(jcetdtim) - MIDNIGHT_SECONDS(jcstdtim))) as INNERAVERAGE,
   min((DAYS(jcetdtim) - DAYS(jcstdtim)) * 86400 + (MIDNIGHT_SECONDS(jcetdtim) - MIDNIGHT_SECONDS(jcstdtim))) AS INNERMIN,
   max((DAYS(jcetdtim) - DAYS(jcstdtim)) * 86400 + (MIDNIGHT_SECONDS(jcetdtim) - MIDNIGHT_SECONDS(jcstdtim))) AS INNERMAX, avg(jcpwprcd) as "ROWS PROCESSED"
from svm910.f986114 t1,ol910.f9860, copd910.f983051, svm910.f986110 t2
where trim(t1.jcpid) = trim(siobnm)
and trim(t1.jcvers) = trim (vrvers)
and trim(t1.jcpid) = trim (vrpid)
and t1.jcjobnbr=t2.jcjobnbr
and t1.jcexehost = 'SYDJDE01'
group by  t1.jcpid, JCVERS, simd || vrjd ;

to reveal


Like my data obfuscation?

So you can quickly see long running jobs or compare averages.

The things that I want to remember out of this is the AS/400 syntax.

Thursday, 12 April 2018 JD Edwards has been released

There are some exciting enhancements in this release, please look at https://docs.oracle.com/cd/E53430_01/EOTNC/software_updates.htm#EOTNC223 for some more information.

I'll be demonstrating the orchestration changes in a series over the next week.

In particular - look for :
launching BV's and changing data selection and processing options:

a new report type service request.

imageGreat if you want to change data selection or POs for the launch


output overrides can be specified too

In Server Manager, you can enable error and exception handling for orchestrations. When enabled, each exception in an orchestration is saved as a single serialized JSON object and stored in a directory on the AIS Server. In addition to storing these files, the directory serves as a buffer for storing orchestration requests if the EnterpriseOne system is down.

When creating orchestrations, business analysts can include an array as an orchestration input, defining the set of data to pass within the array. You can use an array in two ways: with the orchestration ”Iterate Over” feature to repeatedly call a service request for each row in the array; or add to or update a grid by referencing the array name inside the service request at the grid level.


New FTP connector has been added

Wednesday, 4 April 2018

One bad orchestration can ruin the entire testing platform

This problem took too long to solve, but let me tell you about it – as it might save you some time.  I’ve been creating orchestrations of various complexity and am enjoying the tasks.  There are a number of things that I’d like to see improved -

  • math_numeric handling of return values-  not everything is a string.  There needs to be some native casting capabilities.  This occurs when you create a new AN8 (for example) and then want to pass that into the P0092 form as the users AN8.  It’s passed back as a string and the orchestration does not work.  You also cannot change this.  Frustrating to need to use data service to get a number back.


  • You do not see return values until you save or change something in the orchestration studio


  • Complex logic is not going to happen in the standard development environment, you will need to write some java


That’s just my list at the moment, let’s settle back for the current problem though.

I just created a new custom orchestration which added a work order, nice – I’ve done this a number of times before.  Very simple form request and then an orchestration over the top.  But, something went wrong.

When I went to test it (or ANY orchestration, I did not get any parameters in the list).

It looked like the following

   <shortDesc>Add a WO for a thing that you get out of the cross reference</shortDesc>
   <inputFormat>JDE Standard</inputFormat>
     <inputTypes type="String" required="false">
     <inputTypes type="String" required="false">
     <orchestrationSteps type="ServiceRequest" omwObjectName="SRE_1804030006CUST">
         <transformations input="orch_inputszUnitNumber" output="inStringUnitNumber"/>
         <transformations input="orch_inputszFailureDescription" output="szFailureDescription"/>

If you were to try and import this into your orchestration studio, you might find the same problem:


See that all of my parameters are missing!

But, if I delete the orchestration (now that I know the one).

using P98220U



It immediately starts working again


Very strange.

to solve this I did spend hours debugging logs, installing new tools releases, restarting everything…  deleting UDO’s and more.

If you do not see parameters in the orchestration client, take a look at the last orchestration that you created!

very basic post, OEL RHEL change TZ for proper date and time stamps

The little things get to me when I'm troubleshooting, like date and time. 

If I look at the machine and NTP is set up properly but my timestamps are wrong, then generally this is going to be related to TZ. Very simple steps to getting this right for Melbourne: 

 To validate that this is your problem, you can enter the command below: 

It gives you some really cool information about daylight savings and NTP - which you need to know.

[root@ip-10-10-1-235 ~]# timedatectl
      Local time: Tue 2018-04-03 23:24:28 UTC
  Universal time: Tue 2018-04-03 23:24:28 UTC
        RTC time: Tue 2018-04-03 23:24:28
       Time zone: n/a (UTC, +0000)
     NTP enabled: yes
NTP synchronized: yes
 RTC in local TZ: no
      DST active: n/a

Okay, this needs to be fixed!  See how there is no information about DST or TZ

One simple command as root

ln -sf /usr/share/zoneinfo/Australia/Melbourne /etc/localtime

Then viola!

[root@ip-10-10-1-235 ~]# timedatectl
      Local time: Wed 2018-04-04 09:21:07 AEST
  Universal time: Tue 2018-04-03 23:21:07 UTC
        RTC time: Tue 2018-04-03 23:21:06
       Time zone: Australia/Melbourne (AEST, +1000)
     NTP enabled: yes
NTP synchronized: yes
 RTC in local TZ: no
      DST active: no
 Last DST change: DST ended at
                  Sun 2018-04-01 02:59:59 AEDT
                  Sun 2018-04-01 02:00:00 AEST
 Next DST change: DST begins (the clock jumps one hour forward) at
                  Sun 2018-10-07 01:59:59 AEST
                  Sun 2018-10-07 03:00:00 AEDT

Cool, and yes - DST did change on Sunday.  Nice reminder. 

 You can work out your own settings from this example.