JDBC - System/Application Acknowledgement

Hi,
my scenario is IDoc -> XI -> JDBC (Oracle DB)
I use a trigger on my db table. I would like to know whether the data processing on my Oracle db was successful or not. Is system acknowledgement sufficient or have I to realize it via application acknowledgement (by means of BPM or stored procedure)? Where ends system acknowledgement and where starts application acknowledgement in this case?
Thanks in advance
Christian

Hi Chritian,
you can set Integration Engine parameter RUNTIME/ACK_SYSTEM_ERROR=1 to send system acknowledgement. That can of course only control ABAP stack errors, not Java Engine of Adapter Engine of JDBC adapter. Your IDoc adapter will send ALEAUD anyway.
In my point of view is it the best way to have a BP, where you can send an error acknowledgement in case of error, a success ALEAUD other case. For IE system errors use that parameter.
For special problematic of IDOC -> JDBC and sending back acknowledgement have a look to <a href="/people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements Logical System Name for serveral BPM Acknowledgements</a>
Regards,
Udo

Similar Messages

How to send application acknowledgement from R/3 system

Hi guys,
How to send application acknowledgement from R/3 system. Ex. we have post one IDoc and check user validations. Suppose date is wrong that means indicate earlier or wrong date but date format is correct. In this situation we need send one acknowledment to sender.
How to find the solution? pls tell anyone.
Regards
Vijay

Hi Vijay,
Plz do perform the following steps:
1) In the Integration Server, call transaction SE38
2) Run program IDX_ALEREQUEST to process IDocs with message type ALEAUD as XI request
message.
3) Now Enter Sender Port, Sender Client,Partner Number, Partner Type, and Partner Rol
4) In Integration Directory, configure the routing of interface
5) Call transaction SXMB_MONI to display the XI message.
Also,
Further in IDX5 as well you will find entry for IDoc ALEAUD.ALEAUD01
Please go through the link
1)Succesful IDOC acknowledgements from ECC
2)https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
3)https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
After you triggered the IDoc by e.g. tcode: WPMA and IDoc reached FILE system, FILE receiver CC actually is only able to send acknowledgment types SystemErrorAck and AckNotSupported.
This is because:
- IDoc sender adapter requests the following acknowledgments:
SystemAckRequested="false"
SystemErrorAckRequested="true"
ApplicationAckRequested="true"
ApplicationErrorAckRequested="true"
- File receiver adapter that run on the Adapter Engine support system acknowledgments and system error acknowledgments if they are requested by the sender. These acknowledgments are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed.
If you havent suppressed acknowledgments for IDocs WP_PLU in IDX_NOALE in XI then you will get:
SystemErrorAck when message has not reached the FILE system
AckNotSupported for all others acknowledgement types
QQ) Will this IDOC Ack applicable for this scenario???
Rather not, since FILE adapter does not support any other acknowledgements then system and IDoc adapter does not request other acknowledgements then application + SystemErrorAckRequested.
In sender system your IDoc will be always in status 39 (instead of 03), when acknowledgement is turned on.
This is because:
For SystemErrorAck the corresponding ALEAUD status is 56
For AckNotSupported the corresponding ALEAUD status is 50
Both inbound 56 and 50 statuses end up in 39 for your outbound IDoc in sender system.
Q1) Will this ALEAUD Idoc contains any Message from File System????
In both cases, it will result in status 39 - IDoc is in the target system. So it does not matter.
Q2) Basically what Information will contain this IDOC Ack.
Idoc number from sender system and status 56 or 50 depends on acknowledgement type.
Q3) Do we receive any Info from the Target File System , if we implement this Ack concept??
Nothing useful.
Remember that File Receiver has no way to determine if the written file has been correctly processed by the back-end application. However, if your FILE application can read your WP_PLU message and after successful processing is able to generate any kind of message then you can acknowledge the communications but you will not be able to link original message with the acknowledgement request message.
To do that you need to configure just normal scenario (that will be your new acknowledgement scenario) FILE -> XI -> R/3. Your FILE service will send ALEUAUD Idoc to R/3 system. Your FILE application must take care to generate proper ALEAUD XML message. In order to treat ALEAUD as a request message (not standard acknowledgement) you need to run IDX_ALEREQUEST in SE38 on XI.
Q1) It means if the Idoc not reached to Target File system means we can able to get the System Error Ack to Sender SAP R/3 System. Am i Right????
Supposed you have turned off acks on XI (tcode: se38, IDX_NOALE) for your sender port/client:
You have sent the IDoc and the last status is "03 - Data passed to port OK"
You don't know whether it was even delivered to XI ...
Supposed you have turned on acks on XI (tcode: se38, IDX_NOALE) for your sender port/client.
1)
You send and IDoc and it has been delivered successfully to FILE system.
Adapter Engine creates acknowledgement type: AckNotSupported
In XI you can see Ack Status: AckRequestNotSupported (Acknowledgement not possible). Category: permanent.
XI will send ALEAUD IDoc to R/3 system: status "50 - IDoc is added"
The IDoc status in sender will be "39 - IDoc is in receiving system (ALE service)".
2)
You send and IDoc and it has not been delivered successfully to FILE system. e.g. FILE server is down.
Adapter Engine creates acknowledgement type: SystemErrorAck
In XI you can see Ack Status: Error (Acknowledgement contains system errors). Category: transient.
XI will send ALEAUD IDoc to R/3 system: status "56 - IDoc with errors is added"
The IDoc status in sender will be "39 - IDoc is in receiving system (ALE service)".
So status 39 means only that IDoc reached XI, but you don't know whether it was delivered to FILE system or not.
Q2) And one more thing is Even though we are dealing with the IDOCFile OR FileIDOC we can able to get the ACk of Type System Error Ack only. Am I Right?????
No, "Sender adapters of the Adapter Engine do not request any acknowledgements."
Q3) So the same case( Which we disscused for IDOCFile) is Applicable for FileIDOC also????
No.
Can we able to get the System Error Ack, if the File is not reached to SAP R/3( Target here)
No.
Q4) If Yes to Q3 means,Where this System Error Ack will be seen in File System side???
Do we need to do any extra settings to receive these System Error Ack at File system side??
Not relevant.
Regards,
Vinod.

