Web Only Version Pain
Filed under: EnterpriseOne - General, EnterpriseOne - SQLs, eGen, sql
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, xeHow To Find EnterpriseOne Web Only Versions
Filed under: Batch Versions, EnterpriseOne - General, EnterpriseOne - SQLs, eGen, enterpriseone
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:
where VRVCC2 =’1′
Batch Version (P98305W) Version Error
Filed under: EnterpriseOne - General, EnterpriseOne - Install/Upgrade, Tools Release, enterpriseone
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 dont do it. The second image is the Interactive Versions screen that you will need to use to delete the version.
Tags: batch version, e1, enterpriseone, EnterpriseOne - General, EnterpriseOne - Install/Upgrade, jde, Tools Release, Tools Release, version, versionsEnterpriseOne & Sharepoint
A few weeks ago I attended a webinar sponsored by JDETips and presented by K-Rise Systems.
K-Rise has a very interesting set of EASYProcess web parts that integrate with EnterpirseOne.
Below is a list of selling points:
- With EASYProcess you get the power of Web portal interfaces, workflows, a business process automation engine, data integration, reporting, web services and handheld development, all in one place, integrated seamlessly to work with JDE and any database.
- Absolutely NO CODING in using EASYProcess.Your staff will be developing with EASYProcess very quickly. The learning curve is a couple of days. On-Site and On-Line training available. See possible projects below.
- Are you paying your developers to accurately place semi-colons? Let EASYProcess do that. Now your staff can do what they do best: build useful applications for your customers and users.
- Creates SharePoint compatible webparts with complex workflow.
- Team Development Friendly. All versions of World & E1 compatible
It looks like this product could really help in making EnterpriseOne data available through SharePoint a trivial task.
Tags: e1, EASYProcess, enterpriseone, enterpriseone, jde, JDETips, version, versions, worldClean Up Your Web-Only Versions
Filed under: EnterpriseOne - SQLs, IBM i/System i/iSeries/AS400, enterpriseone
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 dont 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)
Egen Process JDBJ Gotcha
Filed under: EnterpriseOne - JAS (Java Application Server), IBM i/System i/iSeries/AS400, JDBJ, eGen, enterpriseone
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 dont, 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, versionsEnterpriseOne 8.12 Functionality with Version 8.11 SP1
Filed under: EnterpriseOne - JAS (Java Application Server), EnterpriseOne - SQLs, IBM i/System i/iSeries/AS400
Background:
In developing the Employee Self-Service user interface without using the portal, the development team had a need to be able to print out an employee’s paystub and have it emailed to them. The email portion of the process is handled by Optio but before it gets to the Optio server, it needs to be sent to an outqueue on the Enterprise Server. Because of the flow of the UBE submission application, upon requesting the paystub (UBE) the user is presented with a printer selection verification screen. It was decided that this screen would be pretty confusing to those employees that do not use EnterpriseOne regularly. So, the developer found a way around that. She submitted the UBE using a Named Event Rule (NER).
Issue:
Because of using the NER to submit the UBE, the Print Immediate parameter in the JAS.INI file doesn’t get read. This is because it is being submitted by the Enterprise Server instead of the JAS server. If the job isn’t printed, or sent to an outqueue, then the PDF never gets to the Optio server to be processed and emailed to the user.
Resolution:
After consulting with Oracle Support, we changed the VRVCC3 field of the F983051 to contain a ’1′ in the record of the UBE Version that we wanted to Print Immediate. Apparently, this version Print Immediate parameter is used in the 8.12 applications but is also read in the 8.11 SP1 version.
Note: We are using 8.11 SP1 and this solution may or may not work with earlier versions.
Tags: enterpriseone, EnterpriseOne - JAS (Java Application Server), EnterpriseOne - SQLs, IBM i/System i/iSeries/AS400, jas, oracle, ube, version, versionsMore E1 Software From Down-Under!
I’ve talked about Everest Software International’s EnterpriseOne utilities software before…particularly, Boomerang and Update Queue Names In Versions.
In their latest newsletter (yes, it is worth subscribing to), Alex highlights 3 software offerings:
- ESI Benchmark 2008: “It allows easy comparison of the performance of different servers in real, JDE-like terms.” This may prove to be very beneficial when looking to purchase upgrades.
- Boomerang: “…it now supports the new Tools Release 8.97 and the latest version is even more stable and reliable than ever before.” This product is invaluable, if you deal with multiple EnterpriseOne installations in any way.
- XML InSPECtor: A new offering that can be used to work with 8.12′s new XML specs. “…it can be used for, it would allow simple changing of the underlying BSVW’s in UBE’s and APPL’s, by simply replacing all references to the old BSVW with a new one, the list of possible applications is endless.” “Endless” is right. I am very excited to see this tool in action!
I haven’t had experience with all of what Everest Software International has to offer but, the site definitely warrants a look. They have a tool for doing almost everything that you wish E1 could do on it’s own.
Thanks, Alex!
Tags: e1, enterpriseone, EnterpriseOne - General, jde, Tools Release, ube, version, versionsEnterpriseOne (E1) Version Promotion With Security
Filed under: EnterpriseOne - General, EnterpriseOne - SQLs
The other day our development manager came to me and stated that she could not promote a version to production.
In order to take any security out of the picture, I tried to promote it with my admin id. I received the same error: "General error promoting object". As with most E1 error messages, this was not real helpful.
I then looked at the object in the Batch Versions application and happened to notice that the version that was causing the issue had version security set to 2. According to the the documentation a "2" in the version security options:
2 (medium to full security) This level allows all users to install or copy the version, but lets only the "Last Modified By" user complete all the tasks.
NOTE: The broken-English is the documentation’s not mine.
Because of this setting I was unable to make any changes to this security through the application. Instead, I used SQL:
update codv811/f983051 set vrexcl='1' where vrpid = 'xxxxxx' and vrvers = 'xxxxxx'
Hope this helps!
Hey, have you ever had trouble with this or something similar? If so, how did you get things to work again?
Tags: batch version, e1, enterpriseone, EnterpriseOne - General, EnterpriseOne - SQLs, jd edwards, jde, oracle, peoplesoft, security, sql, version, versions
iSeries JDBC jt400.jar – {note to self}
Filed under: EnterpriseOne - Install/Upgrade, EnterpriseOne - JAS (Java Application Server), IBM i/System i/iSeries/AS400
Excerpt from a post on JDEList.com by Colin Dawes:
You CAN NOT use the jt400 from the client access folder.
You need to use the jt400 that is on your iSeries. The 2 versions are not the same and you’ll get some hanging if you use the iSeries Access version.
The jt400 on the iSeries is located at:
/QIBM/PRODDTA/HTTP/PUBLIC/JT400/LIB/JT400.JARUsually you need to copy this to the following location on Windows:
\WebSphere\AppServer\libI say usually because sometimes during the installation prople point the installed to the iSeries Access Path. In this case the WAS variable will be incorrect and you either need to (1) Change the variable in WAS or copy the jt400.jar from the iSeries on top of the jt400.jar that came with iSeries Access.


