Pinging sys in SAP
hi everybody,
i want to ping my Sap server/system in my Network thro' SAP application. . What is the Tcode. how can i do that inside SAP.
Thnx
Siva
Hi Siva
I suggest you to read <b>SAP Memory Management</b>
http://help.sap.com/saphelp_nw2004s/helpdata/en/02/96253c538111d1891b0000e8322f96/frameset.htm
it will explain how memory, swap etc being used in SAP..
Also learn about ST02,SM51 SM66 etc . But this is noting to do with your original question " Pinging sys in SAP "
Thanks
Prince Jose
Similar Messages
-
Gettin data from SAP R/3 4.7 unicode sys to SAP ERP non-unicode sys via RFC
We are trying to get data from SAP R/3 4.7 unicode sys to SAP ERP non-unicode sys via RFC. We are reading field from the database via FM and this field got converted by SAP standard Method (CL_ABAP_CONTAINER_UTILITIES=>fill_CONTAINER_C) from structure. When reading this field from ERP sys and converted back to structure using SAP standard Method the value is un-accurate, and different(blank) giving values.
How, if the data originally was a char or numeric it works fine, but not for decimal.
best regards,
Abu-QahtI have a range fields with different type of ranges, am saving these to the database by converting them to a string via the same method. I got the same problem so I tried to convert the string to xstring using function SCMS_STRING_TO_XSTRING, before send it to the other system, but the function raised an exception: CX_SY_CONVERSION_CODEPAGE
-
Useless backtrace in slime with SBCL
SBCL in arch exhibits some strange behavior. For example, typing (a) in the repl results in sldb displaying this:
The function COMMON-LISP-USER::A is undefined.
[Condition of type UNDEFINED-FUNCTION]
Restarts:
0: [RETRY] Retry SLIME REPL evaluation request.
1: [*ABORT] Return to SLIME's top level.
2: [ABORT] Abort thread (#<THREAD "repl-thread" RUNNING {1007B88063}>)
Backtrace:
0: (SB-KERNEL::UNDEFINED-FUN-ERROR-HANDLER ..)
1: (SB-KERNEL:INTERNAL-ERROR #.(SB-SYS:INT-SAP #X7FFFF4945740) #<unavailable argument>)
2: ("foreign function: #x4193AF")
In other distros (at least gentoo and debian) a complete backtrace is displayed.I have sbcl-git from AUR instsalled and get
The function COMMON-LISP-USER::A is undefined.
[Condition of type UNDEFINED-FUNCTION]
Restarts:
0: [ABORT] Exit debugger, returning to top level.
Backtrace:
0: ("undefined function")
1: (SB-INT:SIMPLE-EVAL-IN-LEXENV (A) #<NULL-LEXENV>)
2: (EVAL (A))
3: (INTERACTIVE-EVAL (A) :EVAL NIL)
4: (SB-IMPL::REPL-FUN NIL)
5: ((LAMBDA () :IN SB-IMPL::TOPLEVEL-REPL))
6: (SB-IMPL::%WITH-REBOUND-IO-SYNTAX #<CLOSURE (LAMBDA # :IN SB-IMPL::TOPLEVEL-REPL) {100665C48B}>)
7: (SB-IMPL::TOPLEVEL-REPL NIL)
8: (SB-IMPL::TOPLEVEL-INIT)
9: ((FLET #:WITHOUT-INTERRUPTS-BODY-52 :IN SAVE-LISP-AND-DIE))
10: ((LABELS SB-IMPL::RESTART-LISP :IN SAVE-LISP-AND-DIE))
and
(progn (load "/usr/share/emacs/site-lisp/slime/swank-loader.lisp" :verbose t) (funcall (read-from-string "swank-loader:init")) (funcall (read-from-string "swank:start-server") "/tmp/slime.25686"))
This is SBCL 1.1.0.36-d15afa6, an implementation of ANSI Common Lisp.
More information about SBCL is available at <http://www.sbcl.org/>.
SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses. See the CREDITS and COPYING files in the
distribution for more information.
; loading #P"/usr/share/emacs/site-lisp/slime/swank-loader.lisp"
; compiling file "/usr/share/emacs/site-lisp/slime/swank-backend.lisp" (written 11 OCT 2012 01:58:28 PM):
; file: /usr/share/emacs/site-lisp/slime/swank-backend.lisp
; in: DEFUN UTF8-ENCODE
; (<= SWANK-BACKEND::CODE 67108863)
; ==>
; SWANK-BACKEND::CODE
; note: deleting unreachable code
; (SWANK-BACKEND::UTF8-ENCODE-AUX SWANK-BACKEND::CODE SWANK-BACKEND::BUFFER
; SWANK-BACKEND::START SWANK-BACKEND::END 5)
; --> COND IF < -
; ==>
; SWANK-BACKEND::END
; note: deleting unreachable code
; --> COND IF PROGN
; ==>
; SWANK-BACKEND::START
; note: deleting unreachable code
; --> COND IF COND THE PROGN SETF SB-KERNEL:%ASET
; ==>
; SWANK-BACKEND::BUFFER
; note: deleting unreachable code
; (<= SWANK-BACKEND::CODE 2147483647)
; ==>
; SWANK-BACKEND::CODE
; note: deleting unreachable code
; (SWANK-BACKEND::UTF8-ENCODE-AUX SWANK-BACKEND::CODE SWANK-BACKEND::BUFFER
; SWANK-BACKEND::START SWANK-BACKEND::END 6)
; --> COND IF < -
; ==>
; SWANK-BACKEND::END
; note: deleting unreachable code
; --> COND IF PROGN
; ==>
; SWANK-BACKEND::START
; note: deleting unreachable code
; --> COND IF COND THE PROGN SETF SB-KERNEL:%ASET
; ==>
; SWANK-BACKEND::BUFFER
; note: deleting unreachable code
; (ERROR "Can't encode ~s (~x)" CHAR SWANK-BACKEND::CODE)
; ==>
; "Can't encode ~s (~x)"
; note: deleting unreachable code
; in: DEFINTERFACE SEND
; (SWANK-BACKEND::DEFINTERFACE SWANK-BACKEND::SEND
; (SWANK-BACKEND::THREAD SWANK-BACKEND::OBJECT)
; "Send OBJECT to thread THREAD."
; SWANK-BACKEND::OBJECT)
; --> PROGN SETF LET* LET* MULTIPLE-VALUE-BIND LET LAMBDA
; ==>
; #'(LAMBDA (SWANK-BACKEND::THREAD SWANK-BACKEND::OBJECT) SWANK-BACKEND::OBJECT)
; caught STYLE-WARNING:
; The variable THREAD is defined but never used.
; in: DEFINTERFACE FIND-REGISTERED
; (SWANK-BACKEND::DEFINTERFACE SWANK-BACKEND::FIND-REGISTERED
; (SWANK-BACKEND::NAME)
; "Find the thread that was registered for the symbol NAME.
; Return nil if the no thread was registred or if the tread is dead."
; NIL)
; --> PROGN SETF LET* LET* MULTIPLE-VALUE-BIND LET LAMBDA
; ==>
; #'(LAMBDA (SWANK-BACKEND::NAME) NIL)
; caught STYLE-WARNING:
; The variable NAME is defined but never used.
; compilation unit finished
; caught 2 STYLE-WARNING conditions
; printed 9 notes
; /home/haawda/.slime/fasl/2012-09-04/sbcl-1.1.0.36-d15afa6-linux-x86-64/swank-backend.fasl written
; compilation finished in 0:00:01.164
; loading #P"/home/haawda/.slime/fasl/2012-09-04/sbcl-1.1.0.36-d15afa6-linux-x86-64/swank-backend.fasl"
WARNING: SWANK-BACKEND also exports the following symbols:
(SWANK-BACKEND:INTERRUPT-THREAD SWANK-BACKEND:MAKE-WEAK-VALUE-HASH-TABLE
SWANK-BACKEND:BACKGROUND-SAVE-IMAGE SWANK-BACKEND:GETPID
SWANK-BACKEND:FRAME-PACKAGE SWANK-BACKEND:CURRENT-THREAD
SWANK-BACKEND:CREATE-SOCKET SWANK-BACKEND:SLDB-STEP-INTO
SWANK-BACKEND:GUESS-EXTERNAL-FORMAT SWANK-BACKEND:FORMAT-STRING-EXPAND
SWANK-BACKEND:FRAME-RESTARTABLE-P SWANK-BACKEND:ALL-THREADS
SWANK-BACKEND:WHO-REFERENCES SWANK-BACKEND:SEND
SWANK-BACKEND:FORMAT-SLDB-CONDITION SWANK-BACKEND:GDB-INITIAL-COMMANDS
SWANK-BACKEND:CALL-WITH-COMPILATION-HOOKS
SWANK-BACKEND:PREFERRED-COMMUNICATION-STYLE SWANK-BACKEND:THREAD-ID
SWANK-BACKEND:REMOVE-SIGIO-HANDLERS SWANK-BACKEND:DESCRIBE-PRIMITIVE-TYPE
SWANK-BACKEND:MAKE-OUTPUT-STREAM SWANK-BACKEND:KILL-THREAD
SWANK-BACKEND:LISP-IMPLEMENTATION-TYPE-NAME SWANK-BACKEND:CONDITION-EXTRAS
SWANK-BACKEND:COMPILER-MACROEXPAND SWANK-BACKEND:FIND-DEFINITIONS
SWANK-BACKEND:LIST-CALLERS SWANK-BACKEND:CALL-WITH-DEBUGGER-HOOK
SWANK-BACKEND:INSTALL-SIGINT-HANDLER
SWANK-BACKEND:LISP-IMPLEMENTATION-PROGRAM SWANK-BACKEND:SOCKET-FD
SWANK-BACKEND:LOCAL-PORT SWANK-BACKEND:ACTIVATE-STEPPING
SWANK-BACKEND:PROFILED-FUNCTIONS SWANK-BACKEND:RECEIVE-IF
SWANK-BACKEND:UNPROFILE-ALL SWANK-BACKEND:COMMAND-LINE-ARGS
SWANK-BACKEND:SWANK-COMPILE-FILE SWANK-BACKEND:EXEC-IMAGE
SWANK-BACKEND:SLDB-STEP-NEXT SWANK-BACKEND:SAVE-IMAGE
SWANK-BACKEND:INSTALL-DEBUGGER-GLOBALLY SWANK-BACKEND:PROFILE-PACKAGE
SWANK-BACKEND:SLDB-STEP-OUT SWANK-BACKEND:FRAME-VAR-VALUE
SWANK-BACKEND:TOGGLE-TRACE SWANK-BACKEND:INITIALIZE-MULTIPROCESSING
SWANK-BACKEND:BUFFER-FIRST-CHANGE SWANK-BACKEND:LIST-CALLEES
SWANK-BACKEND:HASH-TABLE-WEAKNESS SWANK-BACKEND:DISASSEMBLE-FRAME
SWANK-BACKEND:DEFAULT-READTABLE-ALIST SWANK-BACKEND:FILENAME-TO-PATHNAME
SWANK-BACKEND:SPAWN SWANK-BACKEND:DESCRIBE-SYMBOL-FOR-EMACS
SWANK-BACKEND:FRAME-CATCH-TAGS SWANK-BACKEND:CALL-WITH-USER-BREAK-HANDLER
SWANK-BACKEND:WHO-SETS SWANK-BACKEND:CLOSE-SOCKET
SWANK-BACKEND:SET-DEFAULT-DIRECTORY SWANK-BACKEND:CHARACTER-COMPLETION-SET
SWANK-BACKEND:FUNCTION-NAME SWANK-BACKEND:CALLS-WHO SWANK-BACKEND:MAKE-LOCK
SWANK-BACKEND:DESCRIBE-DEFINITION SWANK-BACKEND:PRINT-FRAME
SWANK-BACKEND:WAIT-FOR-INPUT SWANK-BACKEND:FIND-THREAD
SWANK-BACKEND:ADD-SIGIO-HANDLER SWANK-BACKEND:MACROEXPAND-ALL
SWANK-BACKEND:THREAD-ATTRIBUTES SWANK-BACKEND:CALL-WITH-SYNTAX-HOOKS
SWANK-BACKEND:WHO-MACROEXPANDS SWANK-BACKEND:FIND-EXTERNAL-FORMAT
SWANK-BACKEND:FRAME-CALL SWANK-BACKEND:SET-STREAM-TIMEOUT
SWANK-BACKEND:UTF8-TO-STRING SWANK-BACKEND:ARGLIST
SWANK-BACKEND:ADD-FD-HANDLER SWANK-BACKEND:SWANK-COMPILE-STRING
SWANK-BACKEND:FIND-SOURCE-LOCATION SWANK-BACKEND:SLDB-STEPPER-CONDITION-P
SWANK-BACKEND:CALL-WITH-DEBUGGING-ENVIRONMENT
SWANK-BACKEND:ACCEPT-CONNECTION SWANK-BACKEND:PATHNAME-TO-FILENAME
SWANK-BACKEND:MAKE-WEAK-KEY-HASH-TABLE SWANK-BACKEND:PROFILE
SWANK-BACKEND:MAKE-FD-STREAM SWANK-BACKEND:RESTART-FRAME
SWANK-BACKEND:MAKE-INPUT-STREAM SWANK-BACKEND:PROFILE-REPORT
SWANK-BACKEND:FIND-REGISTERED SWANK-BACKEND:VALID-FUNCTION-NAME-P
SWANK-BACKEND:WHO-BINDS SWANK-BACKEND:FRAME-LOCALS
SWANK-BACKEND:EVAL-IN-FRAME SWANK-BACKEND:EMACS-CONNECTED
SWANK-BACKEND:COMPILER-MACROEXPAND-1 SWANK-BACKEND:STRING-TO-UTF8
SWANK-BACKEND:REGISTER-THREAD SWANK-BACKEND:THREAD-STATUS
SWANK-BACKEND:CALL-WITH-LOCK-HELD SWANK-BACKEND:COMPUTE-BACKTRACE
SWANK-BACKEND:PROFILE-RESET SWANK-BACKEND:REMOVE-FD-HANDLERS
SWANK-BACKEND:SLDB-BREAK-ON-RETURN SWANK-BACKEND:EVAL-CONTEXT
SWANK-BACKEND:CODEPOINT-LENGTH SWANK-BACKEND:THREAD-NAME
SWANK-BACKEND:WHO-CALLS SWANK-BACKEND:FRAME-SOURCE-LOCATION
SWANK-BACKEND:SET-DEFAULT-INITIAL-BINDING SWANK-BACKEND:DUP
SWANK-BACKEND:SLDB-BREAK-AT-START SWANK-BACKEND:UNPROFILE
SWANK-BACKEND:RETURN-FROM-FRAME SWANK-BACKEND:DEFAULT-DIRECTORY
SWANK-BACKEND:RECEIVE SWANK-BACKEND:THREAD-ALIVE-P
SWANK-BACKEND:WHO-SPECIALIZES)
See also:
The ANSI Standard, Macro DEFPACKAGE
; compiling file "/usr/share/emacs/site-lisp/slime/swank-source-path-parser.lisp" (written 11 OCT 2012 01:58:28 PM):
; /home/haawda/.slime/fasl/2012-09-04/sbcl-1.1.0.36-d15afa6-linux-x86-64/swank-source-path-parser.fasl written
; compilation finished in 0:00:00.086
; loading #P"/home/haawda/.slime/fasl/2012-09-04/sbcl-1.1.0.36-d15afa6-linux-x86-64/swank-source-path-parser.fasl"
; compiling file "/usr/share/emacs/site-lisp/slime/swank-source-file-cache.lisp" (written 11 OCT 2012 01:58:28 PM):
; /home/haawda/.slime/fasl/2012-09-04/sbcl-1.1.0.36-d15afa6-linux-x86-64/swank-source-file-cache.fasl written
; compilation finished in 0:00:00.061
; loading #P"/home/haawda/.slime/fasl/2012-09-04/sbcl-1.1.0.36-d15afa6-linux-x86-64/swank-source-file-cache.fasl"
; compiling file "/usr/share/emacs/site-lisp/slime/swank-sbcl.lisp" (written 11 OCT 2012 01:58:28 PM):
; file: /usr/share/emacs/site-lisp/slime/swank-sbcl.lisp
; in: DEFIMPLEMENTATION FRAME-CALL
; (PPRINT-LOGICAL-BLOCK (STREAM NIL :PREFIX "(" :SUFFIX ")")
; (LET ((*PRINT-LENGTH* NIL) (*PRINT-LEVEL* NIL))
; (PRIN1 (SB-DEBUG::ENSURE-PRINTABLE-OBJECT SWANK-BACKEND::NAME) STREAM))
; (LET ((SWANK-BACKEND::ARGS
; (SB-DEBUG::ENSURE-PRINTABLE-OBJECT SWANK-BACKEND::ARGS)))
; (IF (LISTP SWANK-BACKEND::ARGS)
; (FORMAT STREAM "~{ ~_~S~}" SWANK-BACKEND::ARGS)
; (FORMAT STREAM " ~S" SWANK-BACKEND::ARGS))))
; --> LET LET SB-PRETTY::WITH-PRETTY-STREAM FLET LET IF
; --> #:WITH-PRETTY-STREAM1822
; ==>
; STREAM
; note: deleting unreachable code
; compilation unit finished
; printed 1 note
; /home/haawda/.slime/fasl/2012-09-04/sbcl-1.1.0.36-d15afa6-linux-x86-64/swank-sbcl.fasl written
; compilation finished in 0:00:01.956
; loading #P"/home/haawda/.slime/fasl/2012-09-04/sbcl-1.1.0.36-d15afa6-linux-x86-64/swank-sbcl.fasl"
STYLE-WARNING: redefining EMACS-INSPECT (#<BUILT-IN-CLASS T>) in DEFMETHOD
; compiling file "/usr/share/emacs/site-lisp/slime/swank-gray.lisp" (written 11 OCT 2012 01:58:28 PM):
; /home/haawda/.slime/fasl/2012-09-04/sbcl-1.1.0.36-d15afa6-linux-x86-64/swank-gray.fasl written
; compilation finished in 0:00:00.187
; loading #P"/home/haawda/.slime/fasl/2012-09-04/sbcl-1.1.0.36-d15afa6-linux-x86-64/swank-gray.fasl"
STYLE-WARNING:
Implicitly creating new generic function
SWANK-BACKEND::STREAM-READ-CHAR-WILL-HANG-P.
; compiling file "/usr/share/emacs/site-lisp/slime/swank-match.lisp" (written 11 OCT 2012 01:58:28 PM):
; /home/haawda/.slime/fasl/2012-09-04/sbcl-1.1.0.36-d15afa6-linux-x86-64/swank-match.fasl written
; compilation finished in 0:00:00.055
; loading #P"/home/haawda/.slime/fasl/2012-09-04/sbcl-1.1.0.36-d15afa6-linux-x86-64/swank-match.fasl"
; compiling file "/usr/share/emacs/site-lisp/slime/swank-rpc.lisp" (written 11 OCT 2012 01:58:28 PM):
; /home/haawda/.slime/fasl/2012-09-04/sbcl-1.1.0.36-d15afa6-linux-x86-64/swank-rpc.fasl written
; compilation finished in 0:00:00.211
; loading #P"/home/haawda/.slime/fasl/2012-09-04/sbcl-1.1.0.36-d15afa6-linux-x86-64/swank-rpc.fasl"
; compiling file "/usr/share/emacs/site-lisp/slime/swank.lisp" (written 11 OCT 2012 01:58:28 PM):
; file: /usr/share/emacs/site-lisp/slime/swank.lisp
; in: DEFUN THREAD-FOR-EVALUATION
; (SWANK::FIND-REPL-THREAD SWANK::CONNECTION)
; caught STYLE-WARNING:
; undefined function: FIND-REPL-THREAD
; in: DEFUN FIND-WORKER-THREAD
; (SWANK::FIND-REPL-THREAD SWANK::CONNECTION)
; caught STYLE-WARNING:
; undefined function: FIND-REPL-THREAD
; compilation unit finished
; Undefined function:
; FIND-REPL-THREAD
; caught 2 STYLE-WARNING conditions
; /home/haawda/.slime/fasl/2012-09-04/sbcl-1.1.0.36-d15afa6-linux-x86-64/swank.fasl written
; compilation finished in 0:00:03.117
; loading #P"/home/haawda/.slime/fasl/2012-09-04/sbcl-1.1.0.36-d15afa6-linux-x86-64/swank.fasl"
WARNING: SWANK also exports the following symbols:
(SWANK:QUIT-THREAD-BROWSER SWANK:OPERATOR-ARGLIST SWANK:UNDEFINE-FUNCTION
SWANK:INIT-INSPECTOR SWANK:INSPECTOR-REINSPECT
SWANK:FIND-SOURCE-LOCATION-FOR-EMACS SWANK:APROPOS-LIST-FOR-EMACS
SWANK:PPRINT-EVAL SWANK:TOGGLE-DEBUG-ON-SWANK-ERROR
SWANK:COMPILE-FILE-FOR-EMACS SWANK:DESCRIBE-FUNCTION
SWANK:INVOKE-NTH-RESTART-FOR-EMACS SWANK:PPRINT-INSPECTOR-PART SWANK:PING
SWANK:SWANK-MACROEXPAND SWANK:COMMIT-EDITED-VALUE
SWANK:INSPECTOR-TOGGLE-VERBOSE SWANK:COMPILE-STRING-FOR-EMACS
SWANK:LIST-ALL-PACKAGE-NAMES SWANK:INSPECTOR-HISTORY
SWANK:SWANK-TOGGLE-TRACE SWANK:VALUE-FOR-EDITING SWANK:INSPECTOR-NTH-PART
SWANK:DOCUMENTATION-SYMBOL SWANK:BACKTRACE SWANK:SWANK-EXPAND
SWANK:DESCRIBE-DEFINITION-FOR-EMACS SWANK:FIND-DEFINITIONS-FOR-EMACS
SWANK:INSPECTOR-RANGE SWANK:INTERACTIVE-EVAL SWANK:INSPECTOR-NEXT
SWANK:CONNECTION-INFO SWANK:DESCRIBE-INSPECTEE
SWANK:FRAME-LOCALS-AND-CATCH-TAGS SWANK:LIST-THREADS SWANK:INSPECTOR-EVAL
SWANK:SWANK-REQUIRE SWANK:START-SWANK-SERVER-IN-THREAD SWANK:SLDB-ABORT
SWANK:SDLB-PRINT-CONDITION SWANK:KILL-NTH-THREAD SWANK:SLDB-NEXT
SWANK:SET-PACKAGE SWANK:SIMPLE-BREAK SWANK:SLDB-BREAK-WITH-DEFAULT-DEBUGGER
SWANK:SWANK-EXPAND-1 SWANK:SWANK-MACROEXPAND-1 SWANK:COMPILE-FILE-IF-NEEDED
SWANK:INSPECT-NTH-PART SWANK:EVAL-AND-GRAB-OUTPUT SWANK:INSPECT-IN-FRAME
SWANK:IO-SPEED-TEST SWANK:XREFS SWANK:SIMPLE-COMPLETIONS
SWANK:FLOW-CONTROL-TEST SWANK:XREF SWANK:RE-EVALUATE-DEFVAR
SWANK:EVAL-STRING-IN-FRAME SWANK:FIND-DEFINITION-FOR-THING
SWANK:UPDATE-INDENTATION-INFORMATION SWANK:PROFILE-BY-SUBSTRING
SWANK:SLDB-CONTINUE SWANK:INSPECTOR-POP SWANK:INVOKE-NTH-RESTART
SWANK:TOGGLE-BREAK-ON-SIGNALS SWANK:SWANK-FORMAT-STRING-EXPAND
SWANK:THROW-TO-TOPLEVEL SWANK:SWANK-COMPILER-MACROEXPAND
SWANK:FRAME-PACKAGE-NAME SWANK:PPRINT-EVAL-STRING-IN-FRAME
SWANK:INTERACTIVE-EVAL-REGION SWANK:UNINTERN-SYMBOL
SWANK:COMPILE-MULTIPLE-STRINGS-FOR-EMACS SWANK:SLDB-OUT
SWANK:INSPECT-CURRENT-CONDITION SWANK:DESCRIBE-SYMBOL
SWANK:INSPECT-FRAME-VAR SWANK:MOP SWANK:TOGGLE-PROFILE-FDEFINITION
SWANK:INSPECTOR-CALL-NTH-ACTION SWANK:SLDB-DISASSEMBLE
SWANK:SWANK-COMPILER-MACROEXPAND-1 SWANK:UNTRACE-ALL SWANK:QUIT-INSPECTOR
SWANK:DISASSEMBLE-FORM SWANK:SWANK-MACROEXPAND-ALL SWANK:DEBUG-NTH-THREAD
SWANK:LOAD-FILE SWANK:SLDB-RETURN-FROM-FRAME SWANK:DEBUGGER-INFO-FOR-EMACS)
See also:
The ANSI Standard, Macro DEFPACKAGE
WARNING: These Swank interfaces are unimplemented:
(DISASSEMBLE-FRAME SLDB-BREAK-AT-START SLDB-BREAK-ON-RETURN)
; compiling file "/usr/share/emacs/site-lisp/slime/contrib/swank-util.lisp" (written 11 OCT 2012 01:58:28 PM):
; /home/haawda/.slime/fasl/2012-09-04/sbcl-1.1.0.36-d15afa6-linux-x86-64/contrib/swank-util.fasl written
; compilation finished in 0:00:00.092
; compiling file "/usr/share/emacs/site-lisp/slime/contrib/swank-repl.lisp" (written 11 OCT 2012 01:58:28 PM):
; /home/haawda/.slime/fasl/2012-09-04/sbcl-1.1.0.36-d15afa6-linux-x86-64/contrib/swank-repl.fasl written
; compilation finished in 0:00:00.187
; compiling file "/usr/share/emacs/site-lisp/slime/contrib/swank-c-p-c.lisp" (written 11 OCT 2012 01:58:28 PM):
; /home/haawda/.slime/fasl/2012-09-04/sbcl-1.1.0.36-d15afa6-linux-x86-64/contrib/swank-c-p-c.fasl written
; compilation finished in 0:00:00.173
; compiling file "/usr/share/emacs/site-lisp/slime/contrib/swank-arglists.lisp" (written 11 OCT 2012 01:58:28 PM):
; /home/haawda/.slime/fasl/2012-09-04/sbcl-1.1.0.36-d15afa6-linux-x86-64/contrib/swank-arglists.fasl written
; compilation finished in 0:00:01.288
; compiling file "/usr/share/emacs/site-lisp/slime/contrib/swank-fuzzy.lisp" (written 11 OCT 2012 01:58:28 PM):
; file: /usr/share/emacs/site-lisp/slime/contrib/swank-fuzzy.lisp
; in: DEFUN RECURSIVELY-COMPUTE-MOST-COMPLETIONS
; (LENGTH SWANK::*ALL-CHUNKS*)
; note: unable to
; optimize
; due to type uncertainty:
; The first argument is a SEQUENCE, not a (SIMPLE-ARRAY * (*)).
; note: unable to
; optimize
; due to type uncertainty:
; The first argument is a SEQUENCE, not a VECTOR.
; (INCF SWANK::SHORT-INDEX)
; --> LET* SETQ
; ==>
; (THE FIXNUM #:NEW517)
; note: doing signed word to integer coercion (cost 20), for:
; the first argument of CHECK-FIXNUM
; compilation unit finished
; printed 3 notes
; /home/haawda/.slime/fasl/2012-09-04/sbcl-1.1.0.36-d15afa6-linux-x86-64/contrib/swank-fuzzy.fasl written
; compilation finished in 0:00:00.297
; compiling file "/usr/share/emacs/site-lisp/slime/contrib/swank-fancy-inspector.lisp" (written 11 OCT 2012 01:58:28 PM):
; /home/haawda/.slime/fasl/2012-09-04/sbcl-1.1.0.36-d15afa6-linux-x86-64/contrib/swank-fancy-inspector.fasl written
; compilation finished in 0:00:00.970
; compiling file "/usr/share/emacs/site-lisp/slime/contrib/swank-presentations.lisp" (written 11 OCT 2012 01:58:28 PM):
; /home/haawda/.slime/fasl/2012-09-04/sbcl-1.1.0.36-d15afa6-linux-x86-64/contrib/swank-presentations.fasl written
; compilation finished in 0:00:00.084
; compiling file "/usr/share/emacs/site-lisp/slime/contrib/swank-presentation-streams.lisp" (written 11 OCT 2012 01:58:28 PM):
; /home/haawda/.slime/fasl/2012-09-04/sbcl-1.1.0.36-d15afa6-linux-x86-64/contrib/swank-presentation-streams.fasl written
; compilation finished in 0:00:00.086
; compiling file "/usr/share/emacs/site-lisp/slime/contrib/swank-asdf.lisp" (written 11 OCT 2012 01:58:28 PM):
; /home/haawda/.slime/fasl/2012-09-04/sbcl-1.1.0.36-d15afa6-linux-x86-64/contrib/swank-asdf.fasl written
; compilation finished in 0:00:00.126
; compiling file "/usr/share/emacs/site-lisp/slime/contrib/swank-package-fu.lisp" (written 11 OCT 2012 01:58:28 PM):
; /home/haawda/.slime/fasl/2012-09-04/sbcl-1.1.0.36-d15afa6-linux-x86-64/contrib/swank-package-fu.fasl written
; compilation finished in 0:00:00.040
; compiling file "/usr/share/emacs/site-lisp/slime/contrib/swank-hyperdoc.lisp" (written 11 OCT 2012 01:58:28 PM):
; /home/haawda/.slime/fasl/2012-09-04/sbcl-1.1.0.36-d15afa6-linux-x86-64/contrib/swank-hyperdoc.fasl written
; compilation finished in 0:00:00.113
; compiling file "/usr/share/emacs/site-lisp/slime/contrib/swank-sbcl-exts.lisp" (written 11 OCT 2012 01:58:28 PM):
; /home/haawda/.slime/fasl/2012-09-04/sbcl-1.1.0.36-d15afa6-linux-x86-64/contrib/swank-sbcl-exts.fasl written
; compilation finished in 0:00:00.044
; compiling file "/usr/share/emacs/site-lisp/slime/contrib/swank-mrepl.lisp" (written 11 OCT 2012 01:58:28 PM):
; /home/haawda/.slime/fasl/2012-09-04/sbcl-1.1.0.36-d15afa6-linux-x86-64/contrib/swank-mrepl.fasl written
; compilation finished in 0:00:00.110
;; Swank started at port: 37004.
37004
* (a)
; in: A
; (A)
; caught STYLE-WARNING:
; undefined function: A
; compilation unit finished
; Undefined function:
; A
; caught 1 STYLE-WARNING condition
I this what you meant when saying "complete backtrace"? -
Deploy java components error in NW7.4 installation
Hi Experts,
I am installing NW 7.4, i have done all the pre-installation steps but i am getting error at deploy java components.
please find the log. please help me in this it is very urgent. I need your experience.
An error occurred while processing option SAP NetWeaver 7.4 Support Release 2 > MaxDB > SAP Systems > Optional Standalone Units > Process Orchestration > Standard System > Process Integration and Orchestration Package( Last error reported by the step: Execution of Deploy Controller Runner tool '"C:\Program Files\sapinst_instdir\NW740SR2\ADA\INSTALL\STANDALONE\STD\PICP\sapjvm\sapjvm_6\bin\java.exe" -classpath "C:/Program Files/sapinst_instdir/NW740SR2/ADA/INSTALL/STANDALONE/STD/PICP/install/lib;\\PO/sapmnt/POP/SYS/global/security/lib/tools/iaik_jce.jar;\\PO/sapmnt/POP/SYS/global/security/lib/tools/iaik_jsse.jar;\\PO/sapmnt/POP/SYS/global/security/lib/tools/iaik_smime.jar;\\PO/sapmnt/POP/SYS/global/security/lib/tools/iaik_ssl.jar;\\PO/sapmnt/POP/SYS/global/security/lib/tools/w3c_http.jar;D:/usr/sap/POP/J00/j2ee/j2eeclient/sap.com~tc~exception~impl.jar;D:/usr/sap/POP/J00/j2ee/j2eeclient/sap.com~tc~je~clientlib~impl.jar;D:/usr/sap/POP/J00/j2ee/j2eeclient/sap.com~tc~logging~java~impl.jar;C:/Program Files/sapinst_instdir/NW740SR2/ADA/INSTALL/STANDALONE/STD/PICP/install/lib/tc~je~cl_deploy.jar" -Xmx256m -Ddc.api.verbose=false com.sap.engine.services.dc.api.cmd.Runner deploy -l "C:\Program Files\sapinst_instdir\NW740SR2\ADA\INSTALL\STANDALONE\STD\PICP\deploy.lst" -e stop -u lower -w safety --lcm bulk -t 14400000 --host PO --port 50004' aborts with return code 104. Error message is 'Component:BI_UDI ( sap.com) Status:Aborted Description:. SOLUTION: Check 'C:\Program Files\sapinst_instdir\NW740SR2\ADA\INSTALL\STANDALONE\STD\PICP\log\dc_log\deploy_api.0.log' and 'deploycontroller.log' for more information.). You can now:
Choose Retry to repeat the current step.
Choose Log Files to get more information about the error.
Stop the option and continue later.
Log files are written to C:\Program Files/sapinst_instdir/NW740SR2/ADA/INSTALL/STANDALONE/STD/PICP.
Regards,
Patan Thavaheer.Hi manu,
Please find the error log.
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ Info ] +++ Wait for server response +++. Deploying offline [31] seconds. Will timeout in [14,368] seconds.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50597]. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: java.io.EOFException: End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50597]
at com.sap.engine.services.rmi_p4.ClientConnection.run(ClientConnection.java:501)
at java.lang.Thread.run(Thread.java:763)
[ Error ] Could not establish connection to AS Java on [PO:50004]. End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50597]. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ Info ] +++ Wait for server response +++. Deploying offline [48] seconds. Will timeout in [14,351] seconds.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50615]. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: java.io.EOFException: End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50615]
at com.sap.engine.services.rmi_p4.ClientConnection.run(ClientConnection.java:501)
at java.lang.Thread.run(Thread.java:763)
[ Error ] Could not establish connection to AS Java on [PO:50004]. End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50615]. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ Info ] +++ Deployment of session ID [21] finished with status [Error] +++. [[ deployerId=1 ]] [[#3: 340.111 sec]] [
===== Summary - Deploy Result - Start =====
Type | Status : Count
> SCA(s)
- [Aborted] : [80]
> SDA(s)
- [Success] : [80]
- [Admitted] : [1189]
Type | Status : Id
> SCA(s)
- [Aborted] : name: 'BI_UDI', vendor: 'sap.com', name: 'COMP_BUILDT', vendor: 'sap.com', name: 'CU-BASE-JAVA', vendor: 'sap.com', name: 'CU-BASE-WD', vendor: 'sap.com', name: 'DATA-MAPPING', vendor: 'sap.com', name: 'ECM-CORE', vendor: 'sap.com', name: 'ESCONF_BUILDT', vendor: 'sap.com', name: 'ESMP_BUILDT', vendor: 'sap.com', name: 'LM-TOOLS', vendor: 'sap.com', name: 'MMR_SERVER', vendor: 'sap.com', name: 'MOIN_BUILDT', vendor: 'sap.com', name: 'NWTEC', vendor: 'sap.com', name: 'EP-BASIS', vendor: 'sap.com', name: 'SERVICE-COMP', vendor: 'sap.com', name: 'SWLIFECYCL', vendor: 'sap.com', name: 'UKMS_JAVA', vendor: 'sap.com', name: 'KM-KW_JIKS', vendor: 'sap.com', name: 'INTG_VIS', vendor: 'sap.com', name: 'SAP_XIADMIN', vendor: 'sap.com', name: 'SAP_XITOOL', vendor: 'sap.com', name: 'PI-SCP-EXT', vendor: 'sap.com', name: 'PI-SCP-BUILDT', vendor: 'sap.com', name: 'BPEM-CORE', vendor: 'sap.com', name: 'BPEM-FACADE', vendor: 'sap.com', name: 'BPEM-COLLAB', vendor: 'sap.com', name: 'BPEM-BASE', vendor: 'sap.com', name: 'BPEM-BUILDT', vendor: 'sap.com', name: 'BPEM-CONTENT', vendor: 'sap.com', name: 'BPEM-HIM', vendor: 'sap.com', name: 'BPEM-MM', vendor: 'sap.com', name: 'BPEM-MON', vendor: 'sap.com', name: 'BPEM-PP', vendor: 'sap.com', name: 'BPEM-WDUI', vendor: 'sap.com', name: 'BPEM-CUUI', vendor: 'sap.com', name: 'BRMS-BASE', vendor: 'sap.com', name: 'BRMS-BUILDT', vendor: 'sap.com', name: 'BRMS-CORE', vendor: 'sap.com', name: 'BRMS-FACADE', vendor: 'sap.com', name: 'BRMS-WDUI', vendor: 'sap.com', name: 'BRMS-MON', vendor: 'sap.com', name: 'FP-INFRA', vendor: 'sap.com', name: 'CU-BASE-WD-EXT', vendor: 'sap.com', name: 'TM-WLUI', vendor: 'sap.com', name: 'BPEM-ACC', vendor: 'sap.com', name: 'CAF-MF', vendor: 'sap.com', name: 'CAF-UI', vendor: 'sap.com', name: 'COLLAB-ADP', vendor: 'sap.com', name: 'CAF', vendor: 'sap.com', name: 'BI-BASE-S', vendor: 'sap.com', name: 'BI-BASE-B', vendor: 'sap.com', name: 'BI-BASE-E', vendor: 'sap.com', name: 'SEA-CORE', vendor: 'sap.com', name: 'SEA-FACADE', vendor: 'sap.com', name: 'SEA-UI', vendor: 'sap.com', name: 'BI-WDEXT', vendor: 'sap.com', name: 'CU-WD4VC-ADPT', vendor: 'sap.com', name: 'ECM-APPS', vendor: 'sap.com', name: 'ECM-STORE', vendor: 'sap.com', name: 'EP-ADMIN', vendor: 'sap.com', name: 'EP_BUILDT', vendor: 'sap.com', name: 'EP-CONNECTIVITY', vendor: 'sap.com', name: 'EP-MODELING', vendor: 'sap.com', name: 'EP-RUNTIME', vendor: 'sap.com', name: 'UWLJWF', vendor: 'sap.com', name: 'VCFREESTYLEKIT', vendor: 'sap.com', name: 'VCCORERT', vendor: 'sap.com', name: 'VCBASE', vendor: 'sap.com', name: 'VCKITBI', vendor: 'sap.com', name: 'VCFRAMEWORK', vendor: 'sap.com', name: 'VTP_BUILDT', vendor: 'sap.com', name: 'WDEXTENSIONS', vendor: 'sap.com', name: 'WD-FLEX', vendor: 'sap.com', name: 'ECM-ADMIN', vendor: 'sap.com', name: 'ECM-JEE-COMP', vendor: 'sap.com', name: 'SAP_XIESR', vendor: 'sap.com', name: 'SAP_XIGUILIB', vendor: 'sap.com', name: 'XI_CNT_SAP_BASIS', vendor: 'sap.com', name: 'INTG_VIS_DCJ', vendor: 'sap.com', name: 'SAP_XIAF', vendor: 'sap.com', name: 'SOAMON', vendor: 'sap.com',
> SDA(s)
- [Success] : name: 'com.sap.ip.bi.sdk.dac.connector.odbodll', vendor: 'sap.com', name: 'com.sap.glx.mapping.lib', vendor: 'sap.com', name: 'com.sap.glx.common.rt.lib', vendor: 'sap.com', name: 'tc~lm~ctc~confs~service_sda', vendor: 'sap.com', name: 'bi~mmr~dictionary', vendor: 'sap.com', name: 'bi~mmr~deployer', vendor: 'sap.com', name: 'com.sap.portal.pcm.indexingservice', vendor: 'sap.com', name: 'com.sap.netweaver.rtmf.server', vendor: 'sap.com', name: 'tc~rtmf~service', vendor: 'sap.com', name: 'com.sap.aii.sca.xi.svc', vendor: 'sap.com', name: 'com.sap.aii.sca.maas.svc', vendor: 'sap.com', name: 'tc~bpem~eventlog~ddic', vendor: 'sap.com', name: 'com.sap.glx.base.lib', vendor: 'sap.com', name: 'com.sap.glx.container.dbschema', vendor: 'sap.com', name: 'com.sap.glx.rrhandlermanager.svc', vendor: 'sap.com', name: 'com.sap.glx.repository.handler.dbschema', vendor: 'sap.com', name: 'com.sap.glx.core.svc', vendor: 'sap.com', name: 'com.sap.glx.contextcontainer.dbschema', vendor: 'sap.com', name: 'com.sap.glx.core.dbschema', vendor: 'sap.com', name: 'com.sap.glx.core.svc.facade', vendor: 'sap.com', name: 'tc~bpem~index~ddic', vendor: 'sap.com', name: 'tc~bpem~base~svc', vendor: 'sap.com', name: 'com.sap.glx.repository.dbschema', vendor: 'sap.com', name: 'tc~bpem~bl~lib', vendor: 'sap.com', name: 'tc~bpem~base~type~plib', vendor: 'sap.com', name: 'com.sap.glx.repository.ifc', vendor: 'sap.com', name: 'com.sap.glx.repository.svc', vendor: 'sap.com', name: 'tc~bpem~base~lib', vendor: 'sap.com', name: 'tc~bpem~tm~ddic', vendor: 'sap.com', name: 'tc~bpem~shared~lib', vendor: 'sap.com', name: 'tc~brms~engine~lib', vendor: 'sap.com', name: 'tc~brms~ws~svc', vendor: 'sap.com', name: 'tc~brms~repository~svc', vendor: 'sap.com', name: 'tc~brms~io~plib', vendor: 'sap.com', name: 'tc~brms~acl~plib', vendor: 'sap.com', name: 'tc~brms~ddic', vendor: 'sap.com', name: 'tc~brms~wdui~plib', vendor: 'sap.com', name: 'caf~um~relgroups~ddic', vendor: 'sap.com', name: 'tc~esi~sea~schema~ddic', vendor: 'sap.com', name: 'tc~esi~sea~service', vendor: 'sap.com', name: 'tc~esi~sea~api~lib', vendor: 'sap.com', name: 'com.sap.portal.healthChecks', vendor: 'sap.com', name: 'com.sap.portal.fpn.migration.fpnmigrationlib', vendor: 'sap.com', name: 'com.sap.portal.landscape.config', vendor: 'sap.com', name: 'tc~pp~gpal~deploylistener', vendor: 'sap.com', name: 'com.sap.portal.fpn.service', vendor: 'sap.com', name: 'com.sap.portal.smart.smartsrv', vendor: 'sap.com', name: 'com.sap.obn.migration.obnmigrationlib', vendor: 'sap.com', name: 'tc~kmc~bc.uwl~api', vendor: 'sap.com', name: 'devserver_lib', vendor: 'sap.com', name: 'vc_ds_service', vendor: 'sap.com', name: 'vc_generation', vendor: 'sap.com', name: 'ds_repository', vendor: 'sap.com', name: 'ds_environment', vendor: 'sap.com', name: 'visualcomposer_server_api', vendor: 'sap.com', name: 'SAPMetamodelFW', vendor: 'sap.com', name: 'SAPBuildPluginHandler', vendor: 'sap.com', name: 'tc~ecm~svc~deploy', vendor: 'sap.com', name: 'com.sap.aii.adapter.rfc.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.ispeak.svc', vendor: 'sap.com', name: 'com.sap.aii.af.maas.lib', vendor: 'sap.com', name: 'com.sap.aii.af.ifc.facade', vendor: 'sap.com', name: 'com.sap.aii.adapter.marketplace.lib', vendor: 'sap.com', name: 'com.sap.aii.adapter.jdbc.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.bc.svc', vendor: 'sap.com', name: 'com.sap.aii.af.int.svc.facade', vendor: 'sap.com', name: 'com.sap.aii.af.svc.facade', vendor: 'sap.com', name: 'com.sap.aii.mapping.lib.facade', vendor: 'sap.com', name: 'com.sap.aii.adapter.file.svc', vendor: 'sap.com', name: 'com.sap.aii.af.lib.facade', vendor: 'sap.com', name: 'com.sap.aii.proxy.svc.facade', vendor: 'sap.com', name: 'com.sap.aii.adapter.marketplace.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.ispeak.dbs', vendor: 'sap.com', name: 'com.sap.aii.adapter.mail.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.ws.cxf.lib', vendor: 'sap.com', name: 'com.sap.aii.proxy.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.xi.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.http.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.jms.svc', vendor: 'sap.com', name: 'com.sap.aii.af.axis.lib', vendor: 'sap.com',
- [Admitted] : name: 'com.sap.ip.bi.sdk.monitoring', vendor: 'sap.com', name: 'bi~sdk~resultset', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.checks', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.checko', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.xmla.x', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.jdbc', vendor: 'sap.com', name: 'tc~bi~sdk', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.datasource.ds', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.datasource.fields', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.java', vendor: 'sap.com', name: 'bi~sdk~core', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.datasource.sys', vendor: 'sap.com', name: 'bi~sdk~query', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.datasource.sync', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.checkj', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.xmla', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.checkx', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.odbo', vendor: 'sap.com', name: 'sc~bi_udi', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.sapq', vendor: 'sap.com', name: 'sc~comp_buildt', vendor: 'sap.com', name: 'sc~cu-base-java', vendor: 'sap.com', name: 'tc~cu~base~java~ear', vendor: 'sap.com', name: 'tc~cu~base~wd~adapter~wd2wd~ps', vendor: 'sap.com', name: 'tc~cu~base~wd~core', vendor: 'sap.com', name: 'tc~cu~base~wd~adapter~wd2wd', vendor: 'sap.com', name: 'sc~cu-base-wd', vendor: 'sap.com', name: 'tc~cu~base~wd~intapi', vendor: 'sap.com', name: 'tc~cu~base~wd~utils', vendor: 'sap.com', name: 'tc~cu~base~wd~contract~ps', vendor: 'sap.com', name: 'sc~data-mapping', vendor: 'sap.com', name: 'tc~ecm~core', vendor: 'sap.com', name: 'sc~ecm-core', vendor: 'sap.com', name: 'tc~ecm', vendor: 'sap.com', name: 'sc~esconf_buildt', vendor: 'sap.com', name: 'sc~esmp_buildt', vendor: 'sap.com', name: 'tc~archtech~browser~viewer~model', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~taskplnr', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~processviewer', vendor: 'sap.com', name: 'tc~lm~itsam~lmr~app', vendor: 'sap.com', name: 'tc~bcf~prov~ddic', vendor: 'sap.com', name: 'tc~lm~ctc~nwa~initialsetuptables', vendor: 'sap.com', name: 'tc~lm~itsam~ui~ctc~wd', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~master', vendor: 'sap.com', name: 'tc~lm~aci~engine~sapctrl~wsproxy', vendor: 'sap.com', name: 'tc~lm~aci~engine~ddic', vendor: 'sap.com', name: 'tc~slm~ui_maintain', vendor: 'sap.com', name: 'tc~archtech~browser_ume', vendor: 'sap.com', name: 'tc~slm~ui_jnet', vendor: 'sap.com', name: 'tc~lm~ctc~itsam~kpi', vendor: 'sap.com', name: 'tc~archtech~browser~viewer~defaultui', vendor: 'sap.com', name: 'tc~bcf~ws~ddic', vendor: 'sap.com', name: 'tc~lm~aci~vpm~wsproxy~sap', vendor: 'sap.com', name: 'tc~bcf~prov~wd', vendor: 'sap.com', name: 'tc~archtech~browser~viewer~compif', vendor: 'sap.com', name: 'tc~bcf~lib~ear', vendor: 'sap.com', name: 'tc~lm~itsam~ui~sys~overview~xi~wd', vendor: 'sap.com', name: 'tc~lm~aci~virtual~vmware~wsproxy', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~resource', vendor: 'sap.com', name: 'tc~bcf_xi~ear', vendor: 'sap.com', name: 'tc~archtech~sbook_wd', vendor: 'sap.com', name: 'tc~lm~ctc~nwa~other_ear', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~aclog', vendor: 'sap.com', name: 'tc~bcf~prov~ear', vendor: 'sap.com', name: 'tc~sec~sanity~jmx~sda', vendor: 'sap.com', name: 'tc~archtech~browser~viewer~locator', vendor: 'sap.com', name: 'tc~slm~ui_review', vendor: 'sap.com', name: 'tc~lm~aci~engine~csm~wsproxy', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~utils', vendor: 'sap.com', name: 'tc~archtech~browser~viewer~xmlui', vendor: 'sap.com', name: 'tc~lm~ctc~nwa~sldregisterapp', vendor: 'sap.com', name: 'sc~lm-tools', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~services', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~vpm', vendor: 'sap.com', name: 'tc~lm~ctc~confs~startup_app', vendor: 'sap.com', name: 'tc~lm~itsam~ui~overview~panel~interface', vendor: 'sap.com', name: 'tc~lm~itsam~ui~avail~panel', vendor: 'sap.com', name: 'tc~bcf~ws~ear', vendor: 'sap.com', name: 'tc~slm~ui_slm', vendor: 'sap.com', name: 'tc~lm~itsam~ui~thresholds~wd', vendor: 'sap.com', name: 'tc~lm~ctc~ccl~rep~hist~ddic', vendor: 'sap.com', name: 'tc~lm~aci~engine~archconfig', vendor: 'sap.com', name: 'tc~lm~itsam~ui~sysinfo', vendor: 'sap.com', name: 'tc~lm~aci~engine~hstctrl~wsproxy', vendor: 'sap.com', name: 'tc~lm~ctc~nwa~spc~config_ear', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~types', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~model', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~overview', vendor: 'sap.com', name: 'tc~slm~ui_navigation', vendor: 'sap.com', name: 'tc~archtech~sbook_init_j2ee', vendor: 'sap.com', name: 'tc~bcf~prov~ddic~content', vendor: 'sap.com', name: 'tc~sld~destsvc_dic', vendor: 'sap.com', name: 'tc~bizc~ws~ear', vendor: 'sap.com', name: 'tc~archtech~browser', vendor: 'sap.com', name: 'tc~archtech~sbook_j2ee', vendor: 'sap.com', name: 'tc~sec~sanity~wd', vendor: 'sap.com', name: 'tc~lm~itsam~ui~nwso~cfg~db', vendor: 'sap.com', name: 'tc~lm~itsam~ui~perf~panel', vendor: 'sap.com', name: 'tc~archtech~browser~dbschema', vendor: 'sap.com', name: 'tc~bcf~transport~ddic', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~acenable', vendor: 'sap.com', name: 'tc~lm~nzdm~crr~ui', vendor: 'sap.com', name: 'bi~mmr~mini_md_library', vendor: 'sap.com', name: 'bi~mmr~mini_mm_library', vendor: 'sap.com', name: 'bi~mmr~api', vendor: 'sap.com', name: 'bi~mmr~webToolsEAP', vendor: 'sap.com', name: 'bi~mmr~bi_library', vendor: 'sap.com', name: 'bi~mmr~bi_ear', vendor: 'sap.com', name: 'bi~mmr~mmrlib', vendor: 'sap.com', name: 'bi~mmr~reportmodel_library', vendor: 'sap.com', name: 'bi~mmr~cwm_1.0_library', vendor: 'sap.com', name: 'bi~mmr~reportmodel_ear', vendor: 'sap.com', name: 'bi~mmr~jnet', vendor: 'sap.com', name: 'bi~mmr~cwm_1.0_ear', vendor: 'sap.com', name: 'sc~mmr_server', vendor: 'sap.com', name: 'bi~mmr~mmrapplib', vendor: 'sap.com', name: 'bi~mmr~mof_1.4_library', vendor: 'sap.com', name: 'bi~mmr~amlib', vendor: 'sap.com', name: 'bi~mmr~mini_mm_ear', vendor: 'sap.com', name: 'bi~mmr~mini_md_ear', vendor: 'sap.com', name: 'bi~mmr~bi_repository', vendor: 'sap.com', name: 'bi~mmr~metamodel_library', vendor: 'sap.com', name: 'bi~mmr~mof_1.4_ear', vendor: 'sap.com', name: 'bi~mmr~ejb', vendor: 'sap.com', name: 'bi~mmr~metamodel_ear', vendor: 'sap.com', name: 'sc~moin_buildt', vendor: 'sap.com', name: 'sc~nwtec', vendor: 'sap.com', name: 'tc~di~sdic~support~wd', vendor: 'sap.com', name: 'com.sap.portal.supportability.isolde.api', vendor: 'sap.com', name: 'com.sap.portal.pcd.textrepository', vendor: 'sap.com', name: 'com.sap.portal.prt.cache', vendor: 'sap.com', name: 'com.sap.portal.htmlb', vendor: 'sap.com', name: 'tc~jpe~dbschema', vendor: 'sap.com', name: 'com.sap.portal.design.urdesigndataless', vendor: 'sap.com', name: 'com.sap.portal.pcm.admin.pcdimplservice', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.notification', vendor: 'sap.com', name: 'sc~ep-basis', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.clusterinformation', vendor: 'sap.com', name: 'com.sap.portal.runtime.application.contentconverter', vendor: 'sap.com', name: 'tc~epbc~pcd~pars~srvgl', vendor: 'sap.com', name: 'com.sap.portal.pcd.admintools.ucdadmin', vendor: 'sap.com', name: 'com.sap.portal.pcd.aclservice', vendor: 'sap.com', name: 'com.sap.portal.design.ui5designdataless', vendor: 'sap.com', name: 'com.sap.security.ume.consistencycheck', vendor: 'sap.com', name: 'com.sap.portal.pcd.admintools.configuration', vendor: 'sap.com', name: 'com.sap.portal.pcd.umwrapperservice', vendor: 'sap.com', name: 'tc~epbc~prt~apps~restricted', vendor: 'sap.com', name: 'rtmfcommunicator', vendor: 'sap.com', name: 'com.sap.portal.themes.lafservice', vendor: 'sap.com', name: 'tc~epbc~resourcerepository~api', vendor: 'sap.com', name: 'com.sap.portal.usermapping', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.hooks', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.authentication', vendor: 'sap.com', name: 'com.sap.portal.pcd.softcacheservice', vendor: 'sap.com', name: 'com.sap.portal.pcm.metadata.service', vendor: 'sap.com', name: 'tc~epbc~pcm~pcmadminimplsrv', vendor: 'sap.com', name: 'com.sap.portal.design.vc5designdataless', vendor: 'sap.com', name: 'com.sap.portal.pcd.basicrolefactory', vendor: 'sap.com', name: 'tc~supportplatform~wd', vendor: 'sap.com', name: 'com.sap.portal.design.portaldesigndata', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.prtconnection', vendor: 'sap.com', name: 'com.sap.portal.runtime.prtws', vendor: 'sap.com', name: 'com.sap.portal.resourcerepository', vendor: 'sap.com', name: 'com.sap.portal.pcd.lockservice', vendor: 'sap.com', name: 'irj', vendor: 'sap.com', name: 'tc~epbc~prt~apps', vendor: 'sap.com', name: 'com.sap.portal.runtime.application.xsltransform', vendor: 'sap.com', name: 'com.sap.portal.pcd.traceservice', vendor: 'sap.com', name: 'tc~epbc~pcm~ext', vendor: 'sap.com', name: 'com.sap.portal.design.portaldesigndataless', vendor: 'sap.com', name: 'tc~rtmf~wdtestapp', vendor: 'sap.com', name: 'com.sap.portal.pcd.basictransport', vendor: 'sap.com', name: 'com.sap.portal.pcd.glservice', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.idcounters', vendor: 'sap.com', name: 'com.sap.portal.design.urdesigndata', vendor: 'sap.com', name: 'com.sap.portal.usermanagement.admin', vendor: 'sap.com', name: 'tc~epbc~ume~ep5~deprecated', vendor: 'sap.com', name: 'tc~jpe~engine', vendor: 'sap.com', name: 'tc~epbc~pcd~pars~restricted', vendor: 'sap.com', name: 'tc~ep~useragent~api', vendor: 'sap.com', name: 'com.sap.portal.runtime.gwtintegration', vendor: 'sap.com', name: 'tc~bc~jpe~engine~api', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.connection', vendor: 'sap.com', name: 'com.sap.portal.usermanagement', vendor: 'sap.com', name: 'com.sap.portal.pcd.configservice', vendor: 'sap.com', name: 'com.sap.portal.runtime.application.soap', vendor: 'sap.com', name: 'pcm_ext_libSDA', vendor: 'sap.com', name: 'com.sap.portal.runtime.application.document', vendor: 'sap.com', -
Hello Gurus,
I want the details like....In production support what are the our usual works(roles), and what we have to do.
If we are getting tickets, in which manner we have to respond for those tickets.
What are the exact daily works in a production support project. And what are the exact daily works in a implementation project.
What are the t-codes we have to be perfect in support and implementation.
Please help me
Thanks and Regards
Kumar.Hi,
It may vary in different projects.
I can just give you a couple of general roles.
Migration project
Designing mapping documents in order to check the need of creation in BW.
Developing various objects like Cubes, ODS, Info Sources, InfoObjects etc.
Designing Transfer Rules and update rules including start routines, update routines and Transfer routines as per the requirement.
Scheduling Info Packages to carry out the data loading process. Involved in data loading from SAP R/3 to Source layer ODSs into BW. Loaded data using Data mart, as the Business layer and Report layer ODSs get loaded from source layer ODSs using data mart functionality of BW.
Involve in the backfilling of historical data from present sys to SAP BW .
Developing the Master/Transactional data process chains considering the dependency among the BW objects and automated the triggering and monitoring of the same on daily, weekly and monthly basis.
Transportation of various BW components.
Performing unit testing and data validation of newly developed and enhanced objects in Quality BW system in terms of providing an efficient solution.
Responsible for overseeing the Quality procedures related to the project.
Responsible to deliver (Transport into Prod) the object as per the scheduled deadlines; with accuracy of deliverables by considering the quality norms.
Involving in the Client/Onsite communication for any client side clarifications, for assignment of work, for discussing on project status related issues, etc.
Support project
Data Load Monitoring:
1.Carried out data load on a daily, weekly and monthly basis using Process chains from both SAP Source systems as well as Non-SAP Source systems such as Informatica.
2.Resolving Data load error such as Invalid characters, Time period conversion, Currency conversion, Duplicate records, etc
3.Ensuring the availability of the updated data in the datatarget on time.
4.Spooling out data through Infospoke from SAP BW to systems like Trillium, Ariba (Reporting Tool)
Ticket Resolution:
1.Process chain modification: Working on Optimizing Process chain by creating new process chain considering the load dependencies.
2.Reloading of R/3 data from different clusters Reconciliation issues
3.Enhancements as per Business requirement.
Additional responsibilities:
Preparing design documents from the Business Requirement docs and identified the relevant data targets for satisfying the customer requirements.
Creation of Operational manual: BW Run & Maintain Support.
Process Chain Detail Documentation (Sequencing & Dependency within Local Chains).
Monitoring checklist Document (From Process Chain Perspective)
BW Doc checklist preparation
Table space activity with basis team.
Data load analysis taking into account the CPU utilization.
Applying Support packs and performing ORT.
Most projects have different number of cubes with varying volume of data. You cant generalize this.
hope this helps,
Refer
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/08f1b622-0c01-0010-618c-cb41e12c72be
Roles & Responsibilities for Junior & Senior consultants(Technical)
Thanks,
JituK -
Hi,
I am trying to send an invoice idoc from an external system to R/3 using XI and want to get the status of the idoc using ALEAUD.
This is my scenario:
External system -> XI -> R/3(Invoice Idoc)
R/3 -> XI -> External system (ALEAUD Idoc)
I am able to send the IDOC to R/3 but when I send the ALEAUDIT idoc from R/3, it is received in XI and then I get an error in the technical routing of the response.
This is the error that i see in the trace:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!-- Technical Routing of Response -->
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_ALEAUDIT</SAP:Code>
<SAP:P1>51</SAP:P1>
<SAP:P2>SAPEA066</SAP:P2>
<SAP:P3/>
<SAP:P4/>
<SAP:AdditionalText>Messages from IDoc processing can be found in application log</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace=""/>
<SAP:Stack>ALEAUDIT: 51 SAPEA066 </SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have defined the receiver determination for R/3 -> External system for ALEAUD idoc.
Can anyone throw some light on this issue?
TIA
ASHOK SHi,
We had the same problem and we opened a service call for it.
The Ack is for SAP environment end to end.
It works only if you do it R/3 -> XI -> R/3.
BPM cannot handle the ack since it's a part of an automatic mechanism you cannot interfere with.
If the Ext. sys. is SAP R/3 you need to add a user exit in the ALEAUD for it to work.
control_out = control_in.
CASE control_out-mestyp.
WHEN 'ALEAUD'.
CASE control_out-sndpor.
WHEN 'Sender SAP Name'.
control_out-sndpor = 'XI name as configured in the Sender SAP'
END CASE.
END CASE.
The other way to handle it is to create your own ALEAUD as Francisco described
Cheers and good luck -
RFC error when sending logon data
Hi;
We cannot configure the STMS of our development system. When we try to
configure it, system gives an error message: Errors during distribution
of tp configuration; TMS Alert Viewers tells us
RFC_COMMUNICATION_FAILURE: RFC communications error with
system/destination TMSADM-FKT.DOMAIN_FKT RFC error when sending logon
data and READ_PROFILE_FAILED:File
erptest\sapmnt\trans\bin\TPPARAM
could not be opened for reading (No such file or directory).
Is there any advise for solution?
Best regards
Noyan
PS: Please find the profiles below:
START:
#.* Start profile START_DVEBMGS00_erptest *
#.* Version = 000006 *
#.* Generated by user = BASIS *
#.* Generated on = 30.12.2010 , 15:40:55 *
generated by R3SETUP
SAPSYSTEMNAME = FKT
INSTANCE_NAME = DVEBMGS00
SAPSYSTEM = 00
SAPGLOBALHOST = erptest
DIR_PROFILE = D:\usr\sap\FKT\SYS\profile
start database
#_DB = strdbs.cmd
#Start_Program_02 = immediate $(DIR_EXECUTABLE)\$(_DB) FKT
start message server
#_MS = msg_server.exe
Start_Program_03 = local $(DIR_EXECUTABLE)\$(_MS) pf=$(DIR_PROFILE)\FKT_DVEBMGS00_erptest
Start IGS
Start_Program_05 = local $(DIR_EXECUTABLE)$(DIR_SEP)igswd$(FT_EXE) -mode=profile pf=$(DIR_PROFILE)$(DIR_SEP)FKT_DVEBMGS00_erptest
start application server
#_DW = disp+work.exe
#Start_Program_04 = local $(DIR_EXECUTABLE)\$(_DW) pf=$(DIR_PROFILE)\FKT_DVEBMGS
General parameters for starting the system
#parameter created by: BASIS 24.12.2007 23:53:27
#SAPSYSTEM = 00
#parameter created by: BASIS 24.12.2007 23:53:27
#SAPSYSTEMNAME = FKT
#parameter created by: BASIS 24.12.2007 23:53:27
#INSTANCE_NAME = DVEBMGS00
#parameter created by: BASIS 24.12.2007 23:53:27
DIR_PROFILE = D:\usr\sap\FKT\SYS\profile
#parameter created by: BASIS 24.12.2007 23:53:27
#SAPGLOBALHOST = erptest
Start database
#parameter created by: BASIS 24.12.2007 23:53:27
_DB = strdbs.cmd
#parameter created by: BASIS 24.12.2007 23:53:27
Start_Program_01 = immediate $(DIR_EXECUTABLE)\$(_DB) $(SAPSYSTEMNAME)
Start message server
#parameter created by: BASIS 24.12.2007 23:53:27
MS = msgserver.exe
#parameter created by: BASIS 24.12.2007 23:53:27
Start_Program_02 = local $(DIR_EXECUTABLE)\$(_MS) pf=$(DIR_PROFILE)\FKT_DVEBMGS00_erptest
Start applications server
#parameter created by: BASIS 24.12.2007 23:53:27
_DW = disp+work.exe
#parameter created by: BASIS 24.12.2007 23:53:27
Start_Program_03 = local $(DIR_EXECUTABLE)\$(_DW) pf=$(DIR_PROFILE)\FKT_DVEBMGS00_erptest
DEFAULT:
SAPDBHOST = ERPTEST
dbms/type = mss
dbs/mss/server = ERPTEST
dbs/mss/dbname = FKT
dbs/mss/schema = fkt
SAPSYSTEMNAME = FKT
SAPGLOBALHOST = erptest
SAPFQDN = tr.delta.is
SAPLOCALHOSTFULL = $(SAPLOCALHOST).$(SAPFQDN)
SAPDBHOST = erptest
SAPTRANSHOST = erptest
DIR_TRANS =
$(SAPTRANSHOST)\sapmnt\trans
#DIR_TRANS = D:\usr\sap\trans
DIR_PROFILE = D:\usr\sap\FKT\SYS\profile
SAP Message Server for ABAP
rdisp/mshost = erptest
rdisp/sna_gateway = erptest
rdisp/sna_gw_service = sapgw00
rdisp/vbname = erptest_FKT_00
rdisp/enqname = erptest_FKT_00
rdisp/btcname = erptest_FKT_00
rdisp/msserv = sapmsFKT
rdisp/msserv_internal = 3900
rdisp/bufrefmode = sendoff,exeauto
login/system_client = 200
#GUVENLIK PARAMETRELERI
login/password_expiration_time = 90
login/min_password_lng = 6
#parameter created by: BASIS 25.03.2004 08:41:25
rdisp/gui_auto_logout = 10800
#parameter created by: BASIS 25.03.2004 08:37:47
#old_value: 3 changed: BASIS 25.03.2004 08:42:38
login/fails_to_user_lock = 6
#validasyon geregi, g#venligi artirma ama#i - check active but no check for SRF
#parameter created by: BASIS 16.06.2007 17:35:41
#old_value: 2
#changed: BASIS 14.05.2008 15:24:55
auth/rfc_authority_check = 1
#otomatik unlocki iptal eder
#parameter created by: BASIS 10.11.2006 17:47:15
login/failed_user_auto_unlock = 0
#AUDIT PARAMETRELER?
#old_value: changed: BASIS 20.04.2005 17:13:37
rsau/max_diskspace/per_day = 1996800000
#old_value: 1000000000 changed: BASIS 20.04.2005 17:17:01
#old_value: 0 changed: BASIS 20.04.2005 17:19:12
rsau/max_diskspace/local = 2048000000
#old_value: 2000000000 changed: BASIS 28.03.2005 23:17:11
#old_value: 2 changed: BASIS 29.03.2005 12:09:14
#old_value: 0 changed: BASIS 20.04.2005 17:13:37
rsau/max_diskspace/per_file = 665600000
rsau/enable = 1
rsau/local/file = D:\usr\sap\FKT\DVEBMGS00\log\++++++++######..AUD
rsau/selection_slots = 12
#rec/client = ALL
DIR_AUDIT = D:\usr\sap\FKT\DVEBMGS00\log
FN_AUDIT = ++++++++######..AUD
#DIL PARAMETRELERI
#Turkish codepage settings
abap/import_char_conversion = 0
install/codepage/db/non_transp = 1610
install/codepage/db/transp = 1610
zcsa/installed_languages = DET
#zcsa/system_language = E
zcsa/system_language = T
zcsa/second_language = E
install/codepage/appl_server = 1610
#OS dependent
abap/locale_ctype = Turkish_turkey.28599
#DIR_PUT = D:\usr\sap\FKQ\upg\abap
*** UPGRADE EXTENSIONS (RELEASE "701") ***
#rdisp/msserv_internal = 3900
#system/type = ABAP
INSTANCE:
SAPSYSTEMNAME = FKT
SAPGLOBALHOST = erptest
SAPSYSTEM = 00
INSTANCE_NAME = DVEBMGS00
DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64
DIR_EXECUTABLE = $(DIR_INSTANCE)\exe
icm/server_port_0 = PROT=HTTP,PORT=80$$
SAP Message Server parameters are set in the DEFAULT.PFL
ms/server_port_0 = PROT=HTTP,PORT=81$$
#rdisp/wp_no_dia = 10
#rdisp/wp_no_btc = 3
#rdisp/wp_no_enq = 1
#rdisp/wp_no_vb = 1
#rdisp/wp_no_vb2 = 1
#disp/wp_no_spo = 1
rdisp/wp_no_dia = 12
rdisp/wp_no_vb = 3
rdisp/wp_no_vb2 = 0
rdisp/wp_no_enq = 1
rdisp/wp_no_btc = 3
rdisp/wp_no_spo = 1
#PERFORMANS PARAMETRELERI
#parameter created by: SAP* 08.08.2001 10:30:18
abap/fieldexit = yes
#parameter created by: ALPER 13.10.2000 18:24:16
install/collate/active = 1
rdisp/max_wprun_time = 25000
MEMORY_NO_MORE_PAGING dump nedeniyle
#parameter created by: BASIS 27.12.2006 17:00:22
rdisp/PG_MAXFS = 262144
abap/heap_area_nondia = 2000000000
rdisp/PG_SHM = 16384
rdisp/ROLL_SHM = 32768
#'STORAGE_PARAMETERS_WRONG_SET' or 'TSV_TNEW_PAGE_ALLOC_FAILED'
#Note 552209 - Maximum memory utilization for processes on NT/Win2000
#parameter created by: BASIS 30.10.2007 10:57:24
#abap/heap_area_nondia = 50000
#parameter created by: BASIS 30.10.2007 10:58:54
#rdisp/PG_SHM = 0
#parameter created by: BASIS 30.10.2007 10:58:27
#rdisp/ROLL_SHM = 625
#EWA report 12.2007
#parameter created by: BASIS 03.01.2008 19:49:57
dbs/mss/stats_on = 1
#EWA report 12.2007
#parameter created by: BASIS 03.01.2008 19:49:33
dbs/oledb/stats_on = 1
#EWA report 12.2007
#parameter created by: BASIS 03.01.2008 19:48:23
dbs/oledb/add_procs = 8
#EWA report 12.2007
#parameter created by: BASIS 03.01.2008 19:47:29
rsdb/esm/max_objects = 2000
#EWA report 12.2007
#parameter created by: BASIS 03.01.2008 19:47:03
rsdb/otr/buffersize_kb = 4096
#EWA report 12.2007
#parameter created by: BASIS 03.01.2008 19:46:21
rsdb/esm/buffersize_kb = 4096
Eyl#l 2006 EWA raporu
#parameter created by: BASIS 24.11.2006 13:18:14
ztta/parameter_area = 16000
Eyl#l 2006 EWA raporu
#parameter created by: BASIS 24.11.2006 13:16:43
enque/table_size = 10000
Eyl#l 2006 EWA raporu
#parameter created by: BASIS 24.11.2006 13:16:20
gw/max_sys = 2000
#Eyl#l 2006 EWA raporu
#parameter created by: BASIS 24.11.2006 13:16:01
gw/max_overflow_size = 25000000
#Eyl#l 2006 EWA raporu
#parameter created by: BASIS 24.11.2006 13:15:19
rdisp/max_comm_entries = 2000
Eyl#l 2006 EWA raporu
#parameter created by: BASIS 24.11.2006 13:14:48
rdisp/tm_max_no = 2000
Eyl#l 2006 EWA raporu
#parameter created by: BASIS 24.11.2006 13:14:20
gw/max_conn = 2000
Eyl#l 2006 EWA raporu
#parameter created by: BASIS 24.11.2006 13:13:42
rdisp/max_arq = 2000
#Eyl#l 2006 EWA raporu
#parameter created by: BASIS 24.11.2006 13:12:57
ztta/roll_area = 3500000
#parameter created by: BASIS 18.05.2005 09:20:25
#old_value: 90 changed: BASIS 18.05.2005 09:22:25
rdisp/max_hold_time = 300
#parameter created by: BASIS 20.08.2003 12:10:20
#old_value: 6144
#changed: BASIS 03.01.2008 19:42:10
rsdb/obj/buffersize = 20000
#parameter created by: BASIS 20.08.2003 12:09:48
#old_value: 6000
#changed: BASIS 03.01.2008 19:42:59
rsdb/obj/max_objects = 20000
note 103747
#parameter created by: BASIS 08.07.2003 20:42:11
#old_value: 250000
#changed: BASIS 30.10.2007 10:56:17
#abap/buffersize = 100000
#changed: BASIS 03.01.2008 19:40:36
#abap/buffersize = 300000
#by: BASIS 12.06.2008
abap/buffersize = 400000
note 103747
#parameter created by: BASIS 08.07.2003 20:41:32
#zcsa/presentation_buffer_area = 20000000
#64 bite gectikten sonra by: BASIS 10.06.2008
zcsa/presentation_buffer_area = 30000768
note 103747
#parameter created by: BASIS 08.07.2003 20:40:55
rsdb/ntab/ftabsize = 30000
note 103747
#parameter created by: BASIS 08.07.2003 20:40:12
rtbb/max_tables = 500
note 103747
#parameter created by: BASIS 08.07.2003 20:39:15
#old_value: 20000
#changed: BASIS 03.01.2008 19:41:29
#rtbb/buffer_length = 30000
#64 bite gectikten sonra by: BASIS 10.06.2008
rtbb/buffer_length = 50000
note 103747
#parameter created by: BASIS 08.07.2003 20:38:26
zcsa/db_max_buftab = 10000
note 103747
#parameter created by: BASIS 08.07.2003 20:37:37
#zcsa/table_buffer_area = 50000000
#64 bite gectikten sonra by: BASIS 10.06.2008
#zcsa/table_buffer_area = 89000000
by: BASIS 12.06.08
zcsa/table_buffer_area = 99000000
note 103747
#parameter created by: BASIS 08.07.2003 20:36:54
sap/bufdir_entries = 10000
note 103747
#parameter created by: BASIS 08.07.2003 20:36:12
rsdb/cua/buffersize = 8000
#note 103747
#parameter created by: BASIS 08.07.2003 20:34:46
#old_value: 5000 changed: BASIS 08.07.2003 20:35:39
rsdb/ntab/sntabsize = 5500
#parameter created by: BASIS 08.07.2003 20:33:56
#note 103747
#old_value: 10607 changed: BASIS 08.07.2003 20:34:58
#old_value: 10000 changed: BASIS 08.07.2003 20:35:39
rsdb/ntab/irbdsize = 11000
#note 103747
#parameter created by: BASIS 08.07.2003 20:32:18
rsdb/ntab/entrycount = 40000
#old_value: 2076 changed: BASIS 28.06.2005 19:36:21
#old_value: 5735 changed: BASIS 28.06.2005 19:40:01
PHYS_MEMSIZE = 4096
#64 bite gectikten sonra by: BASIS 10.06.2008
abap/heaplimit = 40894464
abap/heap_area_total = 2000683008
ztta/roll_extension = 2000683008
em/blocksize_KB = 4096
*** UPGRADE EXTENSIONS (RELEASE "701") ***
#rdisp/elem_per_queue = 2000
#auth/auth_number_in_userbuffer = 9000
#snc/enable = 0Hi Srikishan;
You are right. The problem was releated with secstore. I found a SAP note ( Note 1532825 - Deleting SECSTORE entries during system export/system copy). I created the program which ise mentioned in the note and than run it. After that everything seems ok now.
Thanks for your help and interest
Best regards
Noyan -
Hi all,
i need you your help in enhancing one existing BPM.
the initial state was
file sys-> BPM -> sap R3 (system A) and also sap R3 (system B)
where the BPM is --> recv > sync send(A)->send(B)
file sys send ONE vendor_key in xml format to BPM.
now sysnc send is conected to R3 A through a RFC_A, which send one key field to RFC_A and get the whole record of a Z-table
through that very RFC_A
this whole record is then sent to another RFC_B thorugh send(B), which update a Z-table in the second sap system B.
if the picture is clear, then the requirement is that:
this time i have to design a BPM which will receive one xml file from file-sys, in which there will be multiple vendor key
instead of one.
the xml message must undergo 1:n transformation in bpm to craete xml messages containing one vendo key each.then parallely calling RFC_a with vendor key , get the reponse record from system R3 A, and call RFC_B to send the record to system R3 B.HI Abhishek,
Thanks for your response. Pls find below my BPM Design Details
Block 1
Step Name : Block1
Exceptions : runTime
Transformation
Step Name : Transformation1
Exception : System Error - runTime
Exception Branch
Exception Handler - runTime
Control Step
Setp Name : Control0
Action : Throw Alert.
I have followed the blog : https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/3465. [original link is broken] [original link is broken] [original link is broken]
Still the alert is not getting triggered.
Could you pls guide me, whethere is there any change need in my above design.
Regards
Mani -
Unable to convert sender service for IDoc to SOAP Scenario
Hi,
I tried to find the solution my way and by using the search function but without any success. I have the folowing scenario:
SYS(my sap system) => IDoc => PI (Process Integration) => SOAP => XML
When i send the IDoc to the PI System and open SXI_Moni the folowing error is shown:
"Unable to convert the sender service receiver_service to an ALE logical system"
I read about Adapter Specific Identifies so i go to ID->Service without partner->Business System->MyBusinessSystem(SYS) then in Menü on Services and checked Adapter Specific Identifies. They are like maintained in SLD.
Next is a Cache refresh i tried a full one but no impact
Then i tried a header mapping in receiver agreement. I mapped there the receiver party to the definied receiver party and the receiver_service to the service.
I have no idea
Thanks for help, be sure that helpful answers will be awarded
regards
Matthias
P.S. What causes this error ? For my opinion ALE has already done all neccesary things (The Idoc is in PI System and the data is available in mesaage payload) so why didn't the pi map it and send it via Soap?Hi Matthias
>>I dont know if its helpful but in SLD are only the system of our landscape so i have no entry for the external Party.
Party information is generally not required to be maintained in SLD
>>Adapter Specific Identifies
What is the value you have given for sender Business system->adapter specific identifier. Is it the same as the partner profile name in sender SAPECC. if not try making them same.
Regards
Suraj -
Suggesitions required for JDBC in Web Dynpro
Hi SDN,
I am working on Web Dynpro project, till now we are working with SAP R/3 as backend database.
Now we need to store the data in sql server along with SAP R/3 with the same project.
Our people suggested to use EJBs.
I need to know how to create EJB for web dynpro if any specification.
how to deploy it in sneak previw
How to call that EJB in the application.
I have sneak preview in sys1,
Sql server in sys 5,
SAP R/3 in sys2,
NWDS in sys-j2e.
please suggest any PDF exists.
help me in this regard.
Thanks in Advance.
Sai.K.KGo through the following posts.
https://forums.sdn.sap.com/click.jspa?searchID=851468&messageID=1486826
https://forums.sdn.sap.com/click.jspa?searchID=851468&messageID=1531194
https://forums.sdn.sap.com/click.jspa?searchID=851468&messageID=2393486
I have submitted JavaBeanGenerator sample code which will create a bean out of the SAPDB tables.Please find the link below.
https://www.sdn.sap.com/irj/sdn/softwaredownload?download=/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/business_packages/a1-8-4/simple_javabean_generator_project.zip
Regards, Anilkumar -
Experiences around the nCo 3.0 RfcDestinationManager
Hello everyone,
I'm very interested in your application architecture around the .NET connector 3.0.
For example I just don't manage to be friends with the RfcDestinationManager
Example 1:
Okay so there's this MAX_POOL_SIZE and POOL_SIZE setting. According to the developers manual it's exactly the same(?). Whatever. And some piece of documentation I found (some SAP blog) says we cannot grab and manage a connection ourselves and we have to rely on the RfcDestinationManager to return one. That's a good thing. In theory. Indeed this is where it gets complicated.
I wrote a small multi threaded console application to simulate parallel connections. All the console application does is to Ping() the target SAP system. With MAX_POOL_SIZE set to 5 (default value?) I sooner or later run into a SAP.Middleware.Connector.RfcResourceException: Unable to allocate client in pool [NAME=xxx USER=xxx CLIENT=xxx LANG=xxx ASHOST=xxx ASHOST=xxx SYSNR=xxx SYSID=xxx]. MAX_POOL_SIZE [5] exceeded
at SAP.Middleware.Connector.RfcConnectionPool.GetClient()
at SAP.Middleware.Connector.RfcDestination.GetClient(Boolean forRepository)
at SAP.Middleware.Connector.RfcDestination.Ping()
at CA4MultiThread.SapClient.Ping() in D:\workspace\xxx\SapDotNetConnector\CA4MultiThread\SapClient.cs:line 104
at CA4MultiThread.Program.SapPing() in D:\workspace\xxx\SapDotNetConnector\CA4MultiThread\Program.cs:line 98
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
Bad. On one hand I cannot manage the connections myself (because the connector takes care of the connection pool) and on the other hand there's no way to check whether it's safe to submit a request to SAP. Either the connector should implement a queue to handle those scenarios or offer a possibility to check if a connection is present or can be opened.
Of course I can set the MAX_POOL_SIZE to 100 - but what's the point of MAX_POOL_SIZE then?
Example 2:
Another thing that bugs me is the registration of destination configurations.
SAP.Middleware.Connector.RfcInvalidStateException: destination configuration already initialized
at SAP.Middleware.Connector.RfcDestinationManager.RegisterDestinationConfiguration(IDestinationConfiguration config)
at CA4MultiThread.SapClient..ctor() in D:\workspace\rsom\SapDotNetConnector\CA4MultiThread\SapClient.cs:line 81
at CA4MultiThread.SapClient.get_Instance() in D:\workspace\rsom\SapDotNetConnector\CA4MultiThread\SapClient.cs:line 57
at CA4MultiThread.Program.SapPing() in D:\workspace\xxx\SapDotNetConnector\CA4MultiThread\Program.cs:line 96
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
Typically you register your destinations only once. Okay. But in multi threaded scenarios you might very well run into situations where two threads are trying to register their destinations at just the same time and there's your exception. First of all I think the RfcDestinationManager should be aware of its state and know whether it has already a configuration present or not. And the worst thing is... you cannot even check for the RfcDestinationmanager's state yourself. The only public method which comes somewhat close to that purpose is RfcDestinationManager.GetDestination()... but that throws an exception if the destination doesn't exist - so it's not exactly a solution.
So I'm tracking RfcDestinationManager's state - thread safe - in my own application now (which is not a good thing, but I prefer this approach to having some startup code in global.asax or something like that). What's your approach here?Good Day.
I have an existing mobile project that connects to a webService. The webService connects to SAP using the .net connector 3.0. There are multiple concurrent users that make SAP calls, currently there is a random problem that occurs whereby a user gets an incorrect user for the transaction that they are trying to process. The call i make to get a destination is:
RfcDestination destination = RfcDestinationManager.GetDestination(_sapDestinationManager.Username);
_sapDestinationManager.Username being the user which if i compare to the returned destination isn't the same.
This is intermittent and have also tried to implement customDestination to try and fix this but i haven't been able to solve this as yet. I have added a code snippet below:
private static RfcDestination GetSapRfcDestination(string authTicket, out RfcRepository sapRfcRepository,
ref string success)
AuthenticationTicket authenticationTicket;
if (string.IsNullOrEmpty(authTicket)) // Checks if the encrypted authTicket is null, if it is the SAP call is probably not important
authenticationTicket = new AuthenticationTicket();
else
authenticationTicket = new AuthenticationTicket(authTicket); // Decryption of string to get the username and password
if (_sapDestinationManager == null)
_sapDestinationManager = new SapDestinationManager();
RfcDestinationManager.RegisterDestinationConfiguration(_sapDestinationManager);
if (authenticationTicket.UserName == null)
RfcDestination destination = RfcDestinationManager.GetDestination("OneMobile");
sapRfcRepository = destination.Repository; //Out parameter to method
success = "Login Successful"; //Ref parameter
Log.Trace("One Mobile connection: " + destination.Repository.ToString());
return destination;
else
_sapDestinationManager.Username = authenticationTicket.UserName;
_sapDestinationManager.Password = authenticationTicket.Password;
RfcDestination destination = RfcDestinationManager.GetDestination("OneMobile");
RfcCustomDestination customDestination = destination.CreateCustomDestination();
customDestination.User = _sapDestinationManager.Username;
customDestination.Password = _sapDestinationManager.Password;
if (customDestination.SystemAttributes.Destination == null)
RfcDestinationManager.UnregisterDestinationConfiguration(_sapDestinationManager);
_sapDestinationManager = null;
success = "Name or password is incorrect"; //Ref parameter
sapRfcRepository = null; //Out parameter to method
return null;
else
sapRfcRepository = customDestination.Repository; //Out parameter to method
success = "Login Successful"; //Ref parameter
Log.Trace("CTM: " + customDestination.Repository.ToString()); //Loggin
return customDestination; -
Adapter framework failing to send message
Hi,
I am facing an issue in XI, where the adapter framework is getting failed to send the message. The message is also not getting reflected in SXMB_MONI,
"Transmitting the message to endpoint http://server:8080/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 404 : Not found."
No service using the ICM port 8080 is working though active. No XI service, even the ping service in sap/bc/ping is not working.
I have checked the following:
1) SLDCHECK (browser opening properly). In ABAP part i am getting error
Use transaction SLDAPICUST if you wish to maintain
Launching the SLD GUI in a separate browser window.
=> Verify in the browser GUI that the SLD is in a healthy running state!
Calling function LCR_LIST_BUSINESS_SYSTEMS
Retrieving data from the SLD server...
Function call returned exception code 3
=> Check whether the SLD is running!
Summary: Connection to SLD does not work
=> Check SLD function and configurations
for troubleshooting the above error i have gone through the link
http://help.sap.com/saphelp_nw04/helpdata/en/78/20244134a56532e10000000a1550b0/content.htm
Still the problem persists while calling function LCR_LIST_BUSINESS_SYSTEM
2) Then i checked the ping (path - http://server:8080/sap/xi/engine?type=entry ) -- its also not running and showing error :
Service cannot be reached with error code 404 not found.
3) The RFC XIINTEGRATION_SERVER is showing also showing error 404.
4) Checked ICM port - its 8080
Inspite of working hard over this issue, still unable to resolve this issue.
Please help me. Awaiting for your helping suggestions
Thanks in advance..> Still the problem persists while calling function LCR_LIST_BUSINESS_SYSTEM
> 2) Then i checked the ping (path - http://server:8080/sap/xi/engine?type=entry ) -- its also not running and showing error :
> Service cannot be reached with error code 404 not found.
>
> 3) The RFC XIINTEGRATION_SERVER is showing also showing error 404.
> 4) Checked ICM port - its 8080
>
have a look for LCR_LIST_BUSINESS_SYSTEM in the below link
http://help.sap.com/saphelp_nw04/helpdata/en/78/20244134a56532e10000000a1550b0/content.htm
Regards,
Sarvesh -
Dear Friends
I am preparing a FSpec for a customized report ( sales tax register) developed long time back, for 4-5 issues/mistakes in the report.
I've never done this before. Any tips/suggestions?
Rgds
Sumanth.GHi,
i created some of functional specs for a Life science company -
these are the poins which are there in standard templet which we use to upload in
solution manager -
1Functional Specification
1.1 Business Need (functional Narrative of business logic & Rules)
1.2 Business Functionality
1.2.1 Describe u201CAs Isu201D process, the purpose of this business functionalityu2026 <may be able to refer to an existing HLD here>
1.2.2 Describe u201CTo Beu201D process, list and give a description of all process deliverables.
1.3 Propose UI process flow
1.3.1 Supporting UI flow Diagrams
1.3.2 Screen Design/Selection screen
1.4 Reports
1.4.1 Report Name
Example of existing form or layout name.
1.4.2 Report Layout Overview (Standards)
Provide with the sample or standards
1.4.3 Report Output Requirements/Properties
{Examples of report properties are shown below. You may include more as needed}
1.4.4 Report Medium
how do you want users to see/access your report.
1.5 Dependencies
1.5.1.1 Process Dependencies
Describe all the processes and dependencies if applicable.
1.5.1.2 Functional Dependencies
Describe configuration setup if applicable
1.5.1.3 Data Dependencies
Master data setup for this functionality/changes if applicable
1.5.1.4 Job Dependencies
Auto Sys Scheduler, SAP Scheduler u2026if applicable
1.6 Administration Information / Security
1.7 Database Design
1.8 System Architecture
1.9 Risks
1.10 Custom Transactions
1.11 Language Translation Requirements
1.12 Frequency / Data Volume/Performance
1.13 Trouble Shooting /Restart/Recovery Strategy
1.14 Inbound/Outbound/Interfaces
1.15 Data Translation Conversion Logic
1.16 Program/ Function Modules/ Custom Programs
1.17 Additional Report Systems Requirements
2 References
let me know if you need further information regarding the same.
Regards
Rajeev -
Synchronization of R/3 User with self Registration in Portal
Dear All,
In Enterprise portal, we have activated self registration. So that user can register to the portal. We have a scenario that once the user is created in the portal through self registration, the same user Id should be generated in R/3. How do we achieve this in the portal?
Kindly help us for the same.
Regards,
AlpaI was reading SAP certification material just now and have a similar question from my client and looking for answers.
I am writing part of information here so that you can do further research: Please update here what was the result of future understandings and if this worked? Ahh have to type all cant copy from the file
To enable sso b/w sap ume and abap based system, users should ideally have same user id's in both the systems. Replicating usre accnts to relevant sap systems is one meathod to ensure the same user ids.
The data is replicated only from ume to sap system and nt vice versa.
UME accmplishes replication by transmit of XML documents.'
Prerequisites:
Ume supports replication of user data to abap sys with release 4.6D or higher. you can replicate to a maz of 3 systems.
users are created with a de-activated pwd in backend so they shud always logon thru ume in portal and access backend by sso logon tickets.
Procedure:
start config tool
2. choose swich to config editor mode
3. navigate to cluster_data_server_cfg_services
4.switch to edit mode
5.double click on com.sap.security.core.ume.services property sheet
6.specify receiving sys, sending sys, and define sys conn. info. for sap sys
7 save property sheet
8 restart cluster for changes
9. add the sending sys. to sap sys acl list. this is done in sap sys via a data browser against the table smum_acl
After all these steps, create a user in EP and see it being present in R3.
PLZ write back for clarfications or doc, or just to let us know the results and conclusions.
Thanks
ANkur agarwal
SAP Portal consultanat -
404 error while accessing sicf services via apache reverse proxy
Hi,
I set up an reverse proxy with apache 2.2 and try to access SICF Services via this proxy. I got the following error message from the sap system:
Service cannot be reached
The termination occurred in system SMP with error code 404 and for the reason Not found.
The selected virtual host was 0 .
What can I do?
Please select a valid URL.
If you do not yet have a user ID, contact your system administrator.
ErrorCode:ICF-NF-http-c:000-u:SAPSYS-l:E-i:NE-SSMP01_SMP_00-v:0-s:404-r:Notfound
When I access J2EE services via the proxy it works.
Is there any configuration which have to be done in the ABAP Stack for accessing Services via the proxy server?
For tests I tried to access the simple ping service ( /default_host/sap/public/ )
Thanks and best regards,
TimHi Oliver,
I allready checked the SDN posts for the reverse proxy. Maybe I missed something.
The ProxyPreserveHost is on.
I redirect to the ICM. I only redirected to the J2EE for tests. This worked by the way withe the same conifiguration.
Here is my apache config:
VirtualHost *:5443>
ServerName domain.com
ServerAdmin test.de
ProxyPreserveHost On
#ProxyVia On
#AllowEncodedSlashes On
Rewrite Rules
- forward sap/public/ping?sap-client=001 -> Test Ping
- Passthrough /sap/public/ping/*
- Redirect any other URL -> Test Ping
RewriteEngine On
RewriteRule ^/sap/public/ping?sap-client=001$ /sap/public/ping?sap-client=001 [R,L]
RewriteRule ^/sap/public/(.*) /sap/public/$1 [PT,L]
RewriteRule (.*) /sap/public/ping?sap-client=001 [R,L]
RewriteLog logs/rewrite_SMP.log
RewriteLogLevel 3
Reverse Proxy to
- Disable Forward Proxy
- Allow Connections from All
- Reverse Mapping for 302 Response
- Forward / Requests to domain.com:8000
ProxyRequests Off
<Proxy *>
AddDefaultCharset off
Order Allow,Deny
Allow from all
</Proxy>
Forward Rules
ProxyPass /sap/public/ping http://domain.com:8000/sap/public/ping?sap-client=001
ProxyPassReverse / http://domain.com:8000/
</VirtualHost>
Best regards,
Tim
Maybe you are looking for
-
Windows Server TechNet Guru Announced for June 2014
The Results are in! And the winners of the TechNet Guru Competition June 2014 have been posted on the Wiki Ninjas Blog. Below is a summary, heavily trimmed to fit the size restrictions of forum posting. BizTalk Technical Guru - June 2014 Steef-Jan
-
How to save a form for intern use for a client?
Hi, I can only choose between using the FormCentral, email or a server (of which I can't get access). My client needs the form for ONLY intern use - like a simple PDF-doc that eventually collects their data. I used to make such forms in previous vers
-
Recalculation in excel thru java
Hi, Thru java program i can able to read and write the values into the excel sheet. but...Latest re calculating values are not available to read Example, for the following situation i am not getting right values In worksheet1 cell A1 = 10 (writing th
-
Problem with PO output print format
Hello all, I have a problem with PO print output. When I am creating a new PO and taking the printout, the printout is coming perfectly fine. But when I am making any changes to the PO and then trying to taking the printout one more time, the system
-
How to deploye .war files in SOA_Server1 ?
Hi, I was created Auto Generated Task form for Human Task in 11G.After that how to deploye .WAR files manually in "Infra -Soa(Soa_srerver1)" .Plz help me now