Trouble with Application Server connection/deployment

Question

This is the output I get when testing the remote connection I set up:
C:\Program Files\JDeveloper\jdk\jre\bin\javaw.exe -Djava.protocol.handler.pkgs=HTTPClient -jar C:\Program Files\JDeveloper\jdev\lib\oc4j_remote_deploy.jar http://costanza:1810/Oc4jDcmServletAPI/ ias_admin handmodel1 listApplications F:\ora9ias
Initializing log
Servlet interface for OC4J DCM commands
Command timeout defined at 600 seconds
Executing DCM command...
Executing command listApplications F:\ora9ias UNDEFINED UNDEFINED UNDEFINED
Command = LISTAPPLICATIONS
Opening connection to Oc4jDcmServlet
Setting userName to ias_admin
Sending command to DCM servlet
HTTP response code = 200, HTTP response msg = OK
Command was successfully sent to Oc4jDcmServlet
Receiving session id from servlet to check command status
Session id = b3e9da25826746e393a2ab6e17c30b9b
Please, wait for command to finish...
Checking command status...
Setting userName to ias_admin
Setting Cookie to JSESSIONID=b3e9da25826746e393a2ab6e17c30b9b
Checking command status
HTTP response code = 500, HTTP response msg = Internal Server Error
#### HTTP response is NOT ok
Waiting for 30 seconds and trying again...
Command has not finished yet
Checking command status...
Setting userName to ias_admin
Setting Cookie to JSESSIONID=b3e9da25826746e393a2ab6e17c30b9b
Checking command status
HTTP response code = 200, HTTP response msg = OK
Command has finished
Receiving command exit value
Receiving command output
Command output:
BC4J
Closing connection to Oc4jDcmServlet
DCM command completed successfully.
Output:
BC4J
Does this look normal? When I try to then use this connection for deployment of War file I get this output:
---- Deployment started. ---- Oct 30, 2002 11:27:05 AM
Wrote WAR file to C:\Program Files\JDeveloper\jdev\mywork\Workspace1\Project1\deploy\webapp1.war
Wrote EAR file to C:\Program Files\JDeveloper\jdev\mywork\Workspace1\Project1\deploy\webapp1.ear
Invoking DCM servlet client...
C:\Program Files\JDeveloper\jdk\jre\bin\javaw.exe -Djava.protocol.handler.pkgs=HTTPClient -jar C:\Program Files\JDeveloper\jdev\lib\oc4j_remote_deploy.jar http://costanza:1810/Oc4jDcmServletAPI/ ias_admin **** redeploy F:\ora9ias C:\Program Files\JDeveloper\jdev\mywork\Workspace1\Project1\deploy\webapp1.ear webapp1 Oc4j_home
Initializing log
Servlet interface for OC4J DCM commands
Command timeout defined at 600 seconds
Executing DCM command...
Executing command redeploy F:\ora9ias C:\Program Files\JDeveloper\jdev\mywork\Workspace1\Project1\deploy\webapp1.ear webapp1 Oc4j_home
Command = INVALID_COMMAND
#### Invalid command: redeploy F:\ora9ias C:\Program Files\JDeveloper\jdev\mywork\Workspace1\Project1\deploy\webapp1.ear webapp1 Oc4j_home
Opening connection to Oc4jDcmServlet
Setting userName to ias_admin
Sending command to DCM servlet
#### Could not send command to Oc4jDcmServlet
Closing connection to Oc4jDcmServlet
#### DCM command did not complete successfully (-6)
#### HTTP return code was -6
Exit status of DCM servlet client: -6
Elapsed time for deployment: 5 seconds
#### Deployment incomplete. #### Oct 30, 2002 11:27:09 AM
Anybody know why this thing doesn't work.

Answer 1

Hi. I dont know obout CS on UNIX, on windows  CS uses port 1090 and HTTP script ContentServer/ContentServer.dll
The web page is
http://server:1090/ContentServer/ContentServer.dll?serverInfo.
It's on Windows....
Also read this Note 586895. -->
      New access paths and compatibility with Windows systems
              The "/ContentServer/ContentServer. dll" and "/Cache/CSProxyCache.dll" paths have since been established as fixed default values for the Content Server/Cache Servers for Windows.
              The module access in the Apache Web server is not restricted to actual paths for program files. Using <location> tags, you can determine any (sub)paths that are to be used to access a module. These tags are entered in the "httpd.conf" file within the relevant module configurations. You can also define the clients allowed to access this "location" within a <location> tag with an Allow/Deny clause.
              To be able to continue using the Windows paths proposed in the SAP system, these Windows paths are installed as compatibility tags.
              In addition to this, you can use the new, essentially shorter paths "/sapcs" and /sapcsc" to access the SAP Content Server and the SAP Cache Server.
              The "Modifications to httpd. conf" attachment to the installation manual contains a list of all of the access paths delivered.
Regards.. Award if helpful.
Edited by: Sergo Beradze on Mar 11, 2008 4:37 PM