AutoEdge|TheFactory: Getting Started - Wiki - OpenEdge Architecture - Progress Community

AutoEdge|TheFactory: Getting Started

AutoEdge|TheFactory: Getting Started

Prerequisites

The following products should be installed before attempting to install AutoEdge|TheFactory.

OpenEdge

The sample application requires at least OpenEdge Release 11.0.0. We recommend the latest version. Get it while it's hot from ESD or wherever fine software can be found at your office. You'll need these components:

  • Progress Developer Studio for OpenEdge (aka "PDSOE")
  • OpenEdge Database and AppServer. The DB must be Enterprise-class in order to support Savvion.

Savvion

The sample application requires at least release 8.0, and we'll need at least these components:

  • BPM Studio or Process Modeller
  • Business Manager

Setup

  • Firstly, run the installer. The latest version can be found below. There's also a recorded guide to installation, which provides a walk-through of installation and contains much of the information on  this page.
    • The installation location doesn't matter, generally speaking. However, one of the utilities used by the installer to update the ubroker.properties file with the AppServer, database and WSA information doesn't work well with spaces in the pathname. If you install into a location with a space in the path, you'll have to manually install the AppServer etc.
    • The default port numbers provided for the database and AppServer may overlap those provided for the AutoEdge|TheDealer (aka the 'old' AutoEdge) databases and AppServers. Make sure that these are unique port numbers.

  • Once the installer completes, check the AppServer and database setups in OpenEdge Explorer/Management, and start the DB ("dbAutoEdgeTheFactory") and AppServer ("asAutoEdgeTheFactory").
  • Using PDSOE, import the ABL projects. There's a link to the development environment in the installed program group. 
    • Select a workspace location (existing or new)
    • Select File > Import > Import existing projects into workspace. Navigate to the <install_dir>/AutoEdge/Factory/ folder, and select OK. A list of projects appears. Select all of them except for those that are Savvion projects: CustomerOrderProcess is currently the only such project; we will import those into Savvion in a separate step.
    • The import should take a couple of minutes, and will set up the Propath for the projects too.
    • Set up the database connection in PDSOE, and associate it with the AutoEdge|TheFactory Server project. None of the other projects require a connected database.

  • Now we import the BPM projects into Progress Developer Studio for Savvion (or Process Modeller). The process is the same as above, and we only import the 1 Savvion project (CustomerOrderProcess).
    • We need to ensure that the servers, ports and user name/passwords are correct for the OpenEdge webservices as well as the Savvion Business Manager being used.  
      • Check the CustomerVehicleOrderSubmit flow's BIZSITE_USER and BIZSITE_PASSWORD dataslots for validity. These values need to match as user in the Savvion BM server.
    • Also make sure that all of the email steps in the CustomerVehicleOrderSubmit and CustomerOrderVehicle flows point at a valid email / SMTP server. They currently use 'localhost'. The lack of an email server should not affect the running of the process though.
    • Once updated, all contained processes need to be deployed to the Savvion BM server.

Version history

Releases including and after v1.0.4 will have their own documents/pages with release notes and other information.

VersionArchiveNotes
1.0.11

AutoEdgeTheFactorySetup-1.0.11.zip

  • Update installer for 64-bit Windows clients.
  • Release notes here
1.0.10

AutoEdgeTheFactorySetup-1.0.10.zip

  • Update bits for OpenEdge Release 11.2
  • Separate InjectABL dependency injection library into a separate project
  • Release notes here
1.0.9 AutoEdgeTheFactorySetup-1.0.9.zip
  • Fix filtering bug in fetch request when filtering datasource with single table
  • Added license files and header text to source
  • Release notes here
1.0.8 AutoEdgeTheFactorySetup-1.0.8.zip
  • Replace WebServices with OE Managed Adapter
  • Use built-in JSON classes
  • Bugfix to installer when using OE11.1.0
  • Release notes here
1.0.7 AutoEdgeTheFactorySetup-1.0.7.zip
  • Bugfix to installer when using OE11.0.0
  • Release notes here
