on 2016 Apr 21 2:15 PM
Hi,
I was trying to integrated opentext 1.5.1 with hybris 5.5.1 but facing challenges on the final step of media assignment.
Let me give gist of our set up. We have OTMM Server installed on one server along with FTP server. Hybris 5.5.1 is running locally on my machine.
I have enabled all 3 extensions in localextensions.xml file:
<!-- Other hybris extensions -->
<extension name="otmmaddon" />
<extension name="otmmaddonui" />
<extension name="otmmaddonbackoffice" />
The local.properties file is updated with following configuration:
######################################################
# OTMM Server configuration #
######################################################
# OTMM server hostname
otmm.server.domain=10.129.49.143
# OTMM User
otmm.server.login=tsuper
# OTMM User Password
otmm.server.password=abcd
#Comma separated list of OTMM metadata models, which are
#configured #according to documentation for hybris assignment.
otmm.model.image.format.list=OPENTEXT.PRODUCTS
otmm.db.ignore.exclusive.lock=TRUE
# MediaServlet URL and password
#otmm.media.servlet.url=http://<host>:<port>/ImConvServlet/imconv
#otmm.media.servlet.pwd=<password>
#FTP Server hostname or IP (to be used if media servlet is not used)
10012=10.129.49.143
#FTP User
10013=ftpusr
#FTP User Password
10014=abcd
# Local or FTP depending on if the FTP server is locally running
# on hybris instance or not
otmm.AssetSync.SourceRepository=FTP
# Local path to FTP home folder of <ftpuser>, assumes local
# destination i.e FTP server runs on the same machine as hybris
otmm.locationOfFiles=/otmedia
The index.zul file of product cockpit is updated with following snippet:
<?script src="/../otmmaddonui/js/opentextotmmaddon.js?v=16.0.0"?>
<style src="/../otmmaddonui/css/opentextotmmaddon.css?v=16.0.0"/>
Did an ant update and post which navigating to product cockpit, product and multi-media and clicking [..], opens up OTMM server pop up where I can locate the media.
When the media is assigned and DONE is clicked it gives the following exception:
016/04/21 16:30:39.711 | ERROR [Thread-106] [ExceptionHandler] handleException(): Log ID 16:30_21/04/16_9953811: Failed to change to directory /ExportData_094_20160421_163027_0611
INFO | jvm 1 | main | 2016/04/21 16:30:39.711 | com.opentext.hybris.otmmconnector.exceptions.FtpException: [16:30_21/04/16_9953811] Failed to change to directory /ExportData_094_20160421_163027_0611
INFO | jvm 1 | main | 2016/04/21 16:30:39.711 | at com.opentext.hybris.otmmconnector.sync.ExportReaderFTP.changeDirectory(ExportReaderFTP.java:148)
INFO | jvm 1 | main | 2016/04/21 16:30:39.711 | at com.opentext.hybris.otmmconnector.sync.ExportReaderFTP.checkFiles(ExportReaderFTP.java:274)
INFO | jvm 1 | main | 2016/04/21 16:30:39.711 | at com.opentext.hybris.otmmconnector.sync.ExportReaderFTP.isReady(ExportReaderFTP.java:63)
INFO | jvm 1 | main | 2016/04/21 16:30:39.711 | at com.opentext.hybris.otmmconnector.sync.AssetSynchronizationImpl.waitForUpload(AssetSynchronizationImpl.java:450)
INFO | jvm 1 | main | 2016/04/21 16:30:39.712 | at com.opentext.hybris.otmmconnector.sync.AssetSynchronizationImpl.perform(AssetSynchronizationImpl.java:382)
INFO | jvm 1 | main | 2016/04/21 16:30:39.712 | at com.opentext.hybris.otmmconnector.service.impl.AssetAssignmentServiceImpl.runAssetSyncJob(AssetAssignmentServiceImpl.java:219)
INFO | jvm 1 | main | 2016/04/21 16:30:39.712 | at com.opentext.hybris.otmmconnector.service.impl.AssetAssignmentServiceImpl.access$0(AssetAssignmentServiceImpl.java:212)
INFO | jvm 1 | main | 2016/04/21 16:30:39.712 | at com.opentext.hybris.otmmconnector.service.impl.AssetAssignmentServiceImpl$1.execute(AssetAssignmentServiceImpl.java:334)
INFO | jvm 1 | main | 2016/04/21 16:30:39.712 | at com.opentext.hybris.otmmconnector.service.impl.AssetAssignmentServiceImpl$1.execute(AssetAssignmentServiceImpl.java:1)
INFO | jvm 1 | main | 2016/04/21 16:30:39.712 | at de.hybris.platform.servicelayer.session.impl.DefaultSessionService.executeInLocalView(DefaultSessionService.java:107)
INFO | jvm 1 | main | 2016/04/21 16:30:39.712 | at com.opentext.hybris.otmmconnector.service.impl.AssetAssignmentServiceImpl.doExportAndAssign(AssetAssignmentServiceImpl.java:330)
INFO | jvm 1 | main | 2016/04/21 16:30:39.712 | at com.opentext.hybris.otmmconnector.service.impl.AssetAssignmentServiceImpl.performSynchronousAssetAssignment(AssetAssignmentServiceImpl.java:367)
INFO | jvm 1 | main | 2016/04/21 16:30:39.712 | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
INFO | jvm 1 | main | 2016/04/21 16:30:39.713 | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
INFO | jvm 1 | main | 2016/04/21 16:30:39.713 | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
INFO | jvm 1 | main | 2016/04/21 16:30:39.713 | at java.lang.reflect.Method.invoke(Method.java:497)
INFO | jvm 1 | main | 2016/04/21 16:30:39.713 | at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
INFO | jvm 1 | main | 2016/04/21 16:30:39.713 | at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190)
INFO | jvm 1 | main | 2016/04/21 16:30:39.713 | at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
INFO | jvm 1 | main | 2016/04/21 16:30:39.713 | at org.springframework.aop.interceptor.AsyncExecutionInterceptor$1.call(AsyncExecutionInterceptor.java:110)
INFO | jvm 1 | main | 2016/04/21 16:30:39.713 | at java.util.concurrent.FutureTask.run(FutureTask.java:266)
INFO | jvm 1 | main | 2016/04/21 16:30:39.713 | at java.lang.Thread.run(Thread.java:745)
It seems an issue in export. On FTP server i am able to see some 6 images and an XML file.
Failure on the final step is now allowing to associate product image from product cockpit.
Please let me know what may be a possible miss. Thanks. Saurabh
Request clarification before answering.
Please also note that FTP export is only needed for physically replicating renditions to Hybris. Since otmmaddon extension version >= 1.5.1 new improved Media Delivery via adaptive URLs is possible which is much faster, and with latest version 16 also supports automatically pushing renditions to cloud storage if needed.
That new feature is enabled via otmm.rendering..type=MediaServlet and otmm.export.isMandatory = FALSE. You also neeed to deploy the new small footprint .war (Media Servlet) on a Tomcat instance in this case per the installation docs.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We have identified the issue is with OTMM FTP on Linux which is a bug with Open Text.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
19 | |
17 | |
3 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.