tag:blogger.com,1999:blog-79585693459347147892024-10-24T02:05:45.848-04:00JD Edwards EnterpriseOne, SQL Server, WebSphere and other technologiesjxs2151http://www.blogger.com/profile/13599578258965424531noreply@blogger.comBlogger51125tag:blogger.com,1999:blog-7958569345934714789.post-29466182959957117092011-10-13T22:54:00.000-04:002016-11-23T13:14:07.510-05:00

Ever wondered which tables in your databases are being used most heavily?  Below is a script for SQL Server 2005/2008 that will tell you exactly that - which tables are utilized most and what percentage of that use is reads and what percentage is writes.  Heavily utilized tables are prime candidates for SQL Server's Table Partitioning or moving to another filegroup (not necessarily

Unknownnoreply@blogger.com13tag:blogger.com,1999:blog-7958569345934714789.post-56820807470986169162011-09-21T17:38:00.000-04:002011-09-29T17:17:09.518-04:00

There has always been an issue opening PDF files from the Work with Submitted Jobs list in the EnterpriseOne web client - the end user is prompted to determine what they wish to do with the file when, chance are very good that they want to open it.  The problem is related to how the PDF content is delivered to the browser by the E1 code and how the browser handles that content. Full

Unknownnoreply@blogger.com5tag:blogger.com,1999:blog-7958569345934714789.post-25610245651158986892011-09-07T14:33:00.001-04:002012-09-26T10:04:45.286-04:00