1.0.6 AutoEdgeTheFactorySetup-1.0.6.zip
  • Installer updates, enable installation for OE release 11.0.0
  • Release notes here
1.0.5 AutoEdgeTheFactorySetup-1.0.5.zip
  • IMPORTANT: The user names in both the OpenEdge and Savvion have changed. Please read the release notes for more information.
1.0.4 AutoEdgeTheFactorySetup-1.0.4.zip
  • Release notes here
1.0.0 - 1.0.3 Individually specified below
  • Release notes for all releases up to and including 1.0.3 are here. These notes consist largely of information that was previously contained in this  Getting Started page, but following the large changes in user names etc in 1.0.5, have been archived in a separate document.
1.0.3 AutoEdgeTheFactorySetup-1.0.3.zip
  • Simplification of roles/groups/users in Savvion Models (thanks Ken Wilner)
  • Create managed adapters for all WebServices calls  (Ken)
  • Bug fixes in Dealer Review UI (thanks Brent, Gary Clink, Moritz Roedel)
  • Updated Vehicle Order model (Presentation Flow)
1.0.2 AutoEdgeTheFactorySetup-1.0.2.zip
  • Fix for Dealer UI, including the order capture and retrieval entity.
  • Fix for incorrect line endings in client.ini (reported by Brent Adonis)
  • Updated the user logins - reduced the numbers of users for ease-of-use.
1.0.1 AutoEdgeTheFactorySetup-1.0.1.zip
  • Updated Savvion models to work correctly in 7.6 (reported by Laurent Kieffer)
  • Point all WebServices adapters to localhost (rep. Laurent Kieffer)
1.0.0 AutoEdgeTheFactorySetup-1.0.0.zip
  • Initial release

Recorded guides

Please note that these guides are not up-to-date, and refer to versions of AutoEdge|TheFactory up to about 1.0.4.

  • The installation guide is here ; it contains a walk-through of the installation process (approx 15min)
  • A recording describing the design process in SBM Studio is here (approx 30min)
  • A recording running through the process appears here (approx 12min)

Email Users

Each application user has an email address, as described in the list of users attached to the release notes pages. The choice of the AETF domain is deliberate - since it doesn't exist in the real Internet, there's no danger of email leaking out to real people or companies. Most mail servers should be able to cope with this odd domain without trouble; if an email server is required for your server platform, hMailServer works extremely well on Windows, as described in javascript:;

AutoEdgeTheFactory-InstallationGuide.wmv.zip

AutoEdgeTheFactorySetup-1.0.0.zip

AutoEdgeTheFactorySetup-1.0.1.zip

AutoEdgeTheFactorySetup-1.0.2.zip

AutoEdgeTheFactorySetup-1.0.3.zip

AutoEdgeTheFactory_GettingStarted_Design.wmv.zip

AutoEdgeTheFactory_GettingStarted_Runtime.wmv.zip

