Hello,
I was wondering if anyone is using the Correspondence Management Solution Accelerator and has renamed their application from 'cmsa' to something else. For example, instead of the url http://<server>:<port>/cmsa/. it would be http://<server>:<port>/myprojectname/.
I've changed the following files that reference 'cmsa' already:
FSIApp\CreateCorrespondence\src\lcds-config\flex-config.xml
FSIApp\ManageTemplates\src\config\dct-config.xml
FSIApp\Portal\resources\security-config.xml
FSIApp\Portal\src\com\adobe\icc\bootstrap\AuthorizationBootstrapper.java
FSIApp\Portal\src\com\adobe\icc\bootstrap\URLRegistryBootstrapper.java
I've noticed that in the flexConfig that's loaded into both the CreateCorrespondence and ManageTemplate app that the pscmContext is set to 'cmsa', so this needs to change as well. Can someone point me in the right direction to change that? Also, are there any other files that need to be changed in order to make this happen and not break the apps?
Cheers,
K.
Solved! Go to Solution.
Views
Replies
Total Likes
Hi Kristian,
You should try changing the references to 'cmsa' in the following files:
[...\SA_SDK_9.5\CorrespondenceManagement]\
FSIApp\Portal\webapp\ClaimsPortal\pages\CreateCorrespondence.jsp
FSIApp\Portal\webapp\ClaimsPortal\pages\HomePage.jsp
FSIApp\ManageTemplates\src\config\dct-config.xml
FSIApp\CreateCorrespondence\src\lcds-config\flex-config.xml
FSIApp\Portal\src\com\adobe\icc\bootstrap\URLRegistryBootstrapper.java
FSIApp\Portal\webapp\WEB-INF\web.xml
FSIApp\Portal\resources\cm.properties [add a property here 'pscmContext=/{your context}'. For e.g., pscmContext=myprojectname]
FSIApp\Portal\resources\security-config.xml
However, I would say that it is only partially possible, because there are a couple of components that rely on 'cmsa' as the URL's context root, and hence would not work if you change it.
Those are the LCM Plugin Bootstrapper (which is used to bootstrap CMSA from LCM plugin) and the ImportUtility (which is used to import an exported ACP onto a target system) . But may be you can live with that.
Cheers,
~S.
Views
Replies
Total Likes
Hi Kristian,
You should try changing the references to 'cmsa' in the following files:
[...\SA_SDK_9.5\CorrespondenceManagement]\
FSIApp\Portal\webapp\ClaimsPortal\pages\CreateCorrespondence.jsp
FSIApp\Portal\webapp\ClaimsPortal\pages\HomePage.jsp
FSIApp\ManageTemplates\src\config\dct-config.xml
FSIApp\CreateCorrespondence\src\lcds-config\flex-config.xml
FSIApp\Portal\src\com\adobe\icc\bootstrap\URLRegistryBootstrapper.java
FSIApp\Portal\webapp\WEB-INF\web.xml
FSIApp\Portal\resources\cm.properties [add a property here 'pscmContext=/{your context}'. For e.g., pscmContext=myprojectname]
FSIApp\Portal\resources\security-config.xml
However, I would say that it is only partially possible, because there are a couple of components that rely on 'cmsa' as the URL's context root, and hence would not work if you change it.
Those are the LCM Plugin Bootstrapper (which is used to bootstrap CMSA from LCM plugin) and the ImportUtility (which is used to import an exported ACP onto a target system) . But may be you can live with that.
Cheers,
~S.
Views
Replies
Total Likes
Hi Saket,
Just an FYI - it seems that changing the pscmContext in cm.properties causes other issues, namely causing errors when trying to upload layouts in the admin interface.
Cheers,
Kristian
Views
Replies
Total Likes
Hi,
Details (error logs, etc.) on the issue when uploading would help in identifying the root cause here. Thanks!
Cheers,
~S.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies