Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.
SOLVED

Where is web.xml and server.xml in AEM 5.6.1

Avatar

Level 4

I can't find web.xml and server.xml file in AEM 5.6.1.. i need to make some external setting in those xml???????

Thanks Chandra

1 Accepted Solution

Avatar

Correct answer by
Employee

These files aren't used in CQ/AEM unless you are deploying into an App Server.

View solution in original post

8 Replies

Avatar

Former Community Member

Hi Chandra,

as I imagine you need to add a 'filter' configuration into the web.xml. In
CQ you need to do this programatically and send the events to the
introscope classes. In other words, you need an adapter to introscope. Or
maybe this would help: http://forums.adobe.com/thread/1212573
 

Avatar

Correct answer by
Employee

These files aren't used in CQ/AEM unless you are deploying into an App Server.

Avatar

Level 4

I am surprised.,. how j2ee application without these configurations..I have to inject introspect xml into those..

Avatar

Level 10

Please elaborate what are you trying to achieve? 

Avatar

Level 4

There is some hook  (XML Entry )for Introspect. typically any j2ee application... those hooks are added that enabled to send message to extremal monitoring application .

In case AEm 5.6.1 i am not sure where i can put that xml where i can inject that hook.

Avatar

Employee

CQ is not a JavaEE container. It can run in a JavaEE container, but does not provide one.

If you provide the specific XML you are referring to, perhaps someone can tell you how to achive something similar in CQ.

Avatar

Level 10

Sorry I could not understand what you are exactly looking. Generally that you would configure in server.xml (most option should be availble in felix console http service in 5.6.1) & web.xml you would add like filters. You can bridge that gap with implementing [1].  

[1]   http://felix.apache.org/documentation/subprojects/apache-felix-http-service.html

Avatar

Level 10

Sham and Justin are correct -- with CQ you are not creating J2EE Enterprise beans such as session or entity beans or configuring it like a J2EE or even Spring Java application. You are working with OSGi components, Sling, and the JCR.