on 11-12-2014 10:04 AM
Hi Expert,
We were setting for nakisa OrgModeler but we found error as following, during did try to start IDOC Listener.
"./startidocreceiver.sh
: command not
foundee/cluster/apps/Nakisa/OrgModeler/servlet_jsp/OrgModeler/root/idocreceivercmd.sh: line 8:
IDoc Settings file does not
exist:/XML/IDocSettings.xml/cluster/apps/Nakisa/OrgModeler/servlet_jsp/OrgModeler/root
IDoc listener failed to start due to issue(s) mentioned above.”
and we did try to check IDocSettings.xml file and it already existed in /usr/sap/HKD/J84/j2ee/cluster/apps/Nakisa/OrgModeler/servlet_jsp/OrgModeler/root/XML path.
Version Detail:
- Nakisa 4.0 SP 1 >> OrgModeler 4.0 SP1
- sapjco.jar version 2.1.10
- sapidocjco.jar version 1.0
- sapidoc.jar version 1.0
- Database details >> Oracle 11.2.0.3
- Operation system >> Linux suse 11
- SAP ERP system version >> EHP6 for SAP ERP 6.0
- Nakisa Add-on version >> 401_702_RF
And this is the parameter of startdocreceiver script.
sh /usr/sap/HKD/J84/j2ee/cluster/apps/Nakisa/OrgModeler/servlet_jsp/OrgModeler/root/idocreceivercmd.sh /usr/java/jre1.7.0_60/bin
/usr/sap/HKD/J84/j2ee/cluster/apps/Nakisa/OrgModeler/servlet_jsp/OrgModeler/root
/usr/sap/HKD/J84/j2ee/cluster/apps/Nakisa/OrgModeler/servlet_jsp/OrgModeler/root/WEB-INF/lib
/usr/sap/HKD/J84/j2ee/cluster/apps/Nakisa/OrgModeler/servlet_jsp/OrgModeler/root/WEB-INF/lib /usr/sap/HKD/J84/j2ee/cluster/apps/Nakisa/OrgModeler/servlet_jsp/OrgModeler/root/WEB-INF/lib NakisaFrameworkBin
Please kindly help to suggest us for this issue. What is missing or incorrect?
Thanks in advance.
Suppalak K.
Message was edited by: Suppalak Khantidamrongkul
Hi Suppalak,
: command not
foundee/cluster/apps/Nakisa/OrgModeler/servlet_jsp/OrgModeler/root/idocreceivercmd.sh: line 8:
IDoc Settings file does not
The above error is due to the carriage return that is interpreted differently in UNIX environment.
What you can do is run the below command for once:
dos2unix idocreceivercmd.sh
This will convert the carriage return in Unix format. After this if you try to start the listener it won't prompt for the error in Unix environment even if the line #8 is empty.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Suppalak,
Please note that once you set up the startidocreceiver file as per the given parameters, you need to validate the idocsettings.xml file for the below given parameters.
1. ImageDBConnection - Set by admin console based on the database connection configuration
2. SAP Login configuration - Set by admin console based on the SAP connection configuration
3. Receiver configuration
i. Gateway Host - Set by admin console but recommended to cross check and replace with the correct host(application server) if necessary
ii. Gateway Server - This is by default sapgw00. If your system instance number is other than 00 then replace the last two digits with your system instance.
iii. ProgramID - This is defaulted with 'NAKIDOC'. If you maintained the same program id in SM59 rfc destination connection as per deployment guide then do not change it.
iv. Unicode - Defaults to 1
4. Sender Configuration
i. Sender Port - Defaults to NAKPORT. Cross check with the port you created in WE21
ii. SenderPartnerType - Defaults to LS
iii. SenderPartnerNumber - Defaults to NAKJAVASYS. Cross check with the Logical system that you created in BD54
iv. MessageType - Defaults to HRMD_A. If you use different message type to pass your custom fields then replace with the respective message type
v. RecipientPartnerType - Defaults to LS
vi. RecipientPartnerNumber: Defaults to LS800. Replace with the distribution model system you connected to. (BD64)
vii. ActivePlanVersion: Defaults to 01. Replace with your HCM current plan version
viii. WriteBackPlanVersion : Defaults to 08. Replace with the plan version you wanted to write back the scenario objects.
After you setup all the parameters, place the idocsettings.xml file in /usr/sap/HKD/J84/j2ee/cluster/apps/Nakisa/OrgModeler/servlet_jsp/OrgModeler/root/\.system\Admin_Config\build XXX\.delta then Open your admin console and save & publish the respective build.
Thanks,
Manohar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
99 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.