Performances are similar between Oracle storage and SQL Server storage of MEGA data.
It is not clear the performances will be improved when switching to Oracle storage.
What is important is the technical infrastructure supporting the MEGA installation.
If you can improve or tune it, it is likely that you get better performances.
... View more
This version (MEGA 2009 SP4 CP3 version (build 724-2848)) is indeed quite old an cannot be downloaded easily.
Please open a case with Technical support to get an installation master for this version.
You can use this form http://community.mega.com/t5/custom/page/page-id/mega-support-case
By the way, warn your customer that he should seriously consider an upgrade to a more recent version.
MEGA 2009 SP4 is already in limited maintenance phase. It will no longer be supported after December 2013
... View more
Hello, We are answering a proposal from a possible client. They are interested in modeling their processes and simulation, so we are presenting MEGA Process BPMN and the Simulation components. One of the concerns that was raised during the RFP was that the they wanted to model a mix of their roles and their Organizational structure. The scenario is as follows: In a Process (Process_A) we have a participant that does some tasks. In that process, the participant would have a role called Controller. But in terms of all the processes the Controller role can be done by the Operations Department or by the Marketing Department. What would you recommend to model this correctly? On one hand the Controller role would be a perfect match for an Org-Unit of type function. But that would not relate it directly with the Organizational structure. I suppose we could decompose the Controller Org-unit with two sub-org-units (Operations Department and Marketing Department). But then you loose some flexibility, for instance to model that in a given process the role is implemented only by one of the Org-Units and not by both. On the other hand they expressed the desire to model not the role, but some part of the Organizational structure having a specific role in a specific process. So they would like not to model the Controller role itself, but rather say that in Process_A the Operations Department has the role of Controller, but in a Process_B the same Operations Department would have a role of Evaluator. And in in a Process_C role of Controller is done by the Marketing Department Org-unit. For this case I though about using the Org-Unit and using the "conditioning" property in the Participant assignment, trying to say that Operations Department has a role of Controller in one process, and a role of Evaluator in another process. What would you recommend to model this? They are mainly concerned with the correct modeling of this in terms of maintainability of the models. If the organizational structure changes a bit, they want to avoid trying to manually update dozens or hundreds of processes. Another concern is how will this impact the reports that come out-of-the-box and the simulation module?
... View more
Hi, I have a question regarding Participant assignment (specifically Org-Units) and conditioning. First is the assignment of multiple participants (in my example they are all Org-Units - Example1.png). What is being modeled when you do this? - All the assigned org-units are responsible for the tasks inside that container? (i.e. you need all of them to do those tasks) - Any of the assigned org-units is responsible for the tasks inside that container? (i.e. you only need one of them do the tasks, and any one of those Org-UInits can do the tasks) - Other possibilities? The second question is regarding the conditioning when you do an assignment. Whet is the purpose of conditioning? Is there a specific semantics regarding it's usage, or are you completelly free to model any conditioning you want for you assigned Org-units? In my second example, what would be the correct interpretation when you look at that participant: - two Org-units have no conditioning - one Org-unit has conditioning "conditioning_1" - one Org-unit has conditioning "conditioning_2" what are the responsabilities of these org-units in the process when you model that? Thanks.
... View more
From what we could see in the manual, that seems to be the proper method for migrating data in our scenario (One storage medium to a different storage medium).
--> Yes. I confirm the feature recommended for migrating data is the feature 'Reorganize repository' described p 60 of this document (Migrating Your Data from One Storage Support to Another)
Is this the ideal setup for doing the data migration we intend to?
--> what is expected is that the machine running the migration process
- has MEGA installation with a MEGA licence programmed with both products ('MEGA Repository Storage (SQL Server)' AND 'MEGA Repository Storage (Oracle)')
MEGA Repository Storage (SQL Server)
- has a connection to running instance or Oracle (source database server)
- has a connection to running instance or SQL Server (target database server)
You can check both connections by defining a connection in MEGA
See page 15 (Defining an oracle Connection) of the above document
See page 31 (Defining a MEGA SQL Server Connection) of the above document
- SQL server is configured with SQL server authentication
- You have a SQL server user account with the expected privileges
See page 30 of the above document (User privileges)
Also, what would be the best way of creating the target repository?
--> You can either have MEGA create the SQL server repositories or create SQL server repositories manually from SQL Server and have MEGA them. It mainly depends on the privileges you can have.
The first option is easier (have MEGA create the SQL server repositories).
If you use the second option (create SQL server repositories manually from SQL Server and have MEGA use them):
- Follow the naming rule: <Environment folder name>_SystemDb
- Select the option 'Use an existing SQL Server database' at repository creation
... View more
No, it is possible to do an update over the existing installation .
I suggest to keep a backup of your customized files in order to restore them once the new version is installed .
1- The Mega_Std folder contains the standard files, its content may be updated from version to version . it is always recommended to store your customized files in the Mega_Usr folder.
2- If Mega advisor is used, be careful on keeping a backup of the customized files from the advisor installation folder before uninstalling the current version in order to restore them once the new version is installed .
... View more