OD faling for multilingual filename

Hi All,
I am currently facing problem in deploying the file with filename in Chinese character. Can you let me know is there any configuration to be set in OD server so that non english filename can be deployed.

OD Log

[LOG]ENG: 2012-03-09 04:23:51 EST GMT-05:00 Thread-46086 After SETUP, res=0
ENG: 2012-03-09 04:23:51 EST GMT-05:00 Thread-46086 exiting setup
ENG: 2012-03-09 04:23:51 EST GMT-05:00 Thread-46086 entering awaiting-dotask
ENG: 2012-03-09 04:23:51 EST GMT-05:00 Thread-46086 still waiting for 1
ENG: 2012-03-09 04:23:51 EST GMT-05:00 Thread-46086 exiting awaiting-dotask
ENG: 2012-03-09 04:23:51 EST GMT-05:00 Thread-46086 entering dotask
ENG: 2012-03-09 04:23:51 EST GMT-05:00 Thread-46086 COMPARE
LIB: 2012-03-09 04:23:51 Options: do_deletes deploy file_perm=775 dir_perm=775 date_different ignore_acls do_manifest_for_dnr ps_name= verbose_level=5
ENG: 2012-03-09 04:23:51 EST GMT-05:00 Thread-46086 After COMPARE, res=0
ENG: 2012-03-09 04:23:51 EST GMT-05:00 Thread-46086 PRECOMMIT
LIB: 2012-03-09 04:23:51 DEPLOYING - [/iwmnt/default/main/branchname/subbranch/en-US/WORKAREA/en-US] to [/content/docs/]
LIB: 2012-03-09 04:23:51 Filelist=[/apps/iw-home/servletd/temp/deploytask-filelist-38015.txt]
LIB: (3) 2012-03-09 04:23:51 (./templatedata/datatype/storyArticles/data/1331280074_?????????????) not found
LIB: 2012-03-09 04:23:51 Delete [./templatedata/datatype/storyArticles/data/1331280074_?????????????] [reason file_list] -- OK
ENG: 2012-03-09 04:23:51 EST GMT-05:00 Thread-46086 After PRECOMMIT, res=0
ENG: 2012-03-09 04:23:51 EST GMT-05:00 Thread-46086 exiting dotask
ENG: 2012-03-09 04:23:51 EST GMT-05:00 Thread-46086 entering awaiting-commit
ENG: 2012-03-09 04:23:51 EST GMT-05:00 Thread-46086 still waiting for 1
ENG: 2012-03-09 04:23:51 EST GMT-05:00 Thread-46086 exiting awaiting-commit
ENG: 2012-03-09 04:23:51 EST GMT-05:00 Thread-46086 entering commit
LIB: 2012-03-09 04:23:51 *** Proceed
LIB: 2012-03-09 04:23:51 *** fFailedCommitFromEngine 0
LIB: 2012-03-09 04:23:51 COMMITTING Transactional Deployment
LIB: 2012-03-09 04:23:51 Deploying local_directory[.] of area[/iwmnt/default/main/branchname/subbranch/en-US/WORKAREA/en-US] was UNENCRYPTED
ENG: 2012-03-09 04:23:51 EST GMT-05:00 Thread-46086 After COMMIT, res=0
ENG: 2012-03-09 04:23:51 EST GMT-05:00 Thread-46086 exiting commit
ENG: 2012-03-09 04:23:51 EST GMT-05:00 Thread-46086 entering awaiting-cleanup
ENG: 2012-03-09 04:23:51 EST GMT-05:00 Thread-46086 still waiting for 1
ENG: 2012-03-09 04:23:51 EST GMT-05:00 Result after commit 0
ENG: 2012-03-09 04:23:51 EST GMT-05:00 previousPhaseStr:commit
ENG: 2012-03-09 04:23:51 EST GMT-05:00 currentPhaseStr:awaiting-cleanup
ENG: 2012-03-09 04:23:51 EST GMT-05:00 Thread-46086 exiting awaiting-cleanup
ENG: 2012-03-09 04:23:51 EST GMT-05:00 Thread-46086 entering cleanup
LIB: 2012-03-09 04:23:51 Remote status: server-OK
LIB: 2012-03-09 04:23:51 [Fri Mar 9 04:23:51 2012] opendeploy 20120309.25857.2 root COMPLETED /iwmnt/default/main/branchname/subbranch/en-US/
WORKAREA/en-US .od_dev_staticdeploy_datatype.Dev_Web.ODserver.server TEAMSITEserver 192.168.5.111
LIB: 2012-03-09 04:23:51 [Fri Mar 9 04:23:51 2012] 20120309.25857.2 STATS DEPLOYMENT /iwmnt/default/main/branchname/subbranch/en-US/WORKAREA/en-US
-- .od_dev_staticdeploy_datatype.Dev_Web.ODserver OK
Directories deployed : 0 Files deployed : 0 Links deployed : 0
Directories failed : 0 Files failed : 0 Links failed : 0
Directories deleted : 0 Files deleted : 0 Links deleted : 0

