EnterpriseOne Event Rules Debugger Broker Error
Filed under: BPM Broker, E1Tips, EnterpriseOne - General
The other day I was notified by a developer that he was receiving the errors pictured to the left when opening the debugger. The application looked like it opened just fine and then right before it was done, these errors would appear.
I checked all the logs and re-installed the BPM Broker but the error persisted.
Then I searched the My Oracle Support site and… tada! A hit. Knowledge Base ID 661700.1 had the solution.
There are about 5 different solutions listed and, of course, my issue was resolve with solution #5.
1. For 8.97 and higher Tools Releases Only:Make sure the following DLL files are registered on the workstation using the command
regsvr32 <Drive Letter>:\<E1 Release>\system\bin32\<DLL name>
E1Soap.dll
DebuggerService.dll
WinUBEDbgService.dll
JDEBPMSoap.dll
JDEBPMSockets.dll
I’m not sure which DLL was having the issue, but after I ran through these commands the error went away.
Hope this helped.
Tags: BPM Broker, e1, E1Tips, enterpriseone, EnterpriseOne - General, jde, oracle, Tools Release, ube
Hitler and the CNC Guys – Jeff Stevenson
Filed under: IBM i/System i/iSeries/AS400, Oracle Server Manager, SAP, enterpriseone, oracle
You got to check this video out by Jeff Stevenson of the Karamazov Group Blog:
Tags: cnc, e1, enterpriseone, IBM i/System i/iSeries/AS400, oracle, Oracle Server Manager, SAP, ubeJDE, XML and Bi Publisher
Tim Dexter has a helpful little article at the Oracle Bi Publisher Blog about consuming the XML that is produces by E1 UBEs.
Thanks, Tim!
Tags: e1, jde, oracle, ube, XMLEnterpriseOne 8.12 Functionality with Version 8.11 SP1
Filed under: EnterpriseOne - JAS (Java Application Server), EnterpriseOne - SQLs, IBM i/System i/iSeries/AS400
Background:
In developing the Employee Self-Service user interface without using the portal, the development team had a need to be able to print out an employee’s paystub and have it emailed to them. The email portion of the process is handled by Optio but before it gets to the Optio server, it needs to be sent to an outqueue on the Enterprise Server. Because of the flow of the UBE submission application, upon requesting the paystub (UBE) the user is presented with a printer selection verification screen. It was decided that this screen would be pretty confusing to those employees that do not use EnterpriseOne regularly. So, the developer found a way around that. She submitted the UBE using a Named Event Rule (NER).
Issue:
Because of using the NER to submit the UBE, the Print Immediate parameter in the JAS.INI file doesn’t get read. This is because it is being submitted by the Enterprise Server instead of the JAS server. If the job isn’t printed, or sent to an outqueue, then the PDF never gets to the Optio server to be processed and emailed to the user.
Resolution:
After consulting with Oracle Support, we changed the VRVCC3 field of the F983051 to contain a ’1′ in the record of the UBE Version that we wanted to Print Immediate. Apparently, this version Print Immediate parameter is used in the 8.12 applications but is also read in the 8.11 SP1 version.
Note: We are using 8.11 SP1 and this solution may or may not work with earlier versions.
Tags: enterpriseone, EnterpriseOne - JAS (Java Application Server), EnterpriseOne - SQLs, IBM i/System i/iSeries/AS400, jas, oracle, ube, version, versionsEasing The EnterpriseOne Learning Curve
In the past year or so I have been training a very good new CNC Administrator. He’s been working with IT and World for quite a long time and is very good at picking up new things.
In doing this, sometimes I have to think back and try and see things from a more innocent, un-jaded view. Also, I try to think about what has helped me the most in learning this complex, overly-convoluted architecture?
There are the obvious answers:
- Experience
- Terminology (this was huge for me)
- EnterpriseOne SysAdmin classes
- Loyal participation in JDEList
- Etc.
However, one of the things that helps me the most when troubleshooting an issue that can’t be resolved by the normal logs and error messages is…
having a development background and the E1 developer classes.
Why? Well, as a Systems Administrator, I think I see how the system works a little better than a developer. As a developer, I am able to use the tools to logically follow the process of an application or UBE from beginning to end.
I’m sure others can put this a lot more eloquently than I, but you get the idea.
What do you think? What skill helps you out the most when troubleshooting difficult issues?
Tags: cnc, e1, enterpriseone, EnterpriseOne - General, jde, ube, worldMore E1 Software From Down-Under!
I’ve talked about Everest Software International’s EnterpriseOne utilities software before…particularly, Boomerang and Update Queue Names In Versions.
In their latest newsletter (yes, it is worth subscribing to), Alex highlights 3 software offerings:
- ESI Benchmark 2008: “It allows easy comparison of the performance of different servers in real, JDE-like terms.” This may prove to be very beneficial when looking to purchase upgrades.
- Boomerang: “…it now supports the new Tools Release 8.97 and the latest version is even more stable and reliable than ever before.” This product is invaluable, if you deal with multiple EnterpriseOne installations in any way.
- XML InSPECtor: A new offering that can be used to work with 8.12′s new XML specs. “…it can be used for, it would allow simple changing of the underlying BSVW’s in UBE’s and APPL’s, by simply replacing all references to the old BSVW with a new one, the list of possible applications is endless.” “Endless” is right. I am very excited to see this tool in action!
I haven’t had experience with all of what Everest Software International has to offer but, the site definitely warrants a look. They have a tool for doing almost everything that you wish E1 could do on it’s own.
Thanks, Alex!
Tags: e1, enterpriseone, EnterpriseOne - General, jde, Tools Release, ube, version, versionsODBC, QCMDEXC and RUNUBE
I have been working on an ODBC command that I would like to call from an ASP.Net application. It will be used to submit UBEs to a held job queue. Then each night at a specified time the job queue will be released and the jobs will run. This is to try and offset the miserable E1 job scheduler.
Anyway, here is what the SQL looks like:
CALL QCMDEXC ('RUNUBE USER(*****) PASSWORD(******) ENVIRON(JPD811) REPORT(R0010P) VERSION(ZJDE0001) JOBQ(********) IORB(B)',0000000107.00000)
The QCMDEXC is quite the little beast. If you plug the above code into STRSQL on the System i, you will need to count the spaces at the end of each line and add that to the 107 length.
The bad part is that I can get this to work on the System i STRSQL, but not from the ASP.Net page. I have looked through all kinds of web sites and haven’t found a solution.
So, if you have a solution for me, I would really appreciate it.
Tags: e1, EnterpriseOne - SQLs, ibm, iseries, jde, odbc, sql, strsql, system i, ube, version, xeEnterpriseOne (E1) Batch Job Runtimes
Filed under: EnterpriseOne - General, EnterpriseOne - SQLs, IBM i/System i/iSeries/AS400
We had someone ask this question the other day:
Can you tell me what jobs run for over 30 minutes?
Well, that seemed simple enough…
- Take the last action time and subtract the submit time and your good:
SELECT JCJOBQUE as JobQueue, JCENHV as Environment, JCUSER as User, substr(jcfndfuf2,0,locate('_',jcfndfuf2) + locate('_',substr(JCFNDFUF2,posstr(jcfndfuf2,'_')+1))) as JobName, concat(concat(JCSBMDATE,'-'),JCSBMTIME) as Submitted, concat(concat(JCACTDATE,'-'),JCACTTIME) as Ended, (jcacttime - jcsbmtime) as Runtime FROM svm811/f986110 order by Runtime
Ok, I did a little more than that to make it look good. Anyway, the “Runtime” column will be numeric with a length up to 6 digits. So, it could be read in this format: HHMMSS.
Not, too bad, right? Well, the problem comes in when you have a job that runs over 235959. The following is a very lengthy and ugly piece of SQL. It can probably be done more simply so, if you know of a better way, please let me know. Believe it or not but, I split up the lines a little so it would be easier to read.
1: SELECT JCJOBQUE as JobQueue,
2: JCENHV as Environment,
3: JCUSER as User,
4: substr(jcfndfuf2,0,locate('_',jcfndfuf2) +
5: locate('_',substr(JCFNDFUF2,posstr(jcfndfuf2,'_')+1))) as JobName,
6: concat(concat(JCSBMDATE,'-'),JCSBMTIME) as Submitted,
7: concat(concat(JCACTDATE,'-'),JCACTTIME) as Ended,
8: timestampdiff(4,cast(
9: (timestamp(date(char(jcactdate+1900000)),
10: time(
11: insert(insert(right(char(digits(jcacttime)),6),3,0,'.'),6,0,'.'))))
12: -(timestamp(date(char(jcsbmdate+1900000)),
13: time(
14: insert(insert(right(char(digits(jcsbmtime)),6),3,0,'.'),6,0,'.'))))
15: as char(22))) as Runtime
16: FROM svm811/f986110
17: order by Runtime
What the heck did I do? Well, lets go through it (IBM V5R4 SQLReference):
- Lines 1-3: Basic stuff to make the result make more sense.
- Lines 4-7: Remove the extra junk on the job name
(I only want the UBE and the version). - Line 8: Start the timestampdiff function.
The first argument determines the interval that you
want the result in. The second is required to be cast
to CHAR(22) datatype. - Line 9: Start the LastActivity date portion of the timestamp.
- Line 10: Start the LastActivity time portion of the timestamp.
- Line 11: First create a 6 digit numeric value. Then create a char
datatype in the format: HH.MM.SS - Line 12: Start the Submit date portion of the timestamp.
- Line 13: Start the Submit time portion of the timestamp.
- Line 14: Essentially the same as Line 11.
- Line 15: Finish the Cast function and return a nice name.
- Line 16: The table that we use.
- Line 17: Give it some order.
Who Has Access To That In EnterpriseOne (E1)?
Filed under: EnterpriseOne - SQLs, EnterpriseOne - Security
There are many things that I find frustrating about the GUI tools for EnterpriseOne (E1), especially when doing Systems Administration functions.
Apparently, I’m not the only one. We give read-only access to most of the SysAdmin applications to our developers. You may have your own opinions about that, but it’s what we chose to do.
Anyway, our development manager gets a lot of CNC-type questions from our users and doesn’t like to always “bother” us with them. One of the questions she gets is “Who has access to the
Note: iSeries DB2 syntax
SELECT ABALPH, FSOBNM, RLFRROLE, RLTOROLE
FROM SY811/F00950, SY811/F95921, SY811/F0092, PRODDTA/F0101
WHERE FSOBNM = ‘PXXXX’ AND
FSUSER = RLFRROLE AND
RLTOROLE = ULUSER AND
ULAN8 = ABAN8
Thanks Deb!
FTP & iSeries
Ok, we have some UBEs that run and they produce a text file in the IFS System on our i550. In the processing options of these UBEs, the user can specify the name that they would like the file to have. Since their UI to the system is through the web, when they put in things like “c:\401k.txt” or “c:\insmembers.txt” the file gets placed into the root of the IFS system as a file with the name “c:\401k.txt” or “c:\insmembers.txt”. They look very strange in iSeries Navigator. And, oh by the way, you can’t delete them. The only way that I have found to delete them is by using the windows command line FTP. Here is what I do to get rid of them:
- Once logged in through FTP, type quote site namefmt 1 to change to the IFS naming format. You’ll notice that, if you do a pwd, the working directory is “/QSYS.LIB/QGPL.LIB”.
- You need to get to the root so, type cd .. [ENTER] cd .. [ENTER]. You should get a response that says your current directory is “/”.
- Then either use del or mdel and delete the files.
More on switching between the library file system and the directory file system when FTPing an AS400:
quote site namefmt [0|1]
- Summary:
- 0 – specifies the library file system
- 1 – specifies the directory file system
- Detail:
- NAMEFMT 0 | 1 : Specifies the naming
format that identifies file locations inside your FTP session.
- NAMEFMT 0 assumes that you’re only copying
files into and out of the QSYS.LIB file system using the DB2 UDB naming format of
library/file.member.- NAMEFMT 1 is used for identifying files
in all IFS file locations, and all files or locations must be listed in IFS notation
(like /home/dir, /QOpenSys/dir, /QDLS/dir, /QSYS.LIB/dir.lib/file.file). To view the
current NAMEFMT values for your FTP session, type NAMEFMT or QUOTE SITE NAMEFMT without
any parameters.



