Unfortunately, it looks like the documentation is out of date. It should
look something like this:
Path myConfig = Path.of("conf/ignite-config.conf");
Path myWorkDir = Path.of("/home/ignite");
IgniteServer node = IgniteServer.start("node", myConfig, myWorkDir);
InitParameters initParameters = InitParameters.builder()
.metaStorageNodeNames("node")
.clusterName("cluster")
.build();
node.initCluster(initParameters);
var ignite = node.api();
I would suggest you consider stand-alone mode, connecting to the cluster
using a client. Embedded mode is a valid option but (my personal view) is
that it shouldn't be the default choice.
Regards,
Stephen
On Thu, 10 Jul 2025 at 10:47, Vijay Chaurasiya
<vijay.chauras...@beyondsquare.com.invalid> wrote:
> Dear Apache Ignite Team,
> I am currently evaluating Apache Ignite version 3.0.0 for use within an
> embedded Tomcat-based Java application.
> While following the official documentation for Embedded Mode<
> https://ignite.apache.org/docs/ignite3/latest/quick-start/embedded-mode>,
> I noticed that the class org.apache.ignite.IgnitionManager, which is
> referenced for starting an embedded node, appears to be missing from the
> 3.0.0 release artifacts.
> To confirm, I have:
>
> *
> Used the official 3.0.0 Maven dependencies and binary distribution
> *
> Attempted importing IgnitionManager in a clean Java project
> *
> Verified that the class is not present in the available package structure
>
> I would appreciate your clarification on the following points:
>
> 1.
> Has the IgnitionManager class been renamed, moved, or deprecated in
> version 3.0.0?
> 2.
> Is there an alternative way to start an embedded Ignite node
> programmatically in this version?
> 3.
> Should the current documentation be updated to reflect any such changes?
>
> Your assistance would be greatly appreciated, as we are considering Ignite
> 3 for production use in our platform.
> Thank you for your time and continued efforts in maintaining the Apache
> Ignite project.
> Warm regards,
> Vijay Chaurasiya
>
>
>
