Changes for page Install Local Connector

Last modified by Erik Bakker on 2024/02/22 12:20
From version 11.1
edited by Erik Bakker
on 2023/01/24 15:20
Change comment: There is no comment for this version
To version 12.1
edited by Erik Bakker
on 2024/02/22 12:20
Change comment: Renamed back-links.

Summary

Details

Page properties
Content
... ... @@ -1,5 +1,6 @@
1 -{{container}}{{container layoutStyle="columns"}}(((
2 -
1 +{{container}}
2 +{{container layoutStyle="columns"}}
3 +(((
3 3  In this microlearning, we will focus on installing the eMagiz environment locally
4 4  Should you have any questions, please contact academy@emagiz.com.
5 5  
... ... @@ -7,23 +7,23 @@
7 7  
8 8  To install a runtime, please be aware that eMagiz needs an environment that satisfies certain requirements. These requirements can be different depending on your architectural choices. Most common is the connector inside your network and a JMS and container running outside the network. In that case, if you are running only connectors in this environment, please keep the following requirements in mind:
9 9  
10 -* OS with support for Java
11 -* OS user with granted security rights to run startup services (Windows services)
12 -* The correct Java installation ([[Java 8 SE JRE>>https://adoptopenjdk.net||target="blank"]] for example) with NO automatic updates. OpenJDK 8 is currently the recommended version for eMagiz installations.
13 -* NTP synchronization – all eMagiz service instances should use the same time and settings.
14 -* Access to the internet
15 -* Outbound JMS traffic - port 8443 (and 8444 in case of failover situation) - amqp.emagiz.com / cloudXXXX.emagizcloud.com
11 +* OS with support for Java
12 +* OS user with granted security rights to run startup services (Windows services)
13 +* The correct Java installation ([[Java 8 SE JRE>>https://adoptopenjdk.net||target="blank"]] for example) with NO automatic updates. OpenJDK 8 is currently the recommended version for eMagiz installations.
14 +* NTP synchronization – all eMagiz service instances should use the same time and settings.
15 +* Access to the internet
16 +* Outbound JMS traffic - port 8443 (and 8444 in case of failover situation) - amqp.emagiz.com / cloudXXXX.emagizcloud.com
16 16  ** General monitoring data to eMagiz iPaaS
17 17  ** Specific JMS traffic to eMagiz JMS Server
18 -* Outbound HTTPS traffic
19 +* Outbound HTTPS traffic
19 19  ** port 443
20 20  ** Specific provisioning data
21 21  *** [[RTS>>https://rts.emagiz.com/ws/||target="blank"]]
22 22  *** [[eMagiz repository>>https://repository.emagiz.com||target="blank"]]
23 -* Hardware requirements
24 +* Hardware requirements
24 24  ** Modern CPU
25 25  ** Enough Disk Space according to sizing calculations
26 -* Enough Memory according to sizing calculations
27 +* Enough Memory according to sizing calculations
27 27  * JAVA_HOME variable is properly set
28 28  
29 29  == 2. Key concepts ==
... ... @@ -61,11 +61,14 @@
61 61  org.eclipse.gemini.blueprint.extender - 2.1.0.RELEASE | Application context successfully refreshed ApplicationContext(bundle=nl.capesystemsintegration.demo.bus.commupd.ordsys.connector-infra.spring, config=nl.capesystemsintegration.demo.bus.commupd.ordsys.connector-infra.spring_1.0.0.52.xml))
62 62  
63 63  If you see the expected logging, verify in eMagiz if:
64 -* You can reach the runtime via the runtime dashboard.
65 -* You see runtime statistics in Manage.
66 66  
67 -{{warning}}If you see an error or the popup closes itself immediately, please check the above steps and requirements. If the popup closes this is probably due to a mismatch between the Java version and runtime version. Please look back at the section explaining how to set JAVA_HOME for more information. If all the above steps are correct and you are not able to identify the issue, please contact your implementation partner.{{/warning}}
66 +* You can reach the runtime via the runtime dashboard.
67 +* You see runtime statistics in Manage.
68 68  
69 +{{warning}}
70 +If you see an error or the popup closes itself immediately, please check the above steps and requirements. If the popup closes this is probably due to a mismatch between the Java version and runtime version. Please look back at the section explaining how to set JAVA_HOME for more information. If all the above steps are correct and you are not able to identify the issue, please contact your implementation partner.
71 +{{/warning}}
72 +
69 69  == 4. Key takeaways ==
70 70  
71 71  * eMagiz has a runtime software component that allows running flows inside. It is generic for all types of flows that exist in eMagiz
... ... @@ -80,8 +80,13 @@
80 80  * [[Runtime Security>>Main.eMagiz Academy.Microlearnings.Intermediate Level.Portal Security.intermediate-portal-security-runtime-security||target="blank"]]
81 81  * [[Edit Runtime Memory Windows>>Main.eMagiz Academy.Microlearnings.Intermediate Level.Solution Architecture.intermediate-solution-architecture-edit-memory-on-premise-runtime-windows||target="blank"]]
82 82  * [[Architecture runtime decisions>>Main.eMagiz Academy.Microlearnings.Advanced Level.Solution Architecture.advanced-solution-architecture-runtime-decision.WebHome||target="blank"]]
83 -* [[Edit Runtime Memory Linux>>Main.eMagiz Academy.Microlearnings.Advanced Level.Solution Architecture.advanced-solution-architecture-change-memory-runtime-linux.WebHome||target="blank"]]
87 +* [[Edit Runtime Memory Linux>>Main.eMagiz Academy.Microlearnings.Legacy Functionality.advanced-solution-architecture-change-memory-runtime-linux.WebHome||target="blank"]]
84 84  * [[Install runtime on Linux>>Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-platform-deploy-install-local-connector-linux||target="blank"]]
85 85  * [[Install runtime on Windows>>Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-platform-deploy-install-local-connector-windows||target="blank"]]
90 +)))
86 86  
87 -)))((({{toc/}}))){{/container}}{{/container}}
92 +(((
93 +{{toc/}}
94 +)))
95 +{{/container}}
96 +{{/container}}