Comments
  • Peter, I guess there's something missin in the tasks described here. 1.) I'd suggest you supply an exported (and customized) version of an XML files that allows us to import the database connections, rather than to create it manually. For the manual step, the document should list the name of the DB connection anyway so that it's recognized by the server code project (matching the name in the .dbconnection file).2.) To be able to compile the code you'll also have to import the projects in the <install_dir>/AutoEdge/Factory/referencecomponents folder. The propath references in the autoedgethefactory projects won't work otherwise. Nothing will compile because of the missing routine-level.i include file if you don't do this.Further you mention in the document, that the client project does not need DB connections - but you'll get compile errors on the tests if you don't supply them....Mike

  • /AutoEdge TheFactory Server/src/AutoEdge/Factory/Server/Order/BusinessComponent/OrderTableDS.clsLine 236 contains a "me" which causes a compilation error - also caused error messages in the AppServer log during startup of the AppServers.A few lines above (line 226) there was a query:                 find first lbEmployee where                           lbEmployee.DealerId eq lbDealer.DealerId and                           lbEmployee.DepartmentId eq lbDepartment.DepartmentId and                           lbEmployee.TenantId eq lbDealer.TenantIdRservice                           no-lock no-error. that caused compile errors. I've changed that to:                 find first lbEmployee where                           lbEmployee.DealerId eq lbDealer.DealerId and                           lbEmployee.DepartmentId eq lbDepartment.DepartmentId and                           lbEmployee.TenantId eq lbDealer.TenantId                           no-lock no-error.  That solves the compile issue. Could anybody please confirm this change? Besides that I only have compilation issues in various test folders.

  • Rservice is equivalent to SHFT-CTRL-R and service in Architect and the reason why it's in code is that the dialogue is not coming up quickly enough. Thanks for finding these.

  • :-)

  • Peter, I guess there's something missin in the tasks described here. 1.) I'd suggest you supply an exported (and customized) version of an XML files that allows us to import the database connections, rather than to create it manually. For the manual step, the document should list the name of the DB connection anyway so that it's recognized by the server code project (matching the name in the .dbconnection file).Customised by the installer? And yes, will do.2.) To be able to compile the code you'll also have to import the projects in the <install_dir>/AutoEdge/Factory/referencecomponents folder. The propath references in the autoedgethefactory projects won't work otherwise. Nothing will compile because of the missing routine-level.i include file if you don't do this.I thought this was clear, but I'll make the dependencies explicit. Should this be in Getting Started? or in each layers' page?-- peter

  • I thought this was clear, but I'll make the dependencies explicit. Should this be in Getting Started? or in each layers' page?We followed the getting started and it was missing there.

  • Savvion is mandatory for install AutoEdgeTheFactory 1.0.6 with OpenEdge 11.0?I can't see AutoEdgeTheFactory code without Savvion?Juanjo

  • Hi JuanjoYou can install and look at the code etc, you just won't be able to run the Savvion related code.

  • Savvion is not mandatory: the installer will allow you to exclude those components.-- peter

  • Ok. Thanks.But then I don't know what is happening: I run the installer of AutoEdgeTheFactory. In an installation step, it detects my version of OpenEdge (11.0), then I click "Next" button but the installer don't continues ...I've also tried to exclude the two components of Savvion in the installer but the result is the same: when I click "Next" button in the version detection step, The installer does not do anything.

  • Hello!AutoEdgeTheFactory 1.0.10OpenEdge 11.2 Ent Eval 32 bitWindows 7 Pro  64 bitEarlier I did not used the AutoEdge.I can not start the AppServer.  I have this error in the server log file[13/04/26@15:51:54.547+0400] P-002448 T-002396 1 AS -- Logging level set to = 2[13/04/26@15:51:54.547+0400] P-002448 T-002396 1 AS -- Log entry types activated: ASPlumbing,DB.Connects[13/04/26@15:51:54.548+0400] P-002448 T-002396 2 AS AS Starting application server for asAutoEdgeTheFactory. (5560)[13/04/26@15:51:54.566+0400] P-002448 T-002396 2 AS AS Application Server Startup. (5473)[13/04/26@15:51:57.297+0400] P-002448 T-002396 1 AS -- (Procedure: 'OpenEdge/CommonInfrastructure/Server/as_startup.p' Line:59) *** Progress.Lang.AppError[13/04/26@15:51:57.297+0400] P-002448 T-002396 1 AS -- (Procedure: 'OpenEdge/CommonInfrastructure/Server/as_startup.p' Line:60)   AutoEdge.Factory.Server.Common.CommonInfrastructure.TenantManager is not a valid type[13/04/26@15:51:57.298+0400] P-002448 T-002396 1 AS -- (Procedure: 'OpenEdge/CommonInfrastructure/Server/as_startup.p' Line:61)   ArgumentIsValidType OpenEdge.Lang.Assert at line 197  (.\referencecomponents\support\src\OpenEdge\Lang\Assert.cls)[13/04/26@15:51:57.298+0400] P-002448 T-002396 1 AS -- (Procedure: 'OpenEdge/CommonInfrastructure/Server/as_startup.p' Line:61) To OpenEdge.Core.InjectABL.Binding.BindingBuilder at line 83  (.\referencecomponents\injectabl\src\OpenEdge\Core\InjectABL\Binding\BindingBuilder.cls)[13/04/26@15:51:57.298+0400] P-002448 T-002396 1 AS -- (Procedure: 'OpenEdge/CommonInfrastructure/Server/as_startup.p' Line:61) Load AutoEdge.Factory.Server.InjectABL.CommonModule at line 48  (.\autoedgethefactory\server\src\AutoEdge\Factory\Server\InjectABL\CommonModule.cls)[13/04/26@15:51:57.298+0400] P-002448 T-002396 1 AS -- (Procedure: 'OpenEdge/CommonInfrastructure/Server/as_startup.p' Line:61) OnLoad OpenEdge.Core.InjectABL.Binding.Modules.InjectionModule at line 70  (.\referencecomponents\injectabl\src\OpenEdge\Core\InjectABL\Binding\Modules\InjectionModule.cls)[13/04/26@15:51:57.298+0400] P-002448 T-002396 1 AS -- (Procedure: 'OpenEdge/CommonInfrastructure/Server/as_startup.p' Line:61) Load OpenEdge.Core.InjectABL.KernelBase at line 162  (.\referencecomponents\injectabl\src\OpenEdge\Core\InjectABL\KernelBase.cls)[13/04/26@15:51:57.298+0400] P-002448 T-002396 1 AS -- (Procedure: 'OpenEdge/CommonInfrastructure/Server/as_startup.p' Line:61) C:\Arelav\OpenEdgeAE\AutoEdge\Factory\autoedgethefactory\server\bin\load_injectabl_modules.r at line 36  (C:\Arelav\OpenEdgeAE\AutoEdge\Factory\autoedgethefactory\server\bin\load_injectabl_modules.r)[13/04/26@15:51:57.298+0400] P-002448 T-002396 1 AS -- (Procedure: 'OpenEdge/CommonInfrastructure/Server/as_startup.p' Line:61) Load OpenEdge.Core.InjectABL.KernelBase at line 225  (.\referencecomponents\injectabl\src\OpenEdge\Core\InjectABL\KernelBase.cls)[13/04/26@15:51:57.298+0400] P-002448 T-002396 1 AS -- (Procedure: 'OpenEdge/CommonInfrastructure/Server/as_startup.p' Line:61) Load OpenEdge.Core.InjectABL.KernelBase at line 252  (.\referencecomponents\injectabl\src\OpenEdge\Core\InjectABL\KernelBase.cls)[13/04/26@15:51:57.298+0400] P-002448 T-002396 1 AS -- (Procedure: 'OpenEdge/CommonInfrastructure/Server/as_startup.p' Line:61) OpenEdge/CommonInfrastructure/Common/start_session.p at line 101  (.\referencecomponents\commoninfrastructure\shared\src\OpenEdge\CommonInfrastructure\Common\start_session.p)[13/04/26@15:51:57.298+0400] P-002448 T-002396 1 AS -- (Procedure: 'OpenEdge/CommonInfrastructure/Server/as_startup.p' Line:61) OpenEdge/CommonInfrastructure/Server/as_startup.p at line 41  (.\referencecomponents\commoninfrastructure\server\src\OpenEdge\CommonInfrastructure\Server\as_startup.p)[13/04/26@15:51:57.298+0400] P-002448 T-002396 1 AS -- OpenEdge/CommonInfrastructure/Server/as_startup.p  startup procedure ended with an ERROR condition. (8025)[13/04/26@15:51:57.299+0400] P-002448 T-002396 2 AS AS Application Server Shutdown. (5476)  I need help.Thanks!

  • Problem was solved. I had a compiled file load_injectabl_modules.r is dated 11.03.2013, which was located in the directory C: \ Arelav \ OpenEdgeAE \ AutoEdge \ Factory \ autoedgethefactory \ server \ binbecause of him APP did not start. I deleted it, now everything is fine. Probably the file was in the distribution and it was from the old assembly.