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)

Tags: enterpriseone, enterpriseone, EnterpriseOne - General, ibm, IBM i/System i/iSeries/AS400, iseries, Java, JDBC, JDBC, JDBJ, system i

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

Tags: as/400, enterpriseone, enterpriseone, EnterpriseOne - General, EnterpriseOne - Install/Upgrade, EnterpriseOne - JAS (Java Application Server), ibm, IBM i/System i/iSeries/AS400, iseries, jas, oracle, Oracle Server Manager, Server Manager, system i, Tools Release, websphere, websphere

Clean Up Your Web-Only Versions

We have been having some issues lately where users create web-only versions and expect to use them after a full package has been built and deployed.

We have processes in place for them to submit new versions to our development teams, but sometimes things don’t happen the way they are designed.

Anyway, I was doing some checking and noticed that there were quite a few versions in the F983051 that were web-only versions and were older than the last full build.

So, I created an SQL that we are going to run immediately after the deployment of a new full package.

 

DELETE FROM <central objects>/F983051
WHERE VRVCC2='1'  

***NOTE: the syntax used in the SQL statement is for the IBM System i (as400, iSeries)

Tags: as/400, central objects, e1, enterpriseone, EnterpriseOne - SQLs, ibm, IBM i/System i/iSeries/AS400, iseries, sql, system i, version, versions

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.

Tags: as/400, eGen, eGen, enterpriseone, EnterpriseOne - JAS (Java Application Server), ibm, IBM i/System i/iSeries/AS400, JDBC, JDBJ, sql, Tools Release, version, versions

The EnterpriseOne Session Timeout Two-Step…Ok, Three Step

We have several work areas that require a longer inactive timeout setting than the default 20 minutes (Payroll Time-entry, Fixed Asset Accounting, etc.).

Unfortunately, EnterpriseOne’s architecture does not make the process of configuring a session timeout very easy.  There are three separate separate settings that need to configured correctly.  Depending on your architecture that could mean three separate machines using three separate platforms.  Whatever your architecture looks like there are at least three.

1. The Java Application Server (JAS).  No matter what flavor of JAS you are running (IBM Websphere, Oracle Application Server, BEA, etc.) you will need to configure the application’s user session timeout setting.  The screenshots for IBM Websphere 6.0.2.13 are below:

    
   

2. The EnterpriseOne HTML Server.  This setting is in the JAS.INI under the [CACHE] stanza.  The setting is in milliseconds (3600000 = 1 hour).  If you are running the Oracle Server Manager for EnterpriseOne, you can find it in the “Cache Configuration section under the “Web Runtime” configuration.
    
   
3. The HTTP server.  The instructions for both Microsoft IIS and IBM HTTP Server follows:
   • Microsoft IIS:
     • Display the properties of the website that is configured to host EnterpriseOne
     • On the “Website” tab, modify the “Connection Timeout” setting.  Please note that this value is in seconds, not milliseconds.
   • IBM HTTP Server:
     • Edit the “Timeout” setting in the HTTPD.CONF file.  Please note that this value is in seconds, not milliseconds.

NOTE:  To avoid record locking Oracle specifies to configure the system so that the JAS server will “timeout” the user’s session.  To do that both the EnterpriseOne HTML Server and the HTTP server need to be set to great times than the JAS server.  For example:

• To configure a timeout value of 30 minutes:
  • JAS Server: 30
  • EnterpriseOne HTML Server: 3600000
  • HTTP Server: 3600

Tags: e1, enterpriseone, enterpriseone, EnterpriseOne - Install/Upgrade, EnterpriseOne - JAS (Java Application Server), ibm, jas, java application server, Microsoft, oracle, oracle, oracle application server, Oracle Server Manager, Server Manager, websphere, xe

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)

Tags: as/400, e1, EnterpriseOne - Install/Upgrade, fusion, ibm, iseries, system i, Tools Release

How To Throttle The Job Queue

NOTE: The following is intended for use on the IBM System i (iSeries,AS400, etc.)

CHGJOBQE SBSD(QBATCH) JOBQ(JDEOWPACK) MAXACT(2)

Explanation:

CHGJOBQE- Change Job Queue Entry

SBSD- Subsystem Description

JOBQ- Job Queue

MAXACT- Maximum Active Jobs

Tags: as/400, ibm, IBM i/System i/iSeries/AS400, iseries, jde, system i

IBM Docs Of Interest

I received an email today from JDETips.  It provided links to a list of EnterpriseOne data archiving documents on the IBM Optim web site.

They are as follows:

Upgrade and Archive Strategies for JD Edwards EnterpriseOne

Anatomy of a JD Edwards EnterpriseOne Archiving Project

IBM Optim Test Data Management for JD Edwards EnterpriseOne

Closing the Data Privacy Gap for JD Edwards EnterpriseOne

Thanks JDETips!

Tags: enterpriseone, EnterpriseOne - General, ibm, jd edwards, jde

EnterpriseOne Package Build Times

After installing the new IBM hardware, I decided to run a full package build just to get an idea of what the performance improvement was.

So, here are the results:

	Existing Hardware	New Hardware
Client	~4 hours	~5.75 hours
Enterprise Server	~4 hours	~2 hours

Ok, I’m a little confused on the client portion of the build process.  I’m not sure if there was some other process running that slowed some things down or what.

However, I am really liking the Enterprise Server portion of the build.  The new hardware essentially chopped the build time in half.

So, although I need to do some checking on the client part I am really satisfied with the new hardware.

Tags: e1, enterpriseone, esu, ibm, IBM i/System i/iSeries/AS400

EnterpriseOne IBM i Hardware Upgrade

Hooray! The New Hardware Is In! The New Hardware Is In!

Sorry to mutilate a classic line, but…  Hey, this is exciting news.

Our IBM hardware guys put in a lot of hours last weekend and upgraded our Enterprise Server hardware.  Essentially, we doubled processor CPW, tripled RAM & added 1TB of disk.  See the breakdown below:

	Existing Hardware			New Hardware
	System	LPAR 1	LPAR 2	System	LPAR 1	LPAR 2
Chip Set	Power5			Power6
Chip Speed	1.65 GHz			4.7 GHz
CPUs (Active)	2	1.4	.6	3	2	1
CPW System (Active)	6000	4200	1800	13500	9000	4500
CPW Interactive (5250)	3000	2100	900	4500	3000	1500
Memory	20 GB	12 GB	8 GB	64 GB	40 GB	24 GB
DASD – Capacity RAID-5		1848 GB	775 GB		2537 GB	1057 GB

Tags: enterpriseone, ibm, IBM i/System i/iSeries/AS400

Next Page »