Journaling a Physical File on IBM iSeries Using STRJRNPF

We have a system that needs to interface directly with some EnterpriseOne Files.  This system is written in Java and seems to be very difficult to change any JDBC settings to not use commitment control.

Anyway, to get around this issue, we started journaling the physical file that the JDBC command was trying to update using the following command:

STRJRNPF FILE(PRODDTA/F0911) JRN(OWJRNL/OW_JRNL)

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!

Web Only Version Pain

We seem to be having an issue with old “web only” versions.  There are times when the “web only” version causes the other version to not egen correctly.  So, below is the SQL that can be used to select the “web only” versions.

SELECT count(*) FROM COPD811/F983051
WHERE VRVCC2='1'             

If you want to be more precise, you can grab the “web only” versions that have been executed prior to a certain date by using the VRVED field and the six digit date which can be found on the e1 dates page.

How To Start/Stop The Managed Agent On AS400

You can start/stop the managed agent from the command line (green screen) by following the steps below:

1. Start the QSHELL by typing STRQSH at the command prompt.
2. Change to the JDE_HOME/bin directory by typing <install_dir>/JDE_HOME/bin.
   *** The <install_dir> refers to the installation directory in the IFS
3. To start the agent enter: startAgent &
   *** The & allows the agent to start as a background job so that it will not stop when you leave the QSHELL
4. To stop the agent enter: stopAgent
5. To restart or bounce the agent enter: restartAgent

You will want to run this in your startup script with a user that has a job queue that is not able to be interrupted.  Because of this, QINTER is not a very good choice.  The user will also need the following permissions: *ALLOBJ, *SAVSYS, *JOBCTL & *SECADM.

Also covered on Oracle’s My Support page ID 659949.1

Presentations from Oracle OpenWorld 2009

JD Edwards and Oracle Application Integration Architecture: One Powerful Combination

Red Stack Technology and JD Edwards EnterpriseOne 8.12: Future Is Bright for Orlando Utilities Commission

Maximize your JD Edwards EnterpriseOne investment with Tools and Technologies

The Benefits of Running JD Edwards EnterpriseOne on the Oracle Technology Stack

Choosing the Right Technology Stack for JD Edwards EnterpriseOne

Backup All SQL Server Databases

I came across this script to backup all SQL Server databases:

DECLARE @name VARCHAR(50) -- database name
DECLARE @path VARCHAR(256) -- path for backup files
DECLARE @fileName VARCHAR(256) -- filename for backup
DECLARE @fileDate VARCHAR(20) -- used for file name

SET @path = 'E:\Backups\Dynamics' 

SELECT @fileDate = CONVERT(VARCHAR(20),GETDATE(),112)

DECLARE db_cursor CURSOR FOR
SELECT name
FROM master.dbo.sysdatabases
WHERE name NOT IN ('master','model','msdb','tempdb') 

OPEN db_cursor
FETCH NEXT FROM db_cursor INTO @name  

WHILE @@FETCH_STATUS = 0
BEGIN
       SET @fileName = @path + @name + '_' + @fileDate + '.BAK'
       BACKUP DATABASE @name TO DISK = @fileName 

       FETCH NEXT FROM db_cursor INTO @name
END  

CLOSE db_cursor
DEALLOCATE db_cursor

SMTP Test

I ran across this while working on a different project but thought that it might be handy.

SMTP relay behavior in Windows 2000, Windows XP, and Exchange Server

The basic test:

Start a command prompt.

1. Type telnet ServerName 25, where ServerName is the SMTP server name or IP address and 25 is the port number, and then press ENTER.
2. Type EHLO, and then press [ENTER].
3. At the Telnet session prompt, type RSET. The telnet session responds with text that is similar to the following:
   250 2.0.0 Resetting

4. Type MAIL FROM:UserName@DomainName.tld, where UserName is the name of the user, DomainName is the name of the domain, and tld is the top level domain such as .com or .net.
   The telnet session responds with text that is similar to the following:

   250 2.1.0 UserName@DomainName.tld….Sender OK

5. Type RCPT TO:RecipientName@DomainName.tld, where RecipientName is the e-mail address of the recipient.
   The telnet session responds with text that is similar to the following:

   550 5.7.1 Unable to relay for RecipientName@ DomainName.tld

How To Find EnterpriseOne Web Only Versions

Dealing with EnterpriseOne “Web Only” versions can be a real pain.

They are deleted with each full package deployment and can cause a lot of confusion for the users.

In order to find these troublesome quasi-objects you can run the sql below:

select * from copy811/f983051
where VRVCC2 ='1'

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.

Next Page »