E1 Tips & Tricks

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?

Tags: eGen, enterpriseone, EnterpriseOne - JAS (Java Application Server), Java, jde, JVM, oracle

December 31, 2008 | EnterpriseOne - JAS (Java Application Server), JVM, Java, eGen, enterpriseone | No Comments »

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, enterpriseone, EnterpriseOne - JAS (Java Application Server), ibm, IBM i/System i/iSeries/AS400, JDBJ, sql

December 30, 2008 | EnterpriseOne - JAS (Java Application Server), IBM i/System i/iSeries/AS400, JDBJ, eGen, enterpriseone | No Comments »

Hitler and the CNC Guys – Jeff Stevenson

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, ube

December 17, 2008 | IBM i/System i/iSeries/AS400, Oracle Server Manager, SAP, enterpriseone, oracle | No Comments »

Simple Server Manger Improvement Suggestion

Have you used Oracle’s Server Manager for EnterpriseOne?

If so, you may have noticed a little “feature” that is really quite annoying:

• when items are listed on a page they are not consistently sorted.

In other words, when you display the page one time the items are in one order.  Then, when you display the same page for a different server the items are in a different order.  For example, below are 2 screen shots of the JDBj Service Caches for 2 separate EnterpriseOne HTML server instances.  You will notice that the items in figure 1 are in a different order than figure 2.

Figure 1:

Figure 2:

This annoyance happens in most of the other screens that are available in Server Manager.

In my opinion, it would be really nice to have a consistent order to the items in the list.

 

Have you found anything in Server Manager that was annoying?

Tags: e1, enterpriseone, enterpriseone, EnterpriseOne - General, EnterpriseOne - Install/Upgrade, oracle, Oracle Server Manager

December 3, 2008 | EnterpriseOne - General, EnterpriseOne - Install/Upgrade, Oracle Server Manager, enterpriseone | 2 Comments »

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, websphere

November 26, 2008 | EnterpriseOne - Install/Upgrade, EnterpriseOne - JAS (Java Application Server), Microsoft, Oracle Server Manager, enterpriseone, oracle | No Comments »