tian-zhihui / cordysscriptcon

Automatically exported from code.google.com/p/cordysscriptcon
Apache License 2.0
0 stars 0 forks source link

Unable to create ScriptConnector Service Container #6

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.Attach the ScriptConnector Application Connector to an existing Service 
container
2. Goto ScripConnector Configuration Page
3. The default values in the configuration page will be empty.
4. Provide the input values and click Save
5. Nothing will happen and the configuration will not be saved

What is the expected output? What do you see instead?
1. Successfully save the configuration 

What version of the product are you using? On what operating system?
1. BOP 4.2 CU1

Please provide any additional information below.
1. There is a javascript script error in the chrome console at line 
btnTest.hide(); in configuration.js file
with the error as
btnHide is not defined.

Once I comment this line it works fine.

Original issue reported on code.google.com by psrinivas2@cordys.com on 29 May 2013 at 11:57

GoogleCodeExporter commented 8 years ago
Hello,

The reason for script connector not starting is not because of that script 
error, its because of configuration missing in LDAP level. However your 
approach of uncommenting would work anyways but would not solve the problem. 
You must go to the LDAP explorer in that particular organization and in the 
Script container level and expand the busprocessorconfiguration look up you 
would see the configuration page in which I assume configurations would be 
missing. Hence the error. Please mentioned below is the sample configuration 
page which worked in my case. 

Sample Configuration XML:

<configurations autoStartCount="3">
  <cancelReplyInterval>30000</cancelReplyInterval>
  <gracefulCompleteTime>15</gracefulCompleteTime>
  <abortTime>5</abortTime>
  <routing ui_type="loadbalancing" ui_algorithm="failover">
    <preference>1</preference>
  </routing>
  <configuration implementation="com.cordys.coe.ac.scriptconnector.ScriptConnector" htmfile="/cordys/com-cordys-coe/scriptconnector/ui/Configuration.caf">
    <classpath>
      <location>com-cordys-coe/scriptconnector/java/classes</location>
      <location>com-cordys-coe/scriptconnector/java/scriptconnector.jar</location>
      <location>com-cordys-coe/scriptconnector/java/lib/coelib.jar</location>
      <location>com-cordys-coe/scriptconnector/java/lib/js.jar</location>
      <location>com-cordys-coe/scriptconnector/java/lib/wsdl4j.jar</location>
    </classpath>
    <configuration xmlns="http://schemas.cordys.com/2.0/scriptconnector/configuration" xmlns:tns="http://schemas.cordys.com/2.0/scriptconnector/configuration" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <configfile>com-cordys-coe/scriptconnector/java/config.properties</configfile>
      <custompropertyfile />
      <transactionsavefolder />
      <maxnumberoffiles>500</maxnumberoffiles>
      <timeout>30</timeout>
    </configuration>
  </configuration>
</configurations>

We should change in LDAP Directly:

---Another point to be mentioned is that 
"com-cordys-coe\scriptconnector\java\samples" will have all the sample 
javascript files as zipped content, we must extract for the script connector to 
start.

Original comment by kiran.jo...@darkhorseboa.com on 30 May 2013 at 9:33

GoogleCodeExporter commented 8 years ago
About this remark: ---Another point to be mentioned is that 
"com-cordys-coe\scriptconnector\java\samples" will have all the sample 
javascript files as zipped content, we must extract for the script connector to 
start.

This is because a limitation is CWS. CWS does not allow a .js file to be 
deployed to the file system. It assumes it is always web content. That is why 
there is a ZIP.

Original comment by pgus...@gmail.com on 30 May 2013 at 9:36

GoogleCodeExporter commented 8 years ago
 The root cause of the issue is that because of the script error. So I suspect that should be fixed. Because once I have commented that line, it worked for me and could able to create the connector.

Original comment by psrinivas2@cordys.com on 30 May 2013 at 9:39