Giter Site home page Giter Site logo

Comments (9)

coatpont avatar coatpont commented on June 10, 2024

please check https://github.com/Adobe-Marketing-Cloud/aem-demo-machine/wiki/Infrastructure on how to point at an external Mongo instance (by default, but that's for MacOS only, it's pointing at the mongoDB instance that can be setup with the demo machine itself)

from aem-demo-machine.

kapilmalik84 avatar kapilmalik84 commented on June 10, 2024

Thanks Coatpont,
i need more help here to understand the values we need to provide on a windows 2008 R2 machine having an external mongobd install.
can you please suggest if the values are right?
Prpopery name Default value custom value

  1. demo.mongo mongodb-osx-x86_64-3.2.9 C:\Program Files\MongoDB\Server\3.4\bin\mongo.exe
  2. demo.mongo.external false true
  3. demo.mongo.path mongo C:\Program Files\MongoDB\Server\3.4\bin\mongo.exe
  4. demo.mongo.service false "What should be the value here in my case"

Thanks
Kapil

from aem-demo-machine.

coatpont avatar coatpont commented on June 10, 2024

I think all you need is
demo.mongo.external=true
demo.mongo.service=false (this is used to start/stop it as a service on linux only).

from aem-demo-machine.

kapilmalik84 avatar kapilmalik84 commented on June 10, 2024

Mongod should be running on the same system?
should i use /bin/mongod --dbpath as the command to start mongo?
i was getting an IOException with error code=5
but after making the change to Mongo.exe and mongod.exe security settings to give "Full Control" i am not getting that exception now.

from aem-demo-machine.

coatpont avatar coatpont commented on June 10, 2024

No, Mongo doesn't need to be on the same host.
You'll have to start/stop MongoDb separately wit Mongo scripts

from aem-demo-machine.

coatpont avatar coatpont commented on June 10, 2024

on precision though, this configuration (external Mongo on Windows) has not be tested before (just one MacOS), so there might be side effects to investigate.

from aem-demo-machine.

kapilmalik84 avatar kapilmalik84 commented on June 10, 2024