Sun Java System Application Server8 can not startup (help me )

I work in an japanese compay in China. recently, my JSC can not work
who can help me
the error infomation is :
The Sun Java System Application Server could not start:
Possible reasons:
1.port conflict
2.Incorrect server configuartion
3.corrputed deployed application
my java Studio Creator version: 2004Q2 Update9
I have used this tool for three weeks , in the frist week. everything is ok.
no probroblem happened. in the second week ,sometimes my JSC can not startup, so I restarted my JSC. and it can work again. later, the same problem happened again. when I restarted my JSC , it sill does not work, so I have to restart my computer and it startup successfully,
two days later, the same problem happened again. I restarted my computer , it still did not work. so I have to change my port number in the domain.xml. sometimes it woks well, but sometimes I can't not startup.
in the third week, no matter what I do, the problem can not be solved.
some of my colleagues don't have such problem. but some of them have the same problem. when I run my project on the computer that don't have such problem , it can startup. I don't know why, just a little weird.
till now , no one in our company can tell why this problem happened.
and I believe that anybody who use JSC will encountered this error sooner or later.
who can tell me why will this problem happen? and where can I find some related imformation about this problem. thanks!!!!!!
my domain.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE domain PUBLIC "-//Sun Microsystems Inc.//DTD Application Server 8.0 Domain//EN" "http://www.sun.com/software/appserver/dtds/sun-domain_1_0.dtd">


<domain application-root="${com.sun.aas.instanceRoot}/applications" log-root="${com.sun.aas.instanceRoot}/logs">
<applications>
<j2ee-application enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-apps/MEjbApp" name="MEjbApp" object-type="system-all"/>
<j2ee-application enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-apps/__ejb_container_timer_app" name="__ejb_container_timer_app" object-type="system-all"/>
<web-module context-root="/web1" enabled="true" location="${com.sun.aas.installRoot}/lib/install/applications/adminapp/adminapp_war" name="adminapp" object-type="system-admin">

</web-module>
<web-module context-root="/asadmin" enabled="true" location="${com.sun.aas.installRoot}/lib/install/applications/admingui/adminGUI_war" name="admingui" object-type="system-admin">

</web-module>
<web-module context-root="/com_sun_web_ui" enabled="true" location="${com.sun.aas.installRoot}/lib/install/applications/com_sun_web_ui" name="com_sun_web_ui" object-type="system-admin">

