Thursday, 17 December 2015

Cantara 4.1 is now available

The next major release of the Rinami Cantara Integration Platform is now available. Version 4.1.0 is a maintenance release with a number of performance improvements regarding cache management and memory utilisation. It also improves the error handling required when dealing with the Oracle JD Edwards EnterpriseOne XML dispatch kernels.

We have add the following functional features in version 4.1:

  • Ability to define Push Notifications that support both Apple and Android devices
  • Support for both FTP and SMB media object shares
  • The ability to add filter options to existing reports without changing the JD Edwards version
  • Support for multiple time zones within a single schedule
  • The ability to define the JD Edwards user at a scheduler group level, not just environment level
For more information or to request a demonstration please contact us today.

Thursday, 14 May 2015

JDE EnterpriseOne Browser Experience Improvements

This is just a quick summary of a few of the settings you can change on your JAS instance to give the best user experience in browsers like Google Chrome or Mozilla Firefox as well as Internet Explorer. All of these settings can be found in the Web Runtime section of the jas.ini but changes should always be made using Server Manager.

Grid Global Page Size = 50

Back in the early 8.10 and 8.11 days this setting could have a major impact on web performance just due the amount of javascript that used to come down with the grid and the fact that PC's and terminal servers back then would struggle to process it all. These days those issues have long since disappeared so for the convenience of your users we recommend setting this to at least 50. If you leave it at the default you'll find that a lot grids will still only provide the user with the first 10 records on a find.

Use ActiveX Controls = False

ActiveX controls are going the way of the dinosaur with Microsoft announcing that Internet Explorer has reached the end of it's life. To enable a consistent experience across multiple browsers this should be set to false. Before doing this though you should be aware of the impacts.  Firstly your users won't be able to view Microsoft Office documents directly inside the browser window and also they will not be able to import directly from an Excel file (CSV and copy and paste will still work fine). The other major impact is that all of the text attachments currently in your JDE system will need to be converted to HTML format from RTF. You have two options on how to deal with this. You can let your users convert the text to HTML when they first view it after this setting has been changed or alternatively you can run the batch conversion to do it for them. Our recommendation is that it depends on how many F00165 records you have. If you have been on JDE for a significant amount of time then it is likely you have a large number of text attachments and in all likelihood most of those attachments will never be viewed again. In that case you may choose to just leave them and if users need to view existing attachments they can do the conversion on demand. Details on running the batch conversion can be found in the Oracle documentation.

UBE Content Disposition = False

This basically ensures that if the browser can handle the file type, ie the PDF file, then it will be opened and displayed automatically within the browser rather than having the browser prompt the user to save the file.

That's it, just a couple of simple changes can make the life of the user that little bit better. In our experience, due to the speed that it processes and handles JavaScript and Ajax, we strongly recommend using the Google Chrome browser for JDE as responsiveness is noticeably better than other browsers, especially Internet Explorer.

If you have any other settings that believe improve the user experience then please leave a comment below and I'll look to add them to this post.

Tuesday, 12 May 2015

Displaying a Google Map in JD Edwards CafeOne

You've seen plenty of demos of all of the cool things that can be done with CafeOne but where to start. Here's a very simple walk through of enabling CafeOne by putting a Google Map in the Address Book app (P01012) and publishing it to all users.

The first step is to create a publishing entry to enable all of your users to see your published CafeOne element. To do this open P952336, click on add and give the list a name and description. You can then list out the roles or users that can see this content published to this list. In this example I'm allow all users to see CafeOne content so I've set the role to *PUBLIC.

You then need to enable the application for CafeOne. Open P952332 and create two entries to enable the Address Book form W01012A for CafeOne. One for *PUBLIC so that all users can view the content and a second for the role that will be defining the CafeOne page.

You'll note for the role that can publish I've chosen "Allow user to publish to pre-defined Publication List". This is the simplest approach so that you don't have to change the status of layouts once they're saved.

You can now go ahead and define the CafeOne page in the Address Book app. Open P01012 and select a record that has a mailing address specified to open the Address Book Revision form. If everything has been done correctly then you should see the Layout dropdown list on the top right of the form.

Now go to your user menu and you should see the Edit Current Page option at the bottom of the list. Click that to enable you to create a new layout. You should now see two options in the top left of your screen. As we haven't set up any template URL's you'll need to select the Create New Content option.

This will give you a popup with different options depending on your tools release but for 9.1.5 you should see either URL or EnterpriseOne Form. You need to drag the option you want onto the right hand side of the form and then drop it when you have set the appropriate size.  Once you've set the CafeOne frame size you can now enter the details of the URL you wish to show. In this case we'll be using the Google Maps embedded url which is

You can then give the URL and name and optionally a description. Now select the Dynamic Link URL radio button so that you can specify the URL query parameters based on the content in the form.

The good thing about Google Maps is it is very forgiving in terms of the content you put in the query string. To add values you should select the "q" parameter and change the operation from "remain as" to "is mapped to". At this point you can now add one or more elements from the form to create the query string. In this case I've chosen to add Mailing Name, Address Line 1, Address Line 2, City, State and Country.

Once you've included all of the values you require you can click the Save icon in the top left of the content editor and you should see the map appear with the address marked with a pin.

The next step is to save the layout by clicking on the Save Layout button in the top right of the screen. In this example we named the layout Address Book Map.

Now it is time to publish the layout to all of the other users. To do this go into the user overrides program P98950 and filter on your user profile and a UO Type of RI. Assuming you haven't created any other layouts you should only see one option.

