Do you have a custom authentication handler or SAML configured?. If
latter then ensure the group assignment and creation of group is working
as expected by looking at the OSGI config. If former then make sure that
your custom code is appropriately assigning proper group after it
receives the SAML assertion.
Do you have a component specific client libs written out for the date
field? Can you upload a screenshot of the properties so we can take a
look at how the date value is stored? As a property or as a node?
Here are the steps. You'll have to decompile some of the code if you
want to look at it.1) Decompile the SAML authentication Handler.2)
Create your own COMPANY authentication handler by copy pasting the code
from OOB SAML authentication Handler into it.3) Modify the code in your
custom class to create users under communities4) Disable OOB SAML and
enable your COMPANY authentication handler.
You're right, SAML will always create the user under /home/users,
irrespective of if you're using communities or not. You'll have to
extend the OOB SAML handler to create the node under communities vs
/home/users. Be careful though, if you do customize it then all users
who authenticate through SAML will have their username created under
communities path.
11.04.2018 00:30:20.380 *ERROR*
[com.adobe.granite.crx2oak.profile.ProfileHandler]
ProfileHandler.java:198 Tags: [datastore-path] are required but their
values were not resolved or not passed at command line.By looking at the
above log can you verify if your AEM 6.1 is configured to use data store
for binary assets? If so your command is not complete. You have to
specify the --src-datastore .
Do you run GC using Offline Compaction? Also check the code to make sure
there are no open connections you can check that using tools like
JMeter. Please refer to performance tuning guidelines for more
details.https://docs.adobe.com/docs/en/aem/6-2/administer/content/assets/best-practices-for-assets/performance-tuning-guidelines.html
Kkkrish wrote... huzaifaha98521146 wrote... in AEM 6.2 the correct way
to do what you're trying to do is through "metadata schemas" Here is the
doc.
https://docs.adobe.com/docs/en/aem/6-2/author/assets/managing-assets-touch-ui/brandportal/metadata-schemas.html
This would allow you to change the default schemas as well as introduce
new ones. Even if you tried to do an overlay of image, application etc
it won't work. I do not have an answer on why in this particular
instance it's not working for y...
In your compaction script add a sleep time of 45 seconds (depending on
how long your instance takes to shutdown + 20 seconds) after you've
shutdown AEM server as part of your script.
You can use javascript with slightly (html). In your JavaScript you have
access to implicit objects such as PageManager, currentContent,
currentSession etc. You need to create a function in your js file that
returns the value such as page node etc. Once you have that then you can
use slightly to pull the value from your javascript using helper object
. Example of this can be found under the link
below.http://blogs.adobe.com/experiencedelivers/experience-management/htl-javascript-use-api/
Did you check to see if port 4502 is open? If it is can you access
system/console? If you're running AEM on windows, make sure you have
your anti-virus software configured to allow AEM to run.
How big is your production repository vs lower environments? Also how
many CPU's and total memory do you have assigned to lower environment vs
production? Keep in mind that the OS also needs some memory for I/O
operations. Do you have a physical box assigned to each environment or
are they all running in separate VM's on a single physical box?
One way to do it is to use a bundled Java Class where you can put your
logic and then return the result you want into your componentName.html.
Here is an example from
https://docs.adobe.com/docs/en/htl/docs/use-api/java.html
/apps/my-example/component/info/Info.javapackage
org.example.app.components; import com.adobe.cq.sightly.WCMUse; public
class Info extends WCMUse { ...} Code samples are intended for
illustration purposes only.and, the data-sly-use statement must
reference the fully qualifie...
Do you have dynamic media enabled on your author instance? If you don't
have it enabled you won't see that option. Here are the steps.
https://docs.adobe.com/docs/en/aem/6-1/administer/content/dynamic-media/config-dynamic.html#Enabling
Dynamic Media
Do you have MongoDB with replicaset? or just single MongoDB as master?
Also if your author is on a separate box did you make sure that the port
on remoteserver 27017 is open?
Do not rely on system times for your live site especially when
scheduling a job the creation time will obviously be different than the
publish time. It looks like you are displaying creation time value to
your end user. Instead, create a new property called "articlePubDate"
and add the value of the scheduled time you want to be displayed. Then
use that property's value to display on the page.
sonalik77795449 wrote... Hello, Is there any reason why the components
won't be editable in both touch and classic UI post an AEM instance
restart.We are unable to open page properties too. This is a strange
behavior we started experience only now on the server after we had a
restart done recently.Any inputs would be helpful. Thanks. Are there any
exceptions in the log? Have you tried using admin account to make sure
it's not related to ACL? Were there any code changes done before the
restart? H...
Why not create another property for example oldName where you keep the
old X value in it. You can hide it by not displaying it to the user and
you can still reference to it in your code to pull the old values etc.
The answer to your first statement is Yes. If you want to create a
different set of metadata schema for a business use case then you can do
so by following the same link. Click on Create --> Create schema form.
BTW these schemas in 6.2 are created and kept under
/conf/global/settings/dam/adminui-extension/metadataschema........ Your
overlay in this case will not work since the path is different in 6.2 vs
6.0 and 6.1. I made similar changes when I performed a recent migration
from 6.1 to 6.2
are you using
org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreService.cfg?
if so did you specify which DB to use? Have you created a Replicaset? if
so have you created a keyfile that will be used by mongo? If you have
done everything correctly and its still not working then try dropping
the tables created when you initially start your AEM startup script and
try again.
in AEM 6.2 the correct way to do what you're trying to do is through
"metadata schemas" Here is the
doc.https://docs.adobe.com/docs/en/aem/6-2/author/assets/managing-assets-touch-ui/brandportal/metadata-schemas.htmlThis
would allow you to change the default schemas as well as introduce new
ones. Even if you tried to do an overlay of image, application etc it
won't work. I do not have an answer on why in this particular instance
it's not working for you but have an OOB solution that doesn't requi...
What do the replication logs say? Have you tried using an admin account
to see if it works?In replication logs do you see a - INFO - publish :
<< HTTP/1.1 200 OK if not check the ACL or the replication agent. Do you
see cq:lastReplicationAction ?
If you guys have done any UI customization on 6.0, they may not work
when you decide to migrate over from 6.1 to 6.2 in future. Just
something to be aware of. There could be many reasons why a repository
growth happens exponentially overnight. Are there any backend
scripts/processes running that interacts with the repository? Have you
tried putting in compaction script in place "In 6.2 it's called Revision
cleanup"? Have you placed any monitoring on the drives to see what is
the peak time when t...