</web-module>
</applications>
<resources>
<jdbc-resource enabled="true" jndi-name="jdbc/__TimerPool" object-type="system-all" pool-name="__TimerPool"/>
<jdbc-resource enabled="true" jndi-name="jdbc/PointBase" object-type="user" pool-name="PointBasePool"/>
<jdbc-connection-pool connection-validation-method="auto-commit" datasource-classname="com.pointbase.xa.xaDataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="true" max-pool-size="32" max-wait-time-in-millis="60000" name="__TimerPool" pool-resize-quantity="2" res-type="javax.sql.XADataSource" steady-pool-size="8">
<property name="DatabaseName" value="jdbc:pointbase:embedded:ejbtimer,database.home=${com.sun.aas.instanceRoot}/lib/databases"/>
<property name="User" value="pbPublic"/>
<property name="Password" value="pbPublic"/>
</jdbc-connection-pool>
<jdbc-connection-pool connection-validation-method="auto-commit" datasource-classname="com.pointbase.xa.xaDataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="true" max-pool-size="32" max-wait-time-in-millis="60000" name="PointBasePool" pool-resize-quantity="2" res-type="javax.sql.XADataSource" steady-pool-size="8">
<property name="DatabaseName" value="jdbc:pointbase:server://localhost:9092/sun-appserv-samples"/>
<property name="Password" value="pbPublic"/>
<property name="User" value="pbPublic"/>
</jdbc-connection-pool>
</resources>
<configs>
<config name="server-config">
<http-service>
<http-listener acceptor-threads="100" address="0.0.0.0" default-virtual-server="server" enabled="true" id="http-listener-1" port="28080" security-enabled="false" server-name="" xpowered-by="true">
</http-listener>
<http-listener acceptor-threads="100" address="0.0.0.0" default-virtual-server="server" enabled="true" id="http-listener-2" port="21043" security-enabled="true" server-name="" xpowered-by="true">
</http-listener>
<http-listener acceptor-threads="100" address="0.0.0.0" default-virtual-server="__asadmin" enabled="true" id="admin-listener" port="24848" security-enabled="false" server-name="" xpowered-by="true">
</http-listener>
<virtual-server hosts="sif-caicj" http-listeners="http-listener-1,http-listener-2" id="server" state="on">
<property name="docroot" value="${com.sun.aas.instanceRoot}/docroot"/>
<property name="accesslog" value="${com.sun.aas.instanceRoot}/logs/access"/>
</virtual-server>
<virtual-server default-web-module="admingui" hosts="sif-caicj" http-listeners="admin-listener" id="__asadmin" state="on">
<property name="accesslog" value="${com.sun.aas.instanceRoot}/logs/access"/>
</virtual-server>
</http-service>
<iiop-service client-authentication-required="false">
<orb max-connections="1024" message-fragment-size="1024" use-thread-pool-ids="thread-pool-1"/>
<iiop-listener address="0.0.0.0" enabled="true" id="orb-listener-1" port="23700" security-enabled="false"/>
<iiop-listener address="0.0.0.0" enabled="true" id="SSL" port="21060" security-enabled="true">
<ssl cert-nickname="s1as" client-auth-enabled="false" ssl2-enabled="false" ssl3-enabled="true" tls-enabled="true" tls-rollback-enabled="true"/>
</iiop-listener>
<iiop-listener address="0.0.0.0" enabled="true" id="SSL_MUTUALAUTH" port="21061" security-enabled="true">
<ssl cert-nickname="s1as" client-auth-enabled="true" ssl2-enabled="false" ssl3-enabled="true" tls-enabled="true" tls-rollback-enabled="true"/>
</iiop-listener>
</iiop-service>
<admin-service type="das-and-server">
<das-config admin-session-timeout-in-minutes="60" autodeploy-dir="${com.sun.aas.instanceRoot}/autodeploy" autodeploy-enabled="true" autodeploy-jsp-precompilation-enabled="false" autodeploy-polling-interval-in-seconds="2" autodeploy-verifier-enabled="false" deploy-xml-validation="full" dynamic-reload-enabled="true" dynamic-reload-poll-interval-in-seconds="2"/>
</admin-service>
<web-container/>
<ejb-container cache-idle-timeout-in-seconds="600" cache-resize-quantity="32" commit-option="B" max-cache-size="512" max-pool-size="32" pool-idle-timeout-in-seconds="600" pool-resize-quantity="8" removal-timeout-in-seconds="5400" session-store="${com.sun.aas.instanceRoot}/session-store" steady-pool-size="0" victim-selection-policy="nru"/>
<mdb-container idle-timeout-in-seconds="600" max-pool-size="32" pool-resize-quantity="8" steady-pool-size="0"/>
<jms-service init-timeout-in-seconds="60" type="LOCAL">
<jms-host admin-password="admin" admin-user-name="admin" host="sif-caicj" name="default_JMS_host" port="27676"/>
</jms-service>
<log-service alarms="false" file="${com.sun.aas.instanceRoot}/logs/server.log" log-rotation-limit-in-bytes="2000000000" log-to-console="false" use-system-logging="false">
<module-log-levels admin="INFO" classloader="INFO" cmp="INFO" cmp-container="INFO" configuration="INFO" connector="INFO" corba="INFO" deployment="INFO" ejb-container="INFO" javamail="INFO" jaxr="INFO" jaxrpc="INFO" jdo="INFO" jms="INFO" jta="INFO" jts="INFO" mdb-container="INFO" naming="INFO" resource-adapter="INFO" root="INFO" saaj="INFO" security="INFO" server="INFO" verifier="INFO" web-container="INFO"/>
</log-service>
<security-service anonymous-role="ANYONE" audit-enabled="false" audit-modules="default" default-realm="file" jacc="default">
<auth-realm classname="com.sun.enterprise.security.auth.realm.file.FileRealm" name="file">
<property name="file" value="${com.sun.aas.instanceRoot}/config/keyfile"/>
<property name="jaas-context" value="fileRealm"/>
</auth-realm>
<auth-realm classname="com.sun.enterprise.security.auth.realm.certificate.CertificateRealm" name="certificate">
</auth-realm>
<jacc-provider name="default" policy-configuration-factory-provider="com.sun.enterprise.security.provider.PolicyConfigurationFactoryImpl" policy-provider="com.sun.enterprise.security.provider.PolicyWrapper">
<property name="repository" value="${com.sun.aas.instanceRoot}/generated/policy"/>
</jacc-provider>
<audit-module classname="com.sun.enterprise.security.Audit" name="default">
<property name="auditOn" value="false"/>
</audit-module>
</security-service>
<transaction-service automatic-recovery="false" heuristic-decision="rollback" keypoint-interval="2048" retry-timeout-in-seconds="600" timeout-in-seconds="0" tx-log-dir="${com.sun.aas.instanceRoot}/logs"/>
<monitoring-service>
<module-monitoring-levels connector-connection-pool="OFF" ejb-container="OFF" http-service="OFF" jdbc-connection-pool="OFF" orb="OFF" thread-pool="OFF" transaction-service="OFF" web-container="OFF"/>
</monitoring-service>
<java-config classpath-suffix="${com.sun.aas.installRoot}/pointbase/lib/pbclient.jar${path.separator}${com.sun.aas.installRoot}/pointbase/lib/pbembedded.jar${path.separator}" debug-enabled="false" debug-options="-Xdebug -Xrunjdwp:transport=dt_shmem,server=y,suspend=n,address=creator-14848" env-classpath-ignored="true" java-home="${com.sun.aas.javaRoot}" javac-options="-g" rmic-options="-iiop -poa -alwaysgenerate -keepgenerated -g" server-classpath="${com.sun.aas.javaRoot}/lib/tools.jar${path.separator}${com.sun.aas.installRoot}/lib/install/applications/jmsra/imqjmsra.jar${path.separator}${com.sun.aas.imqLib}/jaxm-api.jar${path.separator}${com.sun.aas.imqLib}/fscontext.jar${path.separator}${com.sun.aas.antLib}/ant.jar">

