When you have @component annotation and override activate() method it should automatically initialize when bundle become 'Active' status. To make it immediately active when the bundle is deployed, use @Component(immediate=true)

Open a support ticket and see if they have any better solution !

Can you share your code snippet so we can see if something missing

to add to @jorg, you need to have a mapping between the data and your content modelling. Once you do this exercise, then it would be easy to come up with the strategy of doing the migration. It may be directly creating an xml structure and uploading it or it may be writing a simple service to create...

Hi Kalyan,I dont think teaser component is deprecated instead its named as 'offer'. If you look at the component, Offer uses the teaser component. Try using Offer instead of Target and see if it works Regards,Lokesh

session state you would have got when getting resolver might have been stale by the time you are saving. It happens sometime when you are saving node in the Oak. So always its better to do session.refresh()  and then save()

It looks like logged in User doesnt have permission to impersonate the given userId. Have you configured the same for the logged in User in useradmin ?

I dont think it would be a valid usecase !!Normally, you will have to enable the components for a template and the permissions for creating the pages using that template can be controlled using ACLs.

You will have to connect with Adobe Sales team where they will get the required consulting from Adobe.

So every step of a workflow, you have 'complete' to go fwd and 'Step Back' to basically use it as a reject where it goes to the previous step