ok,
This is giving error while starting the AEM for the first time. This is from Error.log
15.05.2017 12:16:41.714 ERROR [FelixStartLevel] org.apache.jackrabbit.oak-core [org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreService(69)] Failed creating the component instance; see log for reason
15.05.2017 12:24:36.264 ERROR [qtp1625153106-163] org.apache.felix.metatype Missing element AD in element OCD : bundle://283.0:0/OSGI-INF/metatype/com.day.cq.workflow.compatibility.AbsoluteTimeoutHandlerProxyImpl.xml
15.05.2017 12:24:36.265 ERROR [qtp1625153106-163] org.apache.felix.metatype Missing element AD in element OCD : bundle://283.0:0/OSGI-INF/metatype/com.day.cq.workflow.compatibility.CQDynamicParticipantExecutor.xml
15.05.2017 12:24:36.266 ERROR [qtp1625153106-163] org.apache.felix.metatype Missing element AD in element OCD : bundle://283.0:0/OSGI-INF/metatype/com.day.cq.workflow.compatibility.CQWorkflowExtProcessProxy.xml
15.05.2017 12:24:36.266 ERROR [qtp1625153106-163] org.apache.felix.metatype Missing element AD in element OCD : bundle://283.0:0/OSGI-INF/metatype/com.day.cq.workflow.compatibility.CQWorkflowProcessRunner.xml
15.05.2017 12:24:36.266 ERROR [qtp1625153106-163] org.apache.felix.metatype Missing element AD in element OCD : bundle://283.0:0/OSGI-INF/metatype/com.day.cq.workflow.compatibility.ScriptContextProviderImpl.xml
15.05.2017 12:24:36.266 ERROR [qtp1625153106-163] org.apache.felix.metatype Missing element AD in element OCD : bundle://283.0:0/OSGI-INF/metatype/com.day.cq.workflow.impl.CQPayloadMap.xml
15.05.2017 12:24:36.461 ERROR [qtp1625153106-163] org.apache.felix.metatype Missing element AD in element OCD : bundle://283.0:0/OSGI-INF/metatype/com.day.cq.workflow.compatibility.AbsoluteTimeoutHandlerProxyImpl.xml
15.05.2017 12:24:36.461 ERROR [qtp1625153106-163] org.apache.felix.metatype Missing element AD in element OCD : bundle://283.0:0/OSGI-INF/metatype/com.day.cq.workflow.compatibility.CQDynamicParticipantExecutor.xml
15.05.2017 12:24:36.462 ERROR [qtp1625153106-163] org.apache.felix.metatype Missing element AD in element OCD : bundle://283.0:0/OSGI-INF/metatype/com.day.cq.workflow.compatibility.CQWorkflowExtProcessProxy.xml
15.05.2017 12:24:36.462 ERROR [qtp1625153106-163] org.apache.felix.metatype Missing element AD in element OCD : bundle://283.0:0/OSGI-INF/metatype/com.day.cq.workflow.compatibility.CQWorkflowProcessRunner.xml
15.05.2017 12:24:36.462 ERROR [qtp1625153106-163] org.apache.felix.metatype Missing element AD in element OCD : bundle://283.0:0/OSGI-INF/metatype/com.day.cq.workflow.compatibility.ScriptContextProviderImpl.xml
15.05.2017 12:24:36.462 ERROR [qtp1625153106-163] org.apache.felix.metatype Missing element AD in element OCD : bundle://283.0:0/OSGI-INF/metatype/com.day.cq.workflow.impl.CQPayloadMap.xml
15.05.2017 12:24:36.507 ERROR [qtp1625153106-163] org.apache.felix.metatype Missing element AD in element OCD : bundle://283.0:0/OSGI-INF/metatype/com.day.cq.workflow.compatibility.AbsoluteTimeoutHandlerProxyImpl.xml
15.05.2017 12:24:36.508 ERROR [qtp1625153106-163] org.apache.felix.metatype Missing element AD in element OCD : bundle://283.0:0/OSGI-INF/metatype/com.day.cq.workflow.compatibility.CQDynamicParticipantExecutor.xml
15.05.2017 12:24:36.508 ERROR [qtp1625153106-163] org.apache.felix.metatype Missing element AD in element OCD : bundle://283.0:0/OSGI-INF/metatype/com.day.cq.workflow.compatibility.CQWorkflowExtProcessProxy.xml
15.05.2017 12:24:36.508 ERROR [qtp1625153106-163] org.apache.felix.metatype Missing element AD in element OCD : bundle://283.0:0/OSGI-INF/metatype/com.day.cq.workflow.compatibility.CQWorkflowProcessRunner.xml
15.05.2017 12:24:36.508 ERROR [qtp1625153106-163] org.apache.felix.metatype Missing element AD in element OCD : bundle://283.0:0/OSGI-INF/metatype/com.day.cq.workflow.compatibility.ScriptContextProviderImpl.xml
15.05.2017 12:24:36.509 ERROR [qtp1625153106-163] org.apache.felix.metatype Missing element AD in element OCD : bundle://283.0:0/OSGI-INF/metatype/com.day.cq.workflow.impl.CQPayloadMap.xml
15.05.2017 12:24:36.551 ERROR [qtp1625153106-163] org.apache.felix.metatype Missing element AD in element OCD : bundle://283.0:0/OSGI-INF/metatype/com.day.cq.workflow.compatibility.AbsoluteTimeoutHandlerProxyImpl.xml
15.05.2017 12:24:36.551 ERROR [qtp1625153106-163] org.apache.felix.metatype Missing element AD in element OCD : bundle://283.0:0/OSGI-INF/metatype/com.day.cq.workflow.compatibility.CQDynamicParticipantExecutor.xml
15.05.2017 12:24:36.551 ERROR [qtp1625153106-163] org.apache.felix.metatype Missing element AD in element OCD : bundle://283.0:0/OSGI-INF/metatype/com.day.cq.workflow.compatibility.CQWorkflowExtProcessProxy.xml
15.05.2017 12:24:36.551 ERROR [qtp1625153106-163] org.apache.felix.metatype Missing element AD in element OCD : bundle://283.0:0/OSGI-INF/metatype/com.day.cq.workflow.compatibility.CQWorkflowProcessRunner.xml
15.05.2017 12:24:36.552 ERROR [qtp1625153106-163] org.apache.felix.metatype Missing element AD in element OCD : bundle://283.0:0/OSGI-INF/metatype/com.day.cq.workflow.compatibility.ScriptContextProviderImpl.xml
15.05.2017 12:24:36.553 ERROR [qtp1625153106-163] org.apache.felix.metatype Missing element AD in element OCD : bundle://283.0:0/OSGI-INF/metatype/com.day.cq.workflow.impl.CQPayloadMap.xml
15.05.2017 12:24:36.594 ERROR [qtp1625153106-163] org.apache.felix.metatype Missing element AD in element OCD : bundle://283.0:0/OSGI-INF/metatype/com.day.cq.workflow.compatibility.AbsoluteTimeoutHandlerProxyImpl.xml
15.05.2017 12:24:36.594 ERROR [qtp1625153106-163] org.apache.felix.metatype Missing element AD in element OCD : bundle://283.0:0/OSGI-INF/metatype/com.day.cq.workflow.compatibility.CQDynamicParticipantExecutor.xml
15.05.2017 12:24:36.595 ERROR [qtp1625153106-163] org.apache.felix.metatype Missing element AD in element OCD : bundle://283.0:0/OSGI-INF/metatype/com.day.cq.workflow.compatibility.CQWorkflowExtProcessProxy.xml
15.05.2017 12:24:36.595 ERROR [qtp1625153106-163] org.apache.felix.metatype Missing element AD in element OCD : bundle://283.0:0/OSGI-INF/metatype/com.day.cq.workflow.compatibility.CQWorkflowProcessRunner.xml

from aem-demo-machine.

coatpont avatar coatpont commented on June 10, 2024

Sorry I don't know where this is coming from, it has not been reported before

from aem-demo-machine.

coatpont avatar coatpont commented on June 10, 2024

sorry no more suggestion please re-open if still a problem

from aem-demo-machine.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.