<jvm-options>-client</jvm-options>
<jvm-options>-Djava.endorsed.dirs=${com.sun.aas.installRoot}/lib/endorsed</jvm-options>
<jvm-options>-Djava.security.policy=${com.sun.aas.instanceRoot}/config/server.policy</jvm-options>
<jvm-options>-Djava.security.auth.login.config=${com.sun.aas.instanceRoot}/config/login.conf</jvm-options>
<jvm-options>-Dsun.rmi.dgc.server.gcInterval=3600000</jvm-options>
<jvm-options>-Dsun.rmi.dgc.client.gcInterval=3600000</jvm-options>
<jvm-options>-Xmx512m</jvm-options>
<jvm-options>-Djavax.net.ssl.keyStore=${com.sun.aas.instanceRoot}/config/keystore.jks</jvm-options>
<jvm-options>-Djavax.net.ssl.trustStore=${com.sun.aas.instanceRoot}/config/cacerts.jks</jvm-options>
<jvm-options>-Djava.ext.dirs=${com.sun.aas.javaRoot}/jre/lib/ext${path.separator}${com.sun.aas.instanceRoot}/lib/ext</jvm-options>
<jvm-options> -Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver</jvm-options>
<jvm-options>-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar</jvm-options>
<jvm-options>-XX:NewRatio=2</jvm-options>
</java-config>
<thread-pools>
<thread-pool idle-thread-timeout-in-seconds="120" max-thread-pool-size="200" min-thread-pool-size="0" num-work-queues="1" thread-pool-id="thread-pool-1"/>
</thread-pools>
</config>

</configs>
<servers>
<server config-ref="server-config" name="server">
<application-ref enabled="true" ref="adminapp" virtual-servers="__asadmin"/>
<application-ref enabled="true" ref="admingui" virtual-servers="__asadmin"/>
<application-ref enabled="true" ref="com_sun_web_ui" virtual-servers="__asadmin"/>
<application-ref enabled="true" ref="MEjbApp" virtual-servers="server"/>
<application-ref enabled="true" ref="__ejb_container_timer_app" virtual-servers="server"/>
<resource-ref enabled="true" ref="jdbc/__TimerPool"/>
<resource-ref enabled="true" ref="jdbc/PointBase"/>
</server>
</servers>
</domain>
my server.log
I am sorry there are some japanese words in the log
�v��I: fatal
��: information
�x��:warning
�R�l�N�V��G��[�� : error happened when connecting
Starting Sun Java System Application Server Platform Edition 8.0.0_01 (build b08-fcs) ...
[#|2006-02-10T12:59:48.050+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_06] from [Sun Microsystems Inc.]|#]
[#|2006-02-10T12:59:49.206+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2006-02-10T12:59:49.394+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2006-02-10T12:59:51.628+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2006-02-10T12:59:51.659+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2006-02-10T12:59:51.738+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2006-02-10T12:59:53.910+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2006-02-10T12:59:55.519+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2006-02-10T12:59:55.707+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2006-02-10T12:59:56.394+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2006-02-10T12:59:57.019+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2006-02-10T12:59:57.769+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2006-02-10T12:59:57.769+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2006-02-10T12:59:57.816+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2006-02-10T12:59:57.957+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2006-02-10T12:59:58.113+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2006-02-10T12:59:58.113+0800|�x��|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2006-02-10T12:59:58.129+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2006-02-10T12:59:58.129+0800|��|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2006-02-10T12:59:58.129+0800|��|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2006-02-10T12:59:58.222+0800|��|sun-appserver-pe8.0.0_01|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server-PE-8.0|#]
[#|2006-02-10T13:00:01.285+0800|��|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|�A�v��P�[�V��web.xml��A�f�t�H��g��g�p�� StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2006-02-10T13:00:03.191+0800|��|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Coyote HTTP/1.1��|�[�g28080��|#]
[#|2006-02-10T13:00:03.254+0800|��|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Coyote HTTP/1.1��|�[�g 28080 ��N��|#]
[#|2006-02-10T13:00:03.348+0800|��|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Coyote HTTP/1.1��|�[�g21043��|#]
[#|2006-02-10T13:00:03.363+0800|��|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Coyote HTTP/1.1��|�[�g 21043 ��N��|#]
[#|2006-02-10T13:00:03.379+0800|��|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Coyote HTTP/1.1��|�[�g24848��|#]
[#|2006-02-10T13:00:03.379+0800|��|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Coyote HTTP/1.1��|�[�g 24848 ��N��|#]
[#|2006-02-10T13:01:04.883+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5035: Timed out after 60000 milliseconds while trying to verify if the JMS service startup succeeded.|#]
[#|2006-02-10T13:01:04.883+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5037: Check permissions of MQ instance directory E:\Sun\Creator\SunAppServer8\imq\var\instances|#]
[#|2006-02-10T13:01:04.883+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]
[#|2006-02-10T13:01:04.883+0800|�v��I|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: [C4003]: �R�l�N�V��G��[��B - ��o java.net.ConnectException: Connection refused: connect
     at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:415)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:224)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: com.sun.messaging.jms.JMSException: [C4003]: �R�l�N�V��G��[��B - ��o java.net.ConnectException: Connection refused: connect
     at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSConnectException(ExceptionHandler.java:233)
     at com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleConnectException(ExceptionHandler.java:180)
     at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:172)
     at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:97)
     at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperClient.java:50)
     at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<init>(TCPConnectionHandler.java:53)
     at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openConnection(TCPStreamHandler.java:102)
     at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnectionOld(ConnectionInitiator.java:271)
     at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:107)
     at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:92)
     at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.java:562)
     at com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandler.java:1102)
     at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:1741)
     at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:588)
     at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:274)
     at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedConnectionImpl.java:33)
     at com.sun.messaging.jmq.jmsclient.QueueConnectionImpl.<init>(QueueConnectionImpl.java:32)
     at com.sun.messaging.ConnectionFactory.createQueueConnection(ConnectionFactory.java:72)
     at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.pingProvider(JMSAdminImpl.java:734)
     at com.sun.enterprise.jms.JmsProviderLifecycle.waitForJmsProvider(JmsProviderLifecycle.java:324)
     at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:384)
     ... 7 more
