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.

Tags: e1, eGen, eGen, EnterpriseOne - General, EnterpriseOne - SQLs, sql, sql, version, versions, xe

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:

Tags: Batch Versions, eGen, enterpriseone, enterpriseone, EnterpriseOne - General, EnterpriseOne - SQLs, fusion, sql, version, versions

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, eGen, enterpriseone, EnterpriseOne - JAS (Java Application Server), Java, jde, JVM, oracle, Tools Release

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