LIB: 2012-03-09 04:23:51 File Content transferred: 0 bytes
ENG: 2012-03-09 04:23:51 EST GMT-05:00 Thread-46086 After CLEANUP, res=1
ENG: 2012-03-09 04:23:51 EST GMT-05:00 Thread-46086 exiting cleanup
ENG: 2012-03-09 04:23:51 EST GMT-05:00 Thread-46086 entering task-done
ENG: 2012-03-09 04:23:51 EST GMT-05:00 Begin getInfo request if required
ENG: 2012-03-09 04:23:51 EST GMT-05:00 Thread-46086 still waiting for 0
LIB: 2012-03-09 04:23:51 LOGFILE=[/apps/iw-home/OpenDeployNG/log/branchname/src.od_dev_staticdeploy_datatype.Dev_Web.TSserver.to.ODserver
.log]
[/LOG]

Find more posts tagged with

Comments

Adam Stoller

A number of questions come to mind looking at your post:

I'm not sure if that applies here since there's a lot lacking from the original post.Also - have you tried to do a directory-comparison deployment, just for the directory where this file exists, to see if that works? If so, you might be able to get the "proper" way to reference the file for the file list from the logs of that deployment.

Migrateduser

[QUOTE=ghoti]A number of questions come to mind looking at your post:

Q1 = Ans. Version 6.1.1.0.0 Build 64682 Interwoven 200704042 = Ans. Solaris 10 3 = How to find locale of server4 = Ans Chinese filename was testfile but actual branch is zh_CN5 = Ans. 1331280074_从美尚、健康和家居，到更多 orginal file name it is present in data folder of datatype when viewed from backend it shows ascii code 1331280074_\344\273\216\347\276\216\345\260\232\343\200\201\345\201\245\345\272\267\345\222\214\345\256\266\345\261\205\357\274\214\345\210\260\346\233\264\345\244\232we are using filelist deploymentHope info provided helps in analysing the problem better.RegardsManu

Adam Stoller

Q1 = Ans. Version 6.1.1.0.0 Build 64682 Interwoven 20070404
2 = Ans. Solaris 10
3 = How to find locale of server
4 = Ans Chinese filename was testfile but actual branch is zh_CN
5 = Ans. 1331280074_从美尚、健康和家居，到更多 orginal file name it is present in data folder of datatype when viewed from backend it shows ascii code 1331280074_\344\273\216\347\276\216\345\260\232\343\200\201\345\201\245\345\272\267\345\222\214\345\256\266\345\261\205\357\274\214\345\210\260\346\233\264\345\244\232

we are using filelist deployment

Hope info provided helps in analysing the problem better.

Regards
Manu

#3: I believe there is a command called simply locale which, if run from the shell, should provide you all the locale information for that server.

#5 - I understand that the name of the file which was created with Chinese characters represented in a non-Chineese OS will show up as control character sequences. That wasn't the question (though it could be useful information) - the question was - if the file previously existed on the target server, did it in fact get deleted (as indicated in the log data you posted)?

You will probably need to open a case with Support, but my guess is that the simple answer is that you may need to find a way to translate the desired names of the files into something that is handled by both the OS (filesystem) and the web (URLs). I, personally, have not had to deal with this issue on any of my projects to-date. It's possible that someone else (perhaps Boris?) can provide more real-world experience with regard to dealing with this issue.

Migrateduser

#3: I believe there is a command called simply locale which, if run from the shell, should provide you all the locale information for that server.
.

LANG=
LC_CTYPE="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_COLLATE="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_ALL=

#5 - I understand that the name of the file which was created with Chinese characters represented in a non-Chineese OS will show up as control character sequences. That wasn't the question (though it could be useful information) - the question was - if the file previously existed on the target server, did it in fact get deleted (as indicated in the log data you posted)?

You will probably need to open a case with Support, but my guess is that the simple answer is that you may need to find a way to translate the desired names of the files into something that is handled by both the OS (filesystem) and the web (URLs). I, personally, have not had to deal with this issue on any of my projects to-date. It's possible that someone else (perhaps Boris?) can provide more real-world experience with regard to dealing with this issue.

This is fresh file deployment so no question of file getting deleted from target server.

As far my knowledge goes now the URLs are multi linngual and can support chinese or japanese chars in URL, if the TeamSite support unicode filename creation then OD should help in file movement.

I tried looking solution in support also but no luck.

Thanks
Manu