Server Management Will Not Start After Update

We are updating our EnterpriseOne Tools Release to 8.98.2.2 and had an issue with updating the Server Manager Agent on our Windows web servers. After following the steps to do the update of the Server Manager Agent it would not restart. I was able to find a document (Doc ID 983043.1) on Oracle Support that fixed the issue.

To resolve this issue, Customers need to download the 8.98.2.2 (or newer) version of the Server Manager update component and proceed with the following steps:

Update your Server Manager console with the newer version of Server Manager.

Locate the “scfagent.jar” file in the following directory:
{jde_home}\targets\oc4j\j2ee\home\applications\ManagementConsole\ManagementConsole_WAR\scfagent
where {jde_home} is your Server Manager console install location.

Copy this file to the following directory on the machine where your Windows Server Manager agent is running:
{jde_agent_home}\lib\_staging
where {jde_agent_home is the Server Manager agent install location

Rename the “scfagent.jar” file that you have copied to “agentUpdate.jar”. If there is already a file with this name, it should be replaced with the new file you have copied.

Run the “startAgent.bat” command file twice from the {jde_agent_home}\bin directory. The first time will update the Server Manager agent JAR files with the newer version, but will likely fail to start the service. The second time should start the service successfully.

I hope that helps!

EnterpriseOne Event Rules Debugger Broker Error

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. 

Batch Version (P98305W) Version Error

After our latest tools release update there was a special instruction that I forgot to do on one of the environments.  It was to delete all versions of the Batch Versions (P98305W) application.  Usually, there will be just one version: ZJDE0001.

Well, since I forgot, to the left is the error that you might get if you don’t do it.  The second image is the Interactive Versions screen that you will need to use to delete the version.

Oracle Give Away Extended Support

I got this email this morning:

Dear JD Edwards EnterpriseOne Customer,

During the recent COLLABORATE conference Oracle President Charles Phillips announced that Oracle will waive first year Extended Support fees for certain product lines. This includes 8.11 and 8.11 SP1 for JD Edwards EnterpriseOne.

What is Extended Support?
Many JD Edwards legacy programs are supported under Oracle’s Lifetime Support Policy. This means that when Premier Support ends, you may continue to receive updates, and legislative and regulatory fixes for an additional three years under Oracle’s Extended Support. Please be sure to review Oracle’s Lifetime Support Policy for details regarding each JD Edwards release.

How Does this Affect You?
All customers currently using JD Edwards EnterpriseOne 8.11 and 8.11 SP1 will have the first year of their Extended Support fee waived. After that you will have the option of continuing your Extended Support service, and can contact your Support Sales representative to initiate the purchasing process.

For more information, please review the following article on MetaLink 3, NOTE: 778948.1, or contact Global Customer Support for further questions.

I wonder if you still get the HelpDesk101-type support when you first call?  I’m not trying to be negative, but you know what I mean:

• Have you applied all the ESUs?
• Have you modified the object?
• Are you on the latest Tools Release?
• Could you send me a full set of logs for both the web server and the enterprise server? – Yeah, sure. Have funning going through 2 GB of TEXT!

Anyway, it may be a good deal.

EnterpriseOne Javascript Error Causing Errors In Internet Explorer

We recently went live with Employee Self-Service.  In doing so, we no longer send employees their direct deposit pay stub.  Over the last few days we were notified that some employees were unable to view the paycheck details. 

We began troubleshooting the issue with looking at the usually culprits:

• Browser used (Firefox doesn’t work with EnterpriseOne Tools Release 8.97)
• Browser security settings (EnterpriseOne & IE7)
• Browser add-ons/plug-ins/extensions

However, nothing seemed suspect.

So, I put on the Web Developer Hat (don’t tell Charlie) and started troubleshooting.  I found that there was a Javascript error in Internet Explorer.  I tracked down the offending file an commented out the code.

The Javascript file that I changed was /js/JDEDTA.js.

The specific line that was causing the problem was line 344.  I commented out the whole thing because who needs “typeahead” functionality in Employee Self-Service?

340:    this.saveAutoCompleteData = function(){

341:        //Hack to make typeahead work in IE

342:        /*if(document.all){

343:            var formToPost = document.forms[this.formName];

344:                  window.external.AutoCompleteSaveForm(formToPost);

345:        }else if (!this.isSafari){

346:            var formToPost = document.forms[this.formName];

347:              if (formToPost)

348:              {

349:                  var action = formToPost.action;

350:                  formToPost.action = "javascript:void(0)";

351:                  formToPost.submit();

352:                  formToPost.action = action;

353:              }

354:        }*/

355:    }

EnterpriseOne Tools Release Upgrade From 8.96 to 8.97 Rough Outline

1. IBM iSeries/AS400/System i
1. Backup libraries and IFS directories
2. Register Pristine Environment in Server Manager
3. Create Server Manager Server Group for Pristine
4. Upgrade Pristine
2. Web Server
1. Create IBM WebSphere Application Server in Server Manager
2. Create IBM HTTP Server in Server Manager
3. General
1. HTML landing page: update links and info
2. Change DNS entries
3. Copy the code used to restrict access to specified environment
4. Copy images and code for custom backgrounds
5. Modify the JAS.INI file to specify the correct logon logo
6. Set web server to restart nightly and cleanup logs
7. Verify that the server is being backed up and replicated to DR hot site

Handy eGen Tweak

In order to shorten the time that it takes to run the eGen process, I modify a couple settings in the gen.bat file.  They modify the memory that is used by the JVM.

• ms128m –> ms512m
• mx512m –> mx1024m

The full line in the gen.bat looks like the following:

• %JAVA_PGM% -Xss1m -ms512m -mx1536m -Ddefault_path=%INI_DIR% -classpath %GEN_CLASSPATH% com.jdedwards.runtime.generator.Generator %1

NOTE: This is on a workstation with 2GB RAM running Tools Release 8.97 and the settings are what I use.  This is not a recommendation from Oracle.

Do you have any tweaks for the eGen process that you use?

Egen Process JDBJ Gotcha

When setting up a workstation to perform the eGen process, once in a while there is a step that I seem to forget.  It has to do with two settings in the JDBJ.INI file that need to be changed from their default values and JDBJ driver files:

• [JDBj-SPEC DATA SOURCE] – This whole stanza needs to be commented out.  If you don’t, the eGen application will here for the location to which you want to generate your serialized objects, which is defaulted to the local MSDE database.
• [JDBj-JDBC DRIVERS] – The values in this stanza are commented out by default.  You will need to uncomment the drivers that are appropriate to your installation.  For me, that is:
• AS400=com.ibm.as400.access.AS400JDBCDriver
• SQLSERVER=com.microsoft.jdbc.sqlserver.SQLServerDriver
• JDBJ Driver Files – The four files below need to be copied to the C:\e811\MISC directory. 
• jt400.jar
• msbase.jar
• mssqlserver.jar
• msutil.jar

NOTE: This information is for Tools Release 8.97 and may be different for other versions.

EnterpriseOne Tools Release 8.97 & 8.98 Not Compatible With FireFox 3

In doing some last minute testing with EnterpriseOne Tools Release 8.97.2.0, I found that the applications do not render in FireFox 3.  The error that I received in the WAS log is:

VTFormRenderAdaptee: renderHTML4: failed to render:
java.util.MissingResourceException:
Can't find bundle for base name nls.CPResource, locale

This issue is documented under MetaLink BUG 8917620 & 8917611.  The final disposition that is documented as:

Fixfox 3 does not work with e1 due to build id length

change in user agent string, and E1 fail to match it to

firefox pattern with shorter build date pattern.

The following is useragent string for

FF2: MOZILLA/5.0 (WINDOWS; U; WINDOWS NT 5.1; EN-US;

RV:1.8.1.17) GECKO/20080829 FIREFOX/2.0.0.17

FF3: MOZILLA/5.0 (WINDOWS; U; WINDOWS NT 5.2; EN-US;

RV:1.9.0.3) GECKO/2008092417 FIREFOX/3.0.3

Pattern in browsCap.ini for FF2

[*(Win*) Gecko/???????? Firefox/2.*]

Pattern in browsCap.ini for FF3

[*(Win*) Gecko/???????? Firefox/3.*]

With length of build id change from 8 digits to 10 digits

the matching does not work for firefox 3 and runtime fail

to render the E1 form. The solution is to change the match

patter to more generic format without length limitation of

build id by using single wildcard.

[*(Win*) Gecko/* Firefox/3.*]

The change shall be applied to all version of firefox start

from 3. And we may need to check the fix into 897, since

the customer may alread begin to use FF3 instead of FF2.

The LINKBSFN Command Confusion

I don’t know about you, but I can never remember what the correct parameters are for the LINKBSFN command that is required when doing Tools Release updates on an IBM iSeries (i, System i, AS400).

So, just to make it easier on myself, here they are:

LINKBSFN PARENT(PACKAGELIB) PATHCODE(PATHCODE)

Next Page »