Caused by: java.net.ConnectException: Connection refused: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
     at java.net.Socket.connect(Socket.java:452)
     at java.net.Socket.connect(Socket.java:402)
     at java.net.Socket.<init>(Socket.java:309)
     at java.net.Socket.<init>(Socket.java:124)
     at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:152)
     ... 25 more
|#]
[#|2006-02-10T13:01:04.883+0800|�v��I|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server Startup failed. Exiting...|#]
[#|2006-02-10T13:01:04.883+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server shutdown in progress...|#]
[#|2006-02-10T13:01:04.883+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0303: Stopping Tomcat.|#]
[#|2006-02-10T13:01:04.883+0800|��|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Stoping http11 protocol on 28080 server:type=ThreadPool,name=http28080|#]
[#|2006-02-10T13:01:04.899+0800|��|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Stoping http11 protocol on 21043 server:type=ThreadPool,name=http21043|#]
[#|2006-02-10T13:01:04.915+0800|��|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Stoping http11 protocol on 24848 server:type=ThreadPool,name=http24848|#]
[#|2006-02-10T13:01:05.008+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5051: Shutting down all J2EE applications ...|#]
[#|2006-02-10T13:01:05.008+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5122:EJB Timer Service shutdown at [2006/02/10 13:01:05]|#]
[#|2006-02-10T13:01:05.008+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5052: Application shutdown complete.|#]
[#|2006-02-10T13:01:05.008+0800|�x��|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException: MQ startup failed :[C4003]: �R�l�N�V��G��[��B - ��o java.net.ConnectException: Connection refused: connect
     at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:364)
     at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:433)
     at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:400)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:233)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2006-02-10T13:01:05.008+0800|�v��I|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server stopped due to Server startup failure.|#]
[#|2006-02-10T13:01:05.024+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=11;|sending notification to server...server|#]
[#|2006-02-10T13:01:05.024+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=11;|Server shutdown complete.|#]
Starting Sun Java System Application Server Platform Edition 8.0.0_01 (build b08-fcs) ...
[#|2006-02-10T13:01:10.743+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_06] from [Sun Microsystems Inc.]|#]
[#|2006-02-10T13:01:11.728+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2006-02-10T13:01:11.868+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2006-02-10T13:01:14.634+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2006-02-10T13:01:14.650+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2006-02-10T13:01:14.665+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2006-02-10T13:01:16.337+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2006-02-10T13:01:17.603+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2006-02-10T13:01:17.790+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2006-02-10T13:01:18.462+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2006-02-10T13:01:19.025+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2006-02-10T13:01:19.728+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2006-02-10T13:01:19.728+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2006-02-10T13:01:19.775+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2006-02-10T13:01:19.916+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2006-02-10T13:01:20.041+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2006-02-10T13:01:20.041+0800|�x��|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2006-02-10T13:01:20.041+0800|��|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2006-02-10T13:01:20.056+0800|��|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2006-02-10T13:01:20.056+0800|��|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2006-02-10T13:01:20.150+0800|��|sun-appserver-pe8.0.0_01|org.apache.catalina.c                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      &n

Hi,
Restarting the computer should have stopped the appserver.
To kill the appserver manually you can go to the command prompt
<install-dir>\Sun\Creator2\SunAppServer8\bin\asadmin.bat\stop-appserv
Thanks,
RK.

Problem in creating a JDBC System on VC7.1 portal ( CE7.1 SP3)

I have a problem in creating a JDBC System on VC7.1 portal (CE7.1 SP3)
I get the following error:
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the back-end application using the connector defined in this system object
Results
Default alias retrieved successfully
Connection failed. Make sure user mapping is set correctly and all connection properties are correct.
Could you please let me know if there are any guides on SAP Library; I was not able to find any documentation nor any threads discussing this on VC7.1
Although, I saw this thread Can Visual Composer talk to/connect to any Database?..
which says that VC7.1 can connect to SAP backend
and web services only, and there is no direct connection to the db.
Help needed please.

Hi Dharmi
Here is a quote of Dafna's post in [another thread in this forum|Re: Copy VC controls]
CE7.1.1 will be released at September 2008 for ramp-up customers.
There are many improvements and new capabilities in the new release of Visual Composer for CE7.1.1. Among the new features you can find:
The missing features from Visual Composer 7.0 (Html view, portal Eventing support (EPCM), JDBC, Undo/Redo, and more..)
Many layout & modeling improvements
Additional ALV table functionality - export to Excel, switch to chart, configure ALV behavior at design time
Integration of Visual Composer in Eclipse - additional entry point to the Visual Composer models from the NWDS. This integration provides the option to add a WD component (in case of missing functionality in Visual Composer), as a black box component to the Visual Composer model. Right-clicking the component will open the Web Dynpro perspective for creating/modifying the component.
Regards,
Shai

Error while doing connection test for a jdbc system

Hi all,
i created a JDBC system. i gave all the required information for creating it like username, passowrd, connection URL, driver class name.
i even did the user mapping. But still when i try the connetion test it is giving me an error.
the error message that is visible in the front end is like follows
<i>Test Connection with Connector - Jan 1, 1970 2:29:41 PM
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the backend application using the connector defined in this system object
Results
Retrieval of default alias successful
Connection failed. Make sure user mapping is set correctly and all connection properties are correct.</i>
when i c the log files i noticed the following log messages
<b>
#1.5#00065BF80BD800660000000000000C6C000414205F93044C#1148029181853#/System/Server#sap.com/irj#com.sap.portal.ivs.semantic.systemLandscape#Administrator#435####cf4424d0e71511da940a00065bf80bd8#D:/Triniti_Deployment_Source/infrastructure/fdt/WEB-INF/classes
fdtout.log##0#0#Warning#1#com.sap.portal.ivs.semantic.systemLandscape#Java###Failed to retrieve Password##
#1.5#00065BF80BD800660000000100000C6C000414205F93059D#1148029181853#/System/Server#sap.com/irj#com.sap.portal.ivs.semantic.systemLandscape#Administrator#435####cf4424d0e71511da940a00065bf80bd8#D:/Triniti_Deployment_Source/infrastructure/fdt/WEB-INF/classes
fdtout.log##0#0#Warning#1#com.sap.portal.ivs.semantic.systemLandscape#Java###Failed to retrieve User##
#1.5#00065BF80BD800660000000200000C6C000414205F930770#1148029181853#/System/Server#sap.com/irj#com.sap.portal.ivs.connectorService#Administrator#435####cf4424d0e71511da940a00065bf80bd8#D:/Triniti_Deployment_Source/infrastructure/fdt/WEB-INF/classes
fdtout.log##0#0#Error#1#com.sap.portal.ivs.connectorService#Java###Failed to get connection for system #1#Dummy_JDBC_System#
</b>
can any one please tell me where i am going wrong.
thanks in advance
Pavan Kumar.

Hi Pavan
i see the log file that u provide
check ur connection properties.
further also check following might help u
http://help.sap.com/saphelp_nw2004s/helpdata/en/29/acd8403e37762ae10000000a155106/frameset.htm
also look at sap note 773401
regards,
kaushal
Message was edited by: kaushal malavia

How to get detail info of application acknowledgement in BPM send step

Hello
in BPM we will send an async message to SAP backend system, we need to know if the message is successfully process or not, if not, we need to get the detail info which is returned in the acknowledgement message.
As you know in PI monitor, you can open the acknowledgement message and you can see the error texts that are sent by the SAP backend system to PI in the acknowledgement message. However seems like there is no standard way in PI BPM to get the error texts inside the acknowledgement. In the send step you can only specify that application ACK is required, if negative ACK comes in, an exception is raised and you can handle the exception in the exception branch. However there is nowhere to capture the acknowledgement message to get the detail error texts.
Anyone has good idea to get the error texts from the application acknowledgment message inside BPM/
Thanks

we need to know if the message is successfully process or not, if not, we need to get the detail info which is returned in
the acknowledgement message
One way to have the above requirement done is make the process synchronous (if RFC/ Proxy). The response message should contain the state of processing of the message inside SAP....now in the BPM make a check on the response message to see if it is a success or failure....you can apply logic like is success terminate the BPM without any alert.....if failure raise an alert/ send a mail.
Regards,
Abhishek.

Problem in starting Sun Java System Application Server

Hi,
Recently I installed SJSAS 8.1 on my machine (Windoes 2000), before that I was working on SJSAS8.0 and it was working file. But with 8.1 when I try to "Start Default Server". I get the following error on the console:
Starting Domain domain1, please wait.
Log redirected to D:\netbeans-4.1beta\SunAppServer8.1\domains\domain1\logs\server.log.
Timeout waiting for domain domain1 to go to starting state.
CLI156 Could not start the domain domain1.
Press any key to continue . . .
The contents of server.log are:
[#|2005-03-29T15:07:14.242+0530|INFO|sun-appserver-pe8.1|javax.enterprise.tools.launcher|_ThreadID=10;|
D:/Java/jdk1.5\bin\java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=D:/netbeans-4.1beta/SunAppServer8.1/domains/domain1/logs/server.log
-Djava.endorsed.dirs=D:/netbeans-4.1beta/SunAppServer8.1/lib/endorsed
-Djava.security.policy=D:/netbeans-4.1beta/SunAppServer8.1/domains/domain1/config/server.policy
-Djava.security.auth.login.config=D:/netbeans-4.1beta/SunAppServer8.1/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=D:/netbeans-4.1beta/SunAppServer8.1/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=D:/netbeans-4.1beta/SunAppServer8.1/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=D:/Java/jdk1.5/jre/lib/ext;D:/netbeans-4.1beta/SunAppServer8.1/domains/domain1/lib/ext
-Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=D:/netbeans-4.1beta/SunAppServer8.1/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=D:/netbeans-4.1beta/SunAppServer8.1/config
-Djava.library.path=D:\Java\jdk1.5\jre\bin\client;D:\netbeans-4.1beta\SunAppServer8.1\lib;D:\netbeans-4.1beta\SunAppServer8.1\lib;D:\Java\jdk1.5\bin;.;D:\WINNT\system32;D:\WINNT;D:\netbeans-4.1beta\SunAppServer8.1\lib;D:\netbeans-4.1beta\SunAppServer8.1\bin;D:\netbeans-4.1beta\SunAppServer8.1\lib;D:\netbeans-4.1beta\SunAppServer8.1\bin;D:\netbeans-4.1beta\SunAppServer8.1\bin;D:\netbeans-4.1beta\SunAppServer8.1\bin;D:\WINNT\system32;D:\WINNT;D:\WINNT\System32\Wbem;D:\Java\jdk1.5\bin;D:\netbeans-4.1beta\SunAppServer8.1\bin;
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
D:/Java/jdk1.5/lib/tools.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib/appserv-rt.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\activation.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\admin-cli.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\appserv-admin.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\appserv-cmp.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\appserv-ext.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\appserv-jstl.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\appserv-rt1.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\appserv-upgrade.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\commons-launcher.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\commons-logging.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\dom.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\j2ee-svc.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\j2ee.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\jax-qname.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\jaxr-api.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\jaxr-impl.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\jaxrpc-api.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\jaxrpc-impl.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\jmxremote.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\jmxremote_optional.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\jsf-api.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\jsf-impl.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\mail.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\relaxngDatatype.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\rmissl.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\saaj-api.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\saaj-impl.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\xalan.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\xercesImpl.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib\xsdlib.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib/install/applications/jmsra/imqjmsra.jar;D:/netbeans-4.1beta/SunAppServer8.1/imq/lib/jaxm-api.jar;D:/netbeans-4.1beta/SunAppServer8.1/imq/lib/fscontext.jar;D:/netbeans-4.1beta/SunAppServer8.1/lib/ant/lib/ant.jar;D:/netbeans-4.1beta/SunAppServer8.1/pointbase/lib/pbclient.jar;D:/netbeans-4.1beta/SunAppServer8.1/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
*** EXITING ERROR:
Can't create Java VM
I guess I have searched every possible discussion/bug database/forums on this topic but unable to find a solution, please help.
Regards
Nitin

Reply please.
Thanks in advance.
amyt

Can't deploy my app on Sun Java System Application Server Platform Edition

Hi,
I am trying to deploy me app on the Sun's app server but I get the following error:
I am using Sun Java System Application Server Platform Edition 8.2
Invalid Deployment Descriptors in archive jag-ejb.jar in deployment descriptor file META-INF/ejb-jar.xml
Line 29 Column 15 -- The content of element type "session" must match
"(description?,display-name?,small-icon?,large-icon?,ejb-name,home?,remote?,local-home?,local?,ejb-class,session-type,transaction-type,env-entry*,ejb-ref*,ejb-local-ref*,security-role-ref*,security-identity?,resource-ref*,resource-env-ref*)". "It deploys on Orion 2.02
The ejb.xml file is as follows:
<enterprise-beans>
    <session>
      <display-name>Facade stateless session bean</display-name>
      <ejb-name>ejb/PetardsFacade</ejb-name>
      <home>com.jag.petardscmsbeans.interfaces.PetardsFacadeHome</home>
      <remote>com.jag.petardscmsbeans.interfaces.PetardsFacade</remote>
      <local-home>com.jag.businesslogic.interfaces.FacadeLocalHome</local-home
      ><local>com.jag.businesslogic.interfaces.FacadeLocal</local>
      <ejb-class>com.jag.petardscmsbeans.ejb.PetardsFacadeEJB</ejb-class>
      <session-type>Stateless</session-type>
      <transaction-type>Container</transaction-type>
      <resource-ref>
        <res-ref-name>jdbc/OracleDSRES</res-ref-name>
        <res-type>javax.sql.DataSource</res-type>
        <res-auth>Container</res-auth>
      </resource-ref>
      <env-entry>
        <env-entry-name>DSName</env-entry-name>
        <env-entry-type>java.lang.String</env-entry-type>
        <env-entry-value>jdbc/OracleDSRES</env-entry-value>
      </env-entry>
    </session>
</enterprise-beans>also, in the error message what does ? and * signify?
Thanks

This is an element ordering issue. env-entry is before resource-ref in the schema so it must be declared in the same order.
--ken

FTP adapter with application acknowledgment

Hello,
I like to send a file with an FTP adapter to an "in" folder and configure a sender FTP adapter to pick up files from an "out" folder. I'd like to us a BPM and have the BPM determine if the returning file is pointing to an error and send an alert. This is my manual way to create an application acknowledgment.
So my BPM needs a Receive, Send and then another Receive step. Has anyone done this before? Or is there some good documentation on this process?
Thanks,
Matt

Some misunderstanding I guess
I was explaining to use UDF to raise alert message, say for example using this
Triggering XI Alerts from a User Defined Function
Checking file for error should be based on the business logic used by the receiver system. XI won't understand in itself that the file has error. There must be some business requirement that should be checked.
Regards,
Prateek

BPM - Application Acknowledge.

Hi guys,
Im using a SOAP sync scenario to call a sync/async bridge. Under BPM the process asynchronous can waste much time until finish. So, the web service need to maintain the connection established to waiting a response that can have a big delay and generate slowness in the service.
To prevent this situation I would like to send a response back to webservice before the request entered in BPM. If it possible, it would not have to wait that the async process finished to send a response with ok or received.
Is it possible do this like an Application acknowledge?
Thanks in advance,
Ricardo.

Hi Ricardo,
> The information that web service need is a simple
> response message with processed successfully.
To optimize in integration scenario it is not sufficient to know, what the interfaces request technically. You need to know, how the information is used in the application system. That is way I am asking for.
> My question is: Is it possible doing this using my
> s/a bridge in the same sender connection, without new
> receiver message interface and receiver soap
> adapter?
When you have a sync interface, the response is send back to the application automatically. You need not create an interface for the response.
> This response message can be sent to the web service
> directly from the s/a bridge without using a receiver
> soap adapter?
Yes.
> I just only need a response message comparable an
> http 200 ok, but instead of this I would like to use
> a message processed successfully.
>
> It can be possible?
Yes
Regards
Stefan

JDBC system to MS SQL server.

Hi.
I am trying to create a connection to a MS SQL server using a JDBC system.
I have downloaded the jar files for the MS SQL driver and created a new driver in VA under the jdbc connector service.
How do I add this driver to the JDBCFactory class (com.sapportals.connectors.database)?
When I try to add the newly created driver libary to the loader references under the Resources tab it does not save the entry.
Rodney

Hi,
To add new JDBC Drivers, check this:
http://help.sap.com/saphelp_nw2004s/helpdata/en/80/4f34c587f05048adee640f4c346417/frameset.htm
Once your JDBC driver is added you should define it:
http://help.sap.com/saphelp_nw2004s/helpdata/en/c7/641f44be9f1e4ebbe807cfbad61d44/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/b0/6e62f30cbe9e44977c78dbdc7a6b27/frameset.htm
Also follow my reply here:
Defining datasource in portal application
Regards,
Praveen Gudapati

Help with connection pool at system application server admin console 9.0

Hi,
I am trying to create a pool of oracle connections in system application server admin console, but when I ping to the server, it shows me the error: invalid oracle URL: OracleDataSource.makeURL.
I have the jar file of the driver referenced in the classpath suffix field of the path settings.
I have added all kind of combinations of additional properties, like
serverName: 172.16.9.162
databaseName: oradex07
portNumber: 1521
username: usr
password: pwd
or
url: jdbc:oracle:thin:@172.16.9.162:1521:oradex07
but it still showing me the same error

Hey, I use this code to lookup session bean deployed in glassfish.
Based on the glassfish EJB FAQ.
Properties props = new Properties();
props.setProperty("java.naming.factory.initial", "com.sun.enterprise.naming.SerialInitContextFactory");
props.setProperty("java.naming.factory.url.pkgs", "com.sun.enterprise.naming");
props.setProperty("java.naming.factory.state", "com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl");
props.setProperty("org.omg.CORBA.ORBInitialHost", "localhost");
props.setProperty("org.omg.CORBA.ORBInitialPort", "3700");
InitialContext initialContext = new InitialContext(props);
SessionBean bean = initialContext.lookup(ejbName);Cheers.

Creation of bi jdbc system in Portal.

Hi all,
i used following parameters for creating JDBC system in portal and it is working fine
Connection url= jdbc:sap:oracle://172.25.8.195:1527;sid=SAA
Driver class = com.sap.portals.jdbc.oracle.OracleDriver
But when i am trying to create system for BI JDBC using par file com.sap.portal.systems.BIUDI
and component SAP_BI_JDBC
and using the same connection url and driver class as above it is giving error.
thanks
Rajendra

Hi Mario details are
Test Connection with Connector
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the backend application using the connector defined in this system object
Results
Retrieval of default alias successful
Connection failed. Make sure user mapping is set correctly and all connection properties are correct.
Rajendra

Create JDBC System in EP

Dear All,
I am using EP 7.0 SP6.
We encountered a problem in creating a jdbc system for us to configure a jdbc stored procedure iView in EP.
Here is what we have done:
1 - In System administration> System Configuration, create a new system (from template)
2 - Select 'jdbc system'
3 - Provide the system name etc
4 - Provide the jdbc driver url etc information. The jdbc driver is already deployed on the J2EE engine via Visual administrator and tested to be ok
5 - We provided valid username/password via user mapping
However the creation fail and here the error message on EP screen:
=============================================
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the backend application using the connector defined in this system object
Results
Retrieval of default alias successful
Connection failed. Make sure user mapping is set correctly and all connection properties are correct.
================================================
Thanks.
Kelvin

Hi KL, jdbc system doesn't have any other mistery...
May be the drivers that you are using aren't the propers.
for SQL:com.sap.portals.jdbc.sqlserver.SQLServerDriver
and URL: jdbc:sap:sqlserver://servername:port;DatabaseName=PruebaPortal
for ORACLE:com.sap.portals.jdbc.oracle.OracleDriver
and URL:jdbc:sap:oracle://servername:port:1527;SID=PruebaPortal
Best Regards,
Nacho

Force an application acknowledgment for an FTP adapter

Hello,
I am using XI 3.0 and I need to find a way to create an application acknowledgment from an FTP adapter.
Here is what I need to happen:
When a PO is created in R/3 we need to send a transportation order request (TOR) to a trucking companying offsite. They will receive an XML file via FTP. Then they will process the TOR in their system and create an application acknowledgment to inform us of a success or failure. The acknowledgment will be in their "out" folder and our XI system will pull from the "out" folder every 10 minutes. When we receive the acknowledgment we need to send an alert if the acknowledgment informs us of an error or if the acknowledgment tied to a TOR does not arrive within an hour.
Right now I have:
R/3 to XI as a proxy
XI to FTP folder as a FTP adapter
The problem I'm having is trying to come up with the best way to receive an acknowledgment.
Any ideas?
Thanks,
Matt

Hi Matt
Now looking at your requirement to create a Z table in XI.
You can create a Z table. but challenge i see in implementing this is your soruce send message and wait for a response and file need to be picked in the timeout configured. Else the message itself will fail.
Here three possibilities
1. Using ABAP mapping you load the message ID in table. But holding source message for response is a challenge as well as Sync and Async bridginig is another
2. Doing an ABAP mapping and request response bean with file adapter but you need to raise alert when it fails and need to generate response in either case.
3. use of BPM. - creating a Sync - Async bridge for this and mapping/RFC to capture message ID and collect response.
Use of BPM is a proffered choice in my understanding.
Thanks
Gaurav
Edited by: Gaurav Bhargava on Dec 24, 2008 1:18 AM

JDBC - System/Application Acknowledgement

Similar Messages

Maybe you are looking for