Your EnterpriseOne system may be creating hundreds of thousands of files on your JD Edwards Enterprise Server in a location that is not readily apparent and not cleaning them up...ever. During a UBE run that involves a version that has Print Immediate turned on at the version level (introduced in TR 8.96) a 'temporary' print definition file (either PostScript or PCL depending on how you defined

Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-7958569345934714789.post-21395731552525408922011-09-02T15:10:00.001-04:002011-09-02T15:11:21.585-04:00

It is well known that JD Edwards EnterpriseOne splatters logs and temporary files all over the place.  As the application has gotten more complex with added components such as Web servers, Java Application servers, Server Manager, etc. the sheer number of log files generated in wildly varying locations has notably increased and keeping track of and managing all these logs files is a chore.

Unknownnoreply@blogger.com2tag:blogger.com,1999:blog-7958569345934714789.post-4574888887641333142011-08-29T22:41:00.000-04:002012-12-16T17:13:06.229-05:00

Starting in EnterpriseOne 9.0 the platform pack delivers pre-built databases that are simply attached and are set to a collation of Latin1_General_CI_AS_WS when created at Oracle.  This collation is different than the default SQL Server collation and different than the old (pre-9.0) collations.  Because of this, you will usually find a mix of collations on an E1 install, particularly

Unknownnoreply@blogger.com3tag:blogger.com,1999:blog-7958569345934714789.post-20959632367944053542011-07-28T19:14:00.004-04:002011-08-18T21:05:11.904-04:00

I recently had the opportunity (if you'd call it that) to utilize LiteSpeed's Object Level Recovery functionality on a large (~500GB) database and was somewhat surprised at the poor performance. An end user had run a report in the JD Edwards EnterpriseOne application with incorrect settings, corrupting a table to the point where we needed the data from prior to the report run. Object Level

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7958569345934714789.post-234351683997022011-06-16T11:53:00.034-04:002016-12-07T16:01:06.215-05:00

Who knew changing a single setting away from the default in Windows 2008 and later (as of Windows 2016) would result in an increase of 70% in performance? That's exactly what happened recently at a client experiencing JD Edwards EnterpriseOne UBE performance issues during upgrade testing. We were able to make UBE's that previously ran in 10 minutes run in less than 3 minutes simply by changing

Unknownnoreply@blogger.com6tag:blogger.com,1999:blog-7958569345934714789.post-58749766035591185472011-03-31T22:08:00.003-04:002011-04-10T11:07:46.362-04:00

I recently saw a request for a complete list of EnterpriseOne tables with column specifications and other information. Getting these details using a SQL script is not simple since JD Edwards seems to violate several standards in SQL-92 and database normalization best practices. Since the required information is not kept in one table it is necessary to use SQL joins and foreign key

Unknownnoreply@blogger.com5tag:blogger.com,1999:blog-7958569345934714789.post-68356322723112888222010-12-24T21:17:00.006-05:002011-05-23T16:23:49.367-04:00

I recently setup my iPad to use bluetooth to connect  to my Verizon Blackberry Tour 9630 so I could access the Internet (and my customer's VPN's) from anywhere I can get cell reception. Doing this requires you to "Jailbreak" your iPad, a process that opens up the device for non-Apple approved software.  This is not an action that everyone will want to do, but then again not everyone

Unknownnoreply@blogger.com2tag:blogger.com,1999:blog-7958569345934714789.post-76296172448016995262010-11-02T13:53:00.005-04:002010-11-02T13:56:20.646-04:00

In an earlier series of articles on EnterpriseOne SQL Server default security we discussed the issue of Oracle granting permissions to PUBLIC that created a security exposure when placing users in the SQL Server db_datareader database role.  I advised you to place any user of an E1 database that is in the db_datareader role in the db_denydatawriter role also.  However, I didn't leave

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7958569345934714789.post-37129493431123997502010-10-10T22:29:00.014-04:002010-10-28T15:11:40.873-04:00

As mentioned in parts 1 and 2 of Default SQL Permissions in EnterpriseOne the permissions granted in EnterpriseOne databases during the install leave quite a security exposure.  Those articles covered in depth the reasons for this and ways to address the problem.  This article will detail two more items of concern: database level permissions set by the install and Guest user access from

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7958569345934714789.post-67530482567076535392010-10-07T10:22:00.003-04:002012-03-01T21:37:20.967-05:00

In Default SQL Permissions in EnterpriseOne Part 1 we discussed the problem with granting ad-hoc SQL logins access to EnterpriseOne databases and how doing so gave them rights to modify data. In part 2 we are going to demonstrate this effect in hopes of creating a better understanding of exactly what is going on. Afterward I will offer some suggestions to work around and/or remedy the

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7958569345934714789.post-28229552936227299642010-10-03T22:08:00.010-04:002010-10-19T14:56:56.452-04:00

So you've gotten EnterpriseOne installed or have had it installed for a long time and you've finally changed the default E1 SQL user (CRPDTA, DD812, PRODCTL, etc.) passwords in SQL Server.  If you haven't at least done that you should stop right here and go change those passwords using the article E1: DB: How to Change the Database Object Owner Passwords for EnterpriseOne Databases [ID

Unknownnoreply@blogger.com2tag:blogger.com,1999:blog-7958569345934714789.post-76100088492469339272010-08-22T16:12:00.004-04:002010-08-24T17:50:12.276-04:00

Completely rebuilding the tables used by the Cross Reference Facility application in EnterpriseOne is a large, complex process that can take a long time to run.  There is a way to shorten the run time of the rebuild but selecting only those objects changed since the last run. The Cross Reference Facility application (P980011) in EnterpriseOne gives developers and administrators information

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7958569345934714789.post-55804089392840446972010-08-17T11:34:00.003-04:002010-08-19T13:32:06.268-04:00

There is a way to restart just the UBE queue in EnterpriseOne. If you are faced with a situation where submitted jobs are not processing and the jobs are sitting in a waiting status you can get the queue restarted without bringing down the entire E1 system, allowing interactive users to continue their work. In older (prior to 8.9) releases the queue was a separate Windows service called JDE

Unknownnoreply@blogger.com8tag:blogger.com,1999:blog-7958569345934714789.post-26848624097473981582010-07-07T23:55:00.018-04:002011-10-20T15:17:48.333-04:00

Sometimes I am beating around on a SQL script that I really want to share with others. A couple of scripts I wrote to show the largest tables in a database and the largest tables in all databases on a SQL server is a perfect example.The scripts make extensive use of the SQL 2005/2008 dynamic management view sys.dm_db_partition_stats. This view displays information about the space used to store

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7958569345934714789.post-65476610124826817452010-05-22T16:36:00.014-04:002013-10-20T22:37:35.315-04:00

SQL Server indexes are useful objects, greatly decreasing the time needed to find and return data in database tables.  Unfortunately, the opposite occurs during record inserts to tables with indexes.  When one is inserting a record or two, or even a hundred, the penalty generally isn't large enough to warrant spending time disabling the indexes to improve the insert operation

Unknownnoreply@blogger.com5tag:blogger.com,1999:blog-7958569345934714789.post-49506478829965155752010-05-20T16:30:00.001-04:002010-05-20T16:31:21.648-04:00

Jeff Stevenson's Technology Blog is now featured on Quest's Blog Roundup.  Quest International is the customer-driven group supporting Oracle applications users, including PeopleSoft, JD Edwards and Oracle Utilities and their Blog Roundup highlights relevant blogs in the community. Check out the Blog Roundup http://www.questdirect.org/questdirect/Connect/Blog+Roundup.htm and the main Quest

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7958569345934714789.post-58375135243012375692010-05-03T17:00:00.005-04:002010-05-13T11:03:10.046-04:00

I have posted the first in a series of articles on the soon-to-be released Update 3 for Tools Release 8.98 over on The Karamazov Group's blog, where strategy items are published. The first article in the series can here found here: http://blog.karamazovgroup.com/2010/05/enterpriseone-tools-release-8983-notes.html Second article: http://blog.karamazovgroup.com/2010/05/

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7958569345934714789.post-13630483542340096282010-03-22T17:16:00.014-04:002010-04-02T11:49:39.688-04:00

A certain philosophy exists within the JD Edwards ecosphere where some believe that instead of doing the hard work to properly secure an EnterpriseOne system they can instead configure the menu in such as way as to "hide" applications from users.  This is perhaps based on a couple of faulty premises - that menu configuration is easier than security configuration and that users will not be

Unknownnoreply@blogger.com3tag:blogger.com,1999:blog-7958569345934714789.post-83660509317755918502010-03-09T10:00:00.003-05:002010-03-09T10:16:37.213-05:00

Back in the day whole environment refreshes were commonplace, utilized both as a go-live step and as a way of ensuring that environments before PD in the SDLC were synchronized.  It worked and in the absence of a true object management tool, was pretty useful.  Whole methodologies developed around this practice.  With the introduction of OMW and subsequent understanding of how to

Unknownnoreply@blogger.com2tag:blogger.com,1999:blog-7958569345934714789.post-8438796421955726622010-01-03T17:17:00.009-05:002010-08-09T11:53:58.586-04:00

Earlier we discussed methods for executing quick SQL table backups and performing quick SQL table restores as a way to mitigate risk to data during certain operations.  In this article we are going to discuss some low-effort housekeeping methods to keep us from forgetting about the table backups we created. While it is not a huge deal that a few table backups are hanging out in your

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7958569345934714789.post-33714093743854469792009-12-07T20:09:00.015-05:002010-10-04T16:16:19.759-04:00

A while back I discussed a method to do quick SQL table backups.  I usually create backups of tables prior to taking an action that has the potential to create the need to restore that table's data.  It's just a good idea, is easier than taking a full backup and gives you a readily available source of the original data should something go wrong with the changes you make. Not that it

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7958569345934714789.post-73743384741971648542009-12-03T23:25:00.002-05:002014-03-24T21:56:49.411-04:00

One of newest types of security for JD Edwards EnterpriseOne is Data Selection security.  Using Data Selection security CNC administrators can secure users from modifying, adding, deleting, and viewing the data selection for batch applications or specific versions of batch applications. Data Selection security was made available with Tools Release 8.98 Update 1 (8.98.1.0) and has a minimum

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7958569345934714789.post-64214693794176510612009-11-13T09:39:00.034-05:002009-12-03T19:33:27.021-05:00

Occasionally it is necessary to place a large number of objects in an EnterpriseOne Object Management Workbench project.  The default method of selecting a single object in the right pane and clicking the left arrow to add an object to a project is cumbersome but not a huge issue for an object or two.  After about ten objects though and the interface gets tiresome. A typical use that

Unknownnoreply@blogger.com2