Select the row and click on the Copy icon in the form toolbar. Enter in the *PUBLIC role on the copy form and click OK. This will effectively publish the layout to all users.

For a user to see the layout they will need to open the Address Book Revisions form and then select the layout from from the drop down list in the top right of the form.

And that's it, you've successfully published Google Maps in your Address Book Revisions form to all JDE users.

Monday, 11 May 2015

Enabling Basic Google Analytics for JD Edwards EnterpriseOne 9.1.5

If you're comfortable with Google knowing how you use your ERP then here is a simple way to enable the Google Analytics engine for your JDE EnterpriseOne instance. These instructions are for the 9.1.5 tools but could just as easily be adapted to the older tools releases.

So the first thing you need is a Google Analytics account. There's plenty of information available on how to go about it so I'm not going to clutter the internet with yet another tutorial. If you need a starting point, here's Google's documentation.

To activate the data capture for Google Analytics you need to include some javascript. The best place I have found to inject this code at the moment is in the webgui.js file. Simply append the following code to the very end of the file:

    (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
    ga('create', 'UA-XXXXXXXX-X', {"siteSpeedSampleRate": 100});
    ga('send', 'pageview');

You'll need to replace UA-XXXXXXXX-X with your own Google Analytics identifier.

Where is the webgui.js file you might ask... Assuming you're using Server Manager (I don't who isn't) then you'll want to update the deployment package found in the SCFHA folder on your JDE web server. Here's an example linux path you might use for you PY deployment:

That's it. If you restart your web instance the solution will redeploy with the new updated js file and you'll be away. Depending on your browser cache you may need to hit refresh to ensure the latest webgui.js is pulled down onto your client machine. You should then be able to log in to Google Analytics and watch the hits flow through as you navigate through the JDE applications.

Please be aware that this has not been heavily tested and is not supported by Oracle so if you do implement this change you do so at your own risk.

Thursday, 12 February 2015

Cantara Version 4 is nearly here...

Rinami is pleased to announce that we have reached the final round of beta testing with our early adoption customers on version 4 of the Cantara Integration Platform and we expect the new release to be generally available in the first quarter of 2015. With version 4 of the Cantara Integration Platform we're introducing a number of significant enhancements both in terms functionality and underlying technology.

Cantara Scheduler

The biggest functional enhancement to the Cantara Integration Platform to the incorporation of a dedicated JD Edwards batch scheduler. The scheduler delivers a number of significant improvements of the standard job scheduler available within the Oracle JD Edwards product.  These benefits include:

  • Sophisticated scheduling capabilities to enable complicated recurring execution triggers
  • Scheduling based on JDE Company date patterns
  • The ability to schedule groups of reports rather than having to specify schedules for each report individually
  • Dependency management to ensure that prerequisite reports or report groups have executed successfully before any report or group executes
  • Highly available architecture to enable multiple scheduler servers to manage a single schedule
  • Scheduling across multiple batch servers with automatic fail over if any batch server fails
  • Ability to to have schedules defined by different JD Edwards environments
  • The ability to override report processing options, report interconnects and data selection within the scheduler without impacting the version definition in JD Edwards
  • The ability to utilise variables for processing options, data selection etc. This enables changes, such a current financial period, to be done once and apply to all applicable reports.
  • Exclusion calendars can be defined that prevent scheduled reports from executing during the exclusion periods. For example you can exclude particular reports and groups from executing during month end processing.
  • Notifications to multiple parties in response to failures of reports. Failure can include execution run times be below or above user defined tolerances as well as failure to submit or failure during execution.
  • A Gantt Chart view is provided to analyse the defined schedule including complex dependencies and overall expected run times.
  • Full history logging to show which reports have been run, against which environment and what their execution time was.

Enhanced Administration Console

The Cantara Integration Platform Administration Console has been redesigned to provide a cleaner and more intuitive interface for user. The administration console now incorporates role based security so that you can distinguish between administrators, configurators or just viewers. We have also enabled the ability to tag all of the different components within the Cantara Integration Platform which enables far simpler management and consolidation of your overall configuration.

Choice of Local File or Database Configuration Storage

To facilitate true high availability environments we have enabled the option of either local file or database storage for all Cantara component definitions. In addition to this change we also provide a full import/export feature to enable users to migrate definitions between servers and to migrate from one storage method to another.

Token Based Security Enhancement

As a convenience to end users, especially those utilising mobile apps, we now provide token based authentication for clients. This enables applications to implement "Remember Me" functionality securely without exposing user credentials within the client. The Cantara Integration Server handles all of the authentication requirements with the JD Edwards security server giving a seamless experience for users of client applications.

Updated iOS Client Libraries

The Cantara iOS client libraries have been updated to the new Swift programming language and offer full compliance with the current iOS operating system. This enables customers to take advantage of the latest developments within the iOS ecosystem. Rinami will continue to provide updates and enhancements for iOS, Android, Java and .NET to cover all possible development scenarios and technologies.

Subscription Based Licensing

In combination with the release of version 4 of the Cantara Integration Platform we will be launching our new subscription based licensing model. This will make the Cantara Intregration Platform even more affordable to businesses looking to integrate with their Oracle JD Edwards system. One of the guiding principals at Rinami is that we want to be the alternative to "Do Nothing" and to do so we aim to provide the most cost effective solutions available. Please contact us for more information on just how affordable our solutions are.