Avoiding creation of DBlink during deployment of mappings using OMBPlus
Hi
we are facing an issue in our OWB 11g R2 (upgraded to patchset 10185523)
We are deploying the mappings using OMBPlus like so
OMBCREATE TRANSIENT DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN' ADD ACTION '$object_type_DEPLOY' SET PROPERTIES (OPERATION)VALUES ('CREATE') SET REFERENCE $object_type '$objname'
OMBDEPLOY DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN'
set OMBCONTINUE_ON_ERROR true
OMBDROP DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN'
OMBCOMMIT
The $objname is any object(in this case a mapping) that we are deploying
OMBPlus generates a script on OWB level to create the associated DBlink each time it deploys a mapping and we get an error
INFORMATIONAL
multiple rows found for select into statement
DBlink_a Create Error ORA-02011: duplicate database link name
But the mapping deploys fine.
Any tips how we can avoid creation of dblinks from OMBPlus whilst deploying our mappings only?
Any help will be appreciated
Birdy
Edited by: birdy on 22-Nov-2011 05:22
I dont think that you can:
"Deploying a mapping or a process flow includes these steps:
•Generate the PL/SQL, SQL*Loader, or ABAP script, if necessary.
•Register the required locations and deploy any required connectors. This ensures that the details of the physical locations and their connectors are available at runtime."
http://www.comp.dit.ie/btierney/Oracle11gDoc/owb.111/b31278/concept_deploy.htm
But error that you get is only informational so you dont have to worry about it.
Similar Messages
-
Problem deploying certain mappings using OMBPlus
We've got a problem deploying certain mapings using OMBPLus. This applies to all mappings that use a function to lookup the effective date of a SCD (type 2) from a lookup table. We use that function in the dimension operator properties as the "Default Effective Time of Open Record". Though the validation of those mappings fails they can nevertheless be deployed using the Control Center Manager. And, best of all, they work fine.
Now we have to deploy those mappings using OMBPlus because we're not allowed to work with tools on the preproduction and production systems. Deploying those mappings with OMBPlus doesn't seem to work. It works fine for all other mappings but not for those mentioned above. Has anybody a solution?
Regards,
JörgHi Dave,
this is the error message I get whe I run my OMBPLus script:
OMB05602: An unknown Deployment error has occured for Object Type PUB03205 : Validation Error: MAP_DIM_FAHRZEUGKLASSE : VLD-5010: The Default Effective Date of open records for dimension DIM_FAHRZEUGKLASSE should be an expression of type DATE. Value "FCT_GET_AKT_LL_vmon()" is not a valid date: PLS-00201: identifier 'FCT_GET_AKT_LL_VMON' must be declared
I'm not quite sure about what you mean with creating a stub function. As you can see from the error message above I use a function called FCT_GET_AKT_LL_vmon that returns the actual date od the load from a lookup table. This function is of course present in the target schema.
Regards,
Jörg -
Avoiding creation of reservation during creation of production order
Dear gurus,
when we create a production order for a semifinshed material there are reservations created for the raw material used to produce the semifinished material ,what if I what to avoid the creation of material reservation .
I have tried out with setting in opl8 wherein we specify the creation of reservation on release of production order or on creation or never but it is not working otu please if u can help me out.
I what to create manual reservation for production orders......Is it possible?
Thanks in advance.Dear ,
.As long as , you have BOM components are in stock , system will generate reservation for them when you create Production order where as if any of the component is not available in the stock then it will generate PR based on the material master set up because when you are creating production order or creating planned order through MRP , system performs material availablity check in the back ground and generate either reservation or PR automatically .
Secondly, you can not create Manual Reservation , See the Std SAP message .Message no. M7 126
You entered an order whose category only permits automatic reservations. The following order categories do not allow manual reservations:
10 PP production order
20 network
30 maintenance order
40 batch order (process manufacturing)
50 inspection lot.
So conclusion is you can't stop creation of reseravtion .Curious to know why you do not want reservation for PO ?
Hope this is clear
Regards
JH -
Importing mappings using OMBPLUS
we just started using OWB, and in our environment we do not want to migrate mappings from DEV to TEST to PRODUCTION using GUI. i heard that importing and deploying can be done using OMB scripting ..
can any please give some example scripts for importing mapping and deploying mappings on to a different box.
ThanksDo you need to move the mapping definitions over to each box? Or just deploy them to different boxes?
If you want a single design repository where you deploy from to multiple runtime areas, then this is acheived through creating multiple configurations and changing your project configuration prior to each deployment.
If, on the other hand, you want to MOVE the current mapping definitions to each box where you will, in effect, be setting up a new design AND runtime repository, then there is added complexity.
For example, scripting dropping old mappings prior to importing the new version of the project to avoid legacy objects hanging around becomes a potential issue. for that, you would need to script deployemnt plans of type DELETE for objects no longer wanted. This also helps script the new deployment as you don't have to code which mappings are being CREATEd, and which are being REPLACEd.
I have an OMB+ script I am just testing right now to load a project MDL file and deploy it to a new repository. I have a partial script for unloading and old version of the project, but it is not ready yet. This one also assumes a clean install where I even have to go so far as to register my runtime user, and define and register all schemas to be used by the control center. We also do not deploy normal database objects via OWB. This script assumes that the proper database setup for tables, sequences, views, etc. has been done prior to deploying the OWB mappings and process flows. We use Designer as the repository of record for all non-OWB database objects.
I don't claim to be an experienced TCL or OMB+ developer, but it might help you out as a starting point. Note that the config file and file of library functions used by this script (such as the exec_omb you will see that I use) are also appended to this post.
File: owb_import.tcl
#get db connection info
source c:\\omb\\owb_config.tcl
#get standard library
source c:\\omb\\omb_library.tcl
# Connect to repos
# Commit anything from previous work in this session, otherwise OMBDISCONNECT will fail out.
exec_omb OMBCOMMIT
# If already connected, disconnect first.
set print [exec_omb OMBDISCONNECT]
# Test if message is "OMB01001: Not connected to repository." or "Disconnected."
# any other message is a showstopper!
if [string match Disconn* $print ] {
log_msg LOG "Success Disconnecting from previous repository...."
} else {
# We expect an OMB01001 error for trying to disconnect when not connected
if [string match OMB01001* $print ] {
log_msg LOG "Disconnect unneccessary. Not currently connected...."
} else {
log_msg ERROR "Error Disconnecting from previous repository....Exiting process."
log_msg ERROR "$print"
#exit
set print [exec_omb OMBCONNECT $OWB_DEG_USER/$OWB_DEG_PASS@$OWB_DEG_HOST:$OWB_DEG_PORT:$OWB_DEG_SRVC USE REPOSITORY '$OWB_DEG_REPOS']
if [omb_error $print] {
log_msg ERROR "Unable to connect to repository."
log_msg ERROR "$print" "1"
log_msg ERROR "Exiting Script.............."
return
} else {
log_msg LOG "Connected to Repository"
# Connect to project
set print [exec_omb OMBCC '$PROJECT_NAME']
if [omb_error $print] {
log_msg LOG "Project $PROJECT_NAME does not exist. Creating...."
set print [exec_omb OMBCREATE PROJECT '$PROJECT_NAME']
if [omb_error $print] {
log_msg ERROR "Unable to create project '$PROJECT_NAME'"
log_msg ERROR "$print"
log_msg ERROR "Exiting Script.............."
exec_omb OMBROLLBACK
return
} else {
log_msg LOG "Created Project '$PROJECT_NAME'"
exec_omb OMBCOMMIT
exec_omb OMBSAVE
exec_omb OMBCC '$PROJECT_NAME'
} else {
log_msg LOG "Switched context to project $PROJECT_NAME"
# Check Existance of Oracle Module
set print [exec_omb OMBCC '$ORA_MODULE_NAME']
if [omb_error $print] {
log_msg LOG "Oracle Module $ORA_MODULE_NAME does not exist. Creating...."
set print [exec_omb OMBCREATE ORACLE_MODULE '$ORA_MODULE_NAME']
if [omb_error $print] {
log_msg ERROR "Unable to create module '$ORA_MODULE_NAME'"
log_msg ERROR "$print"
log_msg ERROR "Exiting Script.............."
exec_omb OMBROLLBACK
return
} else {
log_msg LOG "Created Oracle Module '$ORA_MODULE_NAME'"
exec_omb OMBCOMMIT
exec_omb OMBSAVE
exec_omb OMBCC '$ORA_MODULE_NAME'
} else {
log_msg LOG "Switched context to module $ORA_MODULE_NAME"
#switch back up to project level. You cannot attach locations to a module if you are in it.
exec_omb OMBCC '..'
log_msg LOG "Switched context back up to project $PROJECT_NAME"
# Check Existance of OWB Registered USer
set lst [OMBLIST USERS]
if {[string match *$DATA_LOCATION_USER* $lst]} {
log_msg LOG "Verify USer $DATA_LOCATION_USER Exists."
} else {
log_msg LOG "registering User $DATA_LOCATION_USER."
# set print [ exec_omb OMBREGISTER USER '$DATA_LOCATION_USER' SET PROPERTIES (DESCRIPTION, ISTARGETSCHEMA, TARGETSCHEMAPWD) VALUES ('$DATA_LOCATION_USER', 'true', '$DATA_LOCATION_PASS')]
if [omb_error $print] {
log_msg ERROR "Unable to register user '$DATA_LOCATION_USER'"
log_msg ERROR "$print"
log_msg ERROR "Exiting Script.............."
exec_omb OMBROLLBACK
return
exec_omb OMBCOMMIT
# Import MDL File
#switch back up to root level to ensure import succeeds.
exec_omb OMBSAVE
exec_omb OMBCC '..'
log_msg LOG "Switched context back up to root level."
set print [exec_omb OMBIMPORT MDL_FILE '$IMPORT_FILE_PATH/$IMPORT_FILE_NAME' USE UPDATE_MODE MATCH_BY NAMES OUTPUT LOG TO '$IMPORT_LOG_PATH/$IMPORT_LOG_NAME' ]
if [omb_error $print] {
#We expect to get warnings due to differences in Control center names etc,
if {[string match OMB05105* $print]} {
log_msg LOG "MDL File $IMPORT_FILE_NAME imported with warnings"
} else {
log_msg ERROR "Unable to import $IMPORT_FILE_PATH/$IMPORT_FILE_NAME. "
log_msg ERROR "$print"
log_msg ERROR "Exiting Script.............."
exec_omb OMBROLLBACK
return
} else {
log_msg LOG "MDL File $IMPORT_FILE_NAME imported with no warnings.............."
exec_omb OMBCOMMIT
exec_omb OMBCC '$PROJECT_NAME'
log_msg LOG "Switched context back to project level."
# Validate to Control Center
set lst [OMBLIST CONTROL_CENTERS]
if [string match *$CONTROL_CENTER_NAME* $lst] {
log_msg LOG "Verify Control Center $CONTROL_CENTER_NAME Exists."
log_msg LOG "Setting Passwords to enable import and deploy"
set print [exec_omb OMBALTER LOCATION '$DATA_LOCATION_NAME' SET PROPERTIES (PASSWORD) VALUES ('$DATA_LOCATION_PASS')]
if [omb_error $print] {
log_msg ERROR "Unable to log onto location '$DATA_LOCATION_NAME' with password $DATA_LOCATION_PASS"
log_msg ERROR "$print"
log_msg ERROR "Exiting Script.............."
exec_omb OMBROLLBACK
return
exec_omb OMBCOMMIT
set print [exec_omb OMBALTER LOCATION '$WFLOW_LOCATION_NAME' SET PROPERTIES (PASSWORD) VALUES ('$WFLOW_LOCATION_PASS')]
if [omb_error $print] {
log_msg ERROR "Unable to log onto workflow location '$WFLOW_LOCATION_NAME' with password $WFLOW_LOCATION_PASS"
log_msg ERROR "$print"
log_msg ERROR "Exiting Script.............."
exec_omb OMBROLLBACK
return
exec_omb OMBCOMMIT
log_msg LOG "Connecting to Control Center $CONTROL_CENTER_NAME"
set print [exec_omb OMBCONNECT CONTROL_CENTER USE '$DATA_LOCATION_PASS' ]
if [omb_error $print] {
log_msg ERROR "Unable to add Location $DATA_LOCATION_NAME to Control Center $CONTROL_CENTER_NAME"
log_msg ERROR "$print"
log_msg ERROR "Exiting Script.............."
exec_omb OMBROLLBACK
return
exec_omb OMBCOMMIT
log_msg LOG "Connected.............."
} else {
log_msg LOG "Need to create Control Center $CONTROL_CENTER_NAME."
log_msg LOG "Creating Code Location."
# For Global_names = FALSE
# set print [exec_omb OMBCREATE LOCATION '$DATA_LOCATION_NAME' SET PROPERTIES (TYPE, VERSION, DESCRIPTION, BUSINESS_NAME, HOST, PORT, SERVICE, CONNECT_AS_USER, PASSWORD, DATABASE_NAME) VALUES ('ORACLE_DATABASE','$DATA_LOCATION_VERS','ERS Datamart Code User','$DATA_LOCATION_NAME', '$DATA_LOCATION_HOST','$DATA_LOCATION_PORT','$DATA_LOCATION_SRVC', '$DATA_LOCATION_USER','$DATA_LOCATION_PASS','$DATA_LOCATION_SRVC' ) ]
set print [exec_omb OMBCREATE LOCATION '$DATA_LOCATION_NAME' SET PROPERTIES (TYPE, VERSION, DESCRIPTION, BUSINESS_NAME, HOST, PORT, SERVICE, CONNECT_AS_USER, PASSWORD) VALUES ('ORACLE_DATABASE','$DATA_LOCATION_VERS','ERS Datamart Code User','$DATA_LOCATION_NAME', '$DATA_LOCATION_HOST','$DATA_LOCATION_PORT','$DATA_LOCATION_SRVC', '$DATA_LOCATION_USER','$DATA_LOCATION_PASS') ]
if [omb_error $print] {
log_msg ERROR "Unable to create location '$DATA_LOCATION_NAME'"
log_msg ERROR "$print"
log_msg ERROR "Exiting Script.............."
exec_omb OMBROLLBACK
return
exec_omb OMBCOMMIT
log_msg LOG "Creating Workflow Location."
set print [exec_omb OMBCREATE LOCATION '$WFLOW_LOCATION_NAME' SET PROPERTIES (TYPE, VERSION, DESCRIPTION, BUSINESS_NAME, HOST, PORT, SERVICE_NAME, PASSWORD, SCHEMA) VALUES ('ORACLE_WORKFLOW','$WFLOW_LOCATION_VERS','ERS Datamart Workflow User','$WFLOW_LOCATION_NAME', '$WFLOW_LOCATION_HOST','$WFLOW_LOCATION_PORT','$WFLOW_LOCATION_SRVC', '$WFLOW_LOCATION_PASS','$WFLOW_LOCATION_USER') ]
if [omb_error $print] {
log_msg ERROR "Unable to create Workflow location '$WFLOW_LOCATION_NAME'"
log_msg ERROR "$print"
log_msg ERROR "Exiting Script.............."
exec_omb OMBROLLBACK
#return
exec_omb OMBCOMMIT
log_msg LOG "Creating Control Center"
set print [exec_omb OMBCREATE CONTROL_CENTER '$CONTROL_CENTER_NAME' SET PROPERTIES (DESCRIPTION, BUSINESS_NAME, HOST, PORT, SERVICE_NAME, USER, SCHEMA, PASSWORD) VALUES ('ERS Datamart Control Center','$CONTROL_CENTER_NAME', '$DATA_LOCATION_HOST','$DATA_LOCATION_PORT','$DATA_LOCATION_SRVC', '$DATA_LOCATION_USER', '$CONTROL_CENTER_SCHEMA','$DATA_LOCATION_PASS') ]
if [omb_error $print] {
log_msg ERROR "Unable to create control center '$CONTROL_CENTER_NAME'"
log_msg ERROR "$print"
log_msg ERROR "Exiting Script.............."
exec_omb OMBROLLBACK
return
exec_omb OMBCOMMIT
log_msg LOG "Adding Location $DATA_LOCATION_NAME to Control Center $CONTROL_CENTER_NAME"
set print [exec_omb OMBALTER CONTROL_CENTER '$CONTROL_CENTER_NAME' ADD REF LOCATION '$DATA_LOCATION_NAME' SET PROPERTIES (IS_TARGET, IS_SOURCE) VALUES ('true', 'true') ]
if [omb_error $print] {
log_msg ERROR "Unable to add Location $DATA_LOCATION_NAME to Control Center $CONTROL_CENTER_NAME"
log_msg ERROR "$print"
log_msg ERROR "Exiting Script.............."
exec_omb OMBROLLBACK
return
exec_omb OMBCOMMIT
log_msg LOG "Adding Workflow Location $WFLOW_LOCATION_NAME to Control Center $CONTROL_CENTER_NAME"
set print [exec_omb OMBALTER CONTROL_CENTER '$CONTROL_CENTER_NAME' ADD REF LOCATION '$WFLOW_LOCATION_NAME' SET PROPERTIES (IS_TARGET, IS_SOURCE) VALUES ('true', 'true') ]
if [omb_error $print] {
log_msg ERROR "Unable to add Location $DATA_LOCATION_NAME to Control Center $CONTROL_CENTER_NAME"
log_msg ERROR "$print"
log_msg ERROR "Exiting Script.............."
exec_omb OMBROLLBACK
#return
exec_omb OMBCOMMIT
log_msg LOG "Setting Control Center as default control center for project"
exec_omb OMBCC 'DEFAULT_CONFIGURATION'
set print [exec_omb OMBALTER DEPLOYMENT 'DEFAULT_DEPLOYMENT' SET REF CONTROL_CENTER '$CONTROL_CENTER_NAME' ]
if [omb_error $print] {
log_msg ERROR "Unable to set Control Center $CONTROL_CENTER_NAME in default configuration"
log_msg ERROR "$print"
log_msg ERROR "Exiting Script.............."
exec_omb OMBROLLBACK
return
exec_omb OMBCOMMIT
exec_omb OMBCC '..'
log_msg LOG "Connecting to Control Center $CONTROL_CENTER_NAME"
set print [exec_omb OMBCONNECT CONTROL_CENTER USE '$DATA_LOCATION_PASS' ]
if [omb_error $print] {
log_msg ERROR "Unable to add Location $DATA_LOCATION_NAME to Control Center $CONTROL_CENTER_NAME"
log_msg ERROR "$print"
log_msg ERROR "Exiting Script.............."
exec_omb OMBROLLBACK
return
exec_omb OMBCOMMIT
log_msg LOG "Registering Code Location."
set print [exec_omb OMBALTER LOCATION '$DATA_LOCATION_NAME' SET PROPERTIES (PASSWORD) VALUES ('$DATA_LOCATION_PASS')]
exec_omb OMBCOMMIT
set print [exec_omb OMBREGISTER LOCATION '$DATA_LOCATION_NAME']
if [omb_error $print] {
log_msg ERROR "Unable to register Location $DATA_LOCATION_NAME"
log_msg ERROR "$print"
log_msg ERROR "Exiting Script.............."
exec_omb OMBROLLBACK
return
exec_omb OMBCOMMIT
log_msg LOG "Registering Workflow Location."
set print [exec_omb OMBALTER LOCATION '$WFLOW_LOCATION_NAME' SET PROPERTIES (PASSWORD) VALUES ('$WFLOW_LOCATION_PASS')]
exec_omb OMBCOMMIT
set print [exec_omb OMBREGISTER LOCATION '$WFLOW_LOCATION_NAME']
if [omb_error $print] {
log_msg ERROR "Unable to register Workflow Location $WFLOW_LOCATION_NAME"
log_msg ERROR "$print"
log_msg ERROR "Exiting Script.............."
exec_omb OMBROLLBACK
return
exec_omb OMBCOMMIT
# Assign location to Oracle Module
log_msg LOG "Assigning Code Location to Oracle Module."
set print [ exec_omb OMBALTER ORACLE_MODULE '$ORA_MODULE_NAME' ADD REFERENCE LOCATION '$DATA_LOCATION_NAME' SET AS DEFAULT ]
if [omb_error $print] {
log_msg ERROR "Unable to add reference location '$DATA_LOCATION_NAME' to module '$ORA_MODULE_NAME' "
log_msg ERROR "$print"
log_msg ERROR "Exiting Script.............."
exec_omb OMBROLLBACK
return
set print [ exec_omb OMBALTER ORACLE_MODULE '$ORA_MODULE_NAME' SET REFERENCE METADATA_LOCATION '$DATA_LOCATION_NAME' ]
if [omb_error $print] {
log_msg ERROR "Unable to set metadata location '$DATA_LOCATION_NAME' on module '$ORA_MODULE_NAME' "
log_msg ERROR "$print"
log_msg ERROR "Exiting Script.............."
exec_omb OMBROLLBACK
return
set print [ exec_omb OMBALTER ORACLE_MODULE '$ORA_MODULE_NAME' SET PROPERTIES (DB_LOCATION) VALUES ('$DATA_LOCATION_NAME') ]
if [omb_error $print] {
log_msg ERROR "Unable to add db_location '$DATA_LOCATION_NAME' to module '$ORA_MODULE_NAME' "
log_msg ERROR "$print"
log_msg ERROR "Exiting Script.............."
exec_omb OMBROLLBACK
return
exec_omb OMBCOMMIT
# Assign location to Workflow Module
log_msg LOG "Assigning Location to Workflow Module."
set print [ exec_omb OMBALTER ORACLE_MODULE '$ORA_MODULE_NAME' ADD REFERENCE LOCATION '$DATA_LOCATION_NAME' SET AS DEFAULT ]
if [omb_error $print] {
log_msg ERROR "Unable to add reference location '$DATA_LOCATION_NAME' to module '$ORA_MODULE_NAME' "
log_msg ERROR "$print"
log_msg ERROR "Exiting Script.............."
exec_omb OMBROLLBACK
return
# Begin Object Deployment
log_msg LOG "*********** Deploying: Mappings ****************"
exec_omb OMBCC '$ORA_MODULE_NAME'
set mapList [ OMBLIST MAPPINGS ]
foreach mapName $mapList {
log_msg LOG "Deploying: $mapName"
set print [ exec_omb OMBCREATE TRANSIENT DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN' ADD ACTION 'MAPPING_DEPLOY' SET PROPERTIES (OPERATION) VALUES ('CREATE') SET REFERENCE MAPPING '$mapName' ]
if [omb_error $print] {
log_msg ERROR "Unable to create Deployment plan for '$mapName'"
log_msg ERROR "$print"
return
set print [ exec_omb OMBDEPLOY DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN' ]
if [omb_error $print] {
log_msg ERROR "Error on execute of Deployment plan for '$mapName'"
log_msg ERROR "$print"
exec_omb OMBDROP DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN'
exec_omb OMBCOMMIT
return
exec_omb OMBDROP DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN'
exec_omb OMBCOMMIT
log_msg LOG "*********** Deploying: Process Flows **************"
exec_omb OMBCC '..'
exec_omb OMBCC '..'
set all_Owfs [OMBLIST PROCESS_FLOW_PACKAGES]
if {$all_Owfs!="" } {
foreach one_Owf $all_Owfs {
set print [ exec_omb OMBCREATE TRANSIENT DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN' ]
if [omb_error $print] {
log_msg ERROR "Unable to create Deployment plan for '$one_Owf'"
log_msg ERROR "$print"
return
set print [ exec_omb OMBALTER DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN' ADD ACTION 'OWFDEP$one_Owf' SET PROPERTIES (OPERATION) VALUES ('CREATE') SET REFERENCE PROCESS_FLOW_PACKAGE '$one_Owf' ]
if [omb_error $print] {
log_msg ERROR "Unable to alter Deployment plan for '$one_Owf'"
log_msg ERROR "$print"
exec_omb OMBDROP DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN'
return
log_msg LOG "OWF LOCATION: $Process_Flow_Module - OWF: $one_Owf Deployment...";
set print [ exec_omb OMBDEPLOY DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN' ]
if [omb_error $print] {
log_msg ERROR "Unable to execute Deployment plan for '$one_Owf'"
log_msg ERROR "$print"
exec_omb OMBDROP DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN'
return
set print [ exec_omb OMBDROP DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN' ]
log_msg LOG "OWF LOCATION: $Process_Flow_Module - OWF: $one_Owf Deployed";
log_msg LOG "OWF LOCATION: $Process_Flow_Module - All Workflows Deployed...";
#OMBDISCONNECTWhich depends on the following two files:
OMB_LIBRARY.TCL
# Default logging function.
# Accepts inputs: LOGMSG - a text string to output
# FORCELOG - if "1" then output regardless of VERBOSE_LOG setting
proc log_msg {LOGTYPE LOGMSG {FORCELOG "0"}} {
global VERBOSE_LOG
if { $VERBOSE_LOG == "1"} {
puts "$LOGTYPE:-> $LOGMSG"
} else {
if { $FORCELOG == "1"} {
puts "$LOGTYPE:-> $LOGMSG"
proc exec_omb { args } {
log_msg OMBCMD "$args"
# the point of this is simply to return errorMsg or return string, whichever is applicable,
# to simplify error checking using omb_error{}
if [catch { set retstr [eval $args] } errmsg] {
return $errmsg
} else {
return $retstr
proc omb_error { retstr } {
# OMB and Oracle errors may have caused a failure.
if [string match OMB0* $retstr] {
return 1
} elseif [string match ORA-* $retstr] {
return 1
} else {
return 0
}and a config file where all config/passowrd info is put.
# GLOBAL VARIABLE DECLARATION SECTION
#DESIGN REPOSITORY CONNECTION INFORMATION
# Login info for the main design repository owner
set OWB_DEG_USER owb_user
set OWB_DEG_PASS password
set OWB_DEG_HOST host01
set OWB_DEG_PORT 5555
set OWB_DEG_SRVC orcl_srvc
set OWB_DEG_REPOS owb_user
# CONTROL CENTER AND LOCATION DECLARATION SECTION
set CONTROL_CENTER_NAME ERS_DM_CTLCNTR
set CONTROL_CENTER_SCHEMA owb_user
#Connection info to ers_etl_app schema for deployment
set DATA_LOCATION_NAME ERS_DM_DATA
set DATA_LOCATION_VERS 9.2
set DATA_LOCATION_USER ERS_ETL_APP
set DATA_LOCATION_PASS ers_etl_app
set DATA_LOCATION_HOST newserver
set DATA_LOCATION_PORT 1555
set DATA_LOCATION_SRVC orcl_new
#Connection info to workflow schema for deployment
set WFLOW_LOCATION_NAME ERS_DM_WFLOW
set WFLOW_LOCATION_VERS 2.6.2
set WFLOW_LOCATION_USER OWF_MGR
set WFLOW_LOCATION_PASS owf_mgr
set WFLOW_LOCATION_HOST newserver
set WFLOW_LOCATION_PORT 1555
set WFLOW_LOCATION_SRVC orcl_new
# PROJECT,MUDULE AND DIRECTORY DECLARATION SECTION
set PROJECT_NAME ERS_DM
set ORA_MODULE_NAME ERS_ETL_APP
set PFLOW_MODULE_NAME LD_DMRT
set PFLOW_PACKAGE_NAME LD_DMRT
# Directory DECLARATION SECTION
set IMPORT_FILE_NAME "ers_dply_tst_rc01.mdl"
set IMPORT_FILE_PATH "C:/OMB/import/db_imports"
set IMPORT_LOG_NAME "ers_dply_tst_rc01_imp.log"
set IMPORT_LOG_PATH "C:/OMB/import/logs"
# Logging Option
global VERBOSE_LOG
set VERBOSE_LOG "1"Hope that this helps you out!
Message was edited by: zeppo
Edited to: Try and correct formatting tags. -
Export/import of mappings using OMBPLUS and Collections?
Hi,
We've got some good TCL code to export (and import) mappings for our projects along the lines of:
OMBEXPORT MDL_FILE '$projname.mdl' \
PROJECT '$projname' \
CONTROL_FILE '$controlfile.txt' \
OUTPUT LOG '$projname.log'
and now we're moving to organizing mappings by OWB COLLECTION and need to export/import by collection instead. Thought it might be as simple as this:
OMBEXPORT MDL_FILE '$collname.mdl' \
FROM COMPONENTS ( COLLECTION '$collname')
CONTROL_FILE '$controlfile.txt' \
but that's not working (saying "Project $collname does not exist.", so it seems to still be treating what I thought was a collection name as a project name . Can someone point out the right syntax to use COLLECTIONs in OMBEXPORT/OMBIMPORT?
All thoughts/tips appreciated...
Thanks,
Jim C.Hi,
If we use the below tcl script for the entire project export , does it also export the locaitons,control center,configurations along???
If yes then can you gimme the script for altering the locations , control center/configuration connection details??
OMBEXPORT MDL_FILE '$projname.mdl' \
PROJECT '$projname' \
CONTROL_FILE '$controlfile.txt' \
OUTPUT LOG '$projname.log'
Can you also provide me the tcl for project import??
Thanks -
Deployment error during deployment of the process flow...
i have made a program using OMB to deploy an OWB process flow. i have used tcl programming to run it on UNIX.
when i run the program it gives me a strange error saying:
an unknown error has occured during deployment .
when i open the OWB design center to check the status i find the the process folw is stuck during the generation part and it continues but the generation never takes place.. for that i wrote an OMBALTER to alter the generation language of the mappings used in the process flow ,but it does not help...
also after the error in the program when i see the mapping through the desibn center i do not see the original mapping when i open the mapping editor.
then if I run the again program again i get the process flow deployed successfully ,obviously with the incorrect mappings.
can anybody plz help me out with it???Hello!
I searched metalink on error RTC-5161 and found a reference in note 392263.1
It is a bug but there is a patch available ( bug 5504848, patch number 5525337).
Read the note on metalink to check if you really hit this bug and apply the patch.
Regards,
Robert -
Could anybody assist me to avoid exception occured during deployment fo webservice application ?
===========================================================================
Deployment started Tue Apr 28 13:49:40 CEST 2009
===========================================================================
Starting Deployment of mdp/commons/ear
Aborted: development component 'mdp/commons/ear'/'accenture.com'/'PJU_MDPCORE2_D'/'20090428154119'/'0':Caught exception during application deployment from SAP J2EE Engine's deploy service:java.rmi.RemoteException: Cannot deploy application accenture.com/mdpcommonsear.. Reason: Exception during generation of components of application accenture.com/mdpcommonsear in container EJBContainer.; nested exception is: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application accenture.com/mdpcommonsear in container EJBContainer. (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of mdp/commons/ear finished with Error (Duration 7781 ms)Could you be a little more specific?
-
CreateProcess exception during deployment...
I've read an old article describing this problem with getting the following dump:
at java.lang.Win32Process.create(Native Method)
at java.lang.Win32Process.<init>(Win32Process.java:66)
at java.lang.Runtime.execInternal(Native Method)
at java.lang.Runtime.exec(Runtime.java:551)
at java.lang.Runtime.exec(Runtime.java:477)
at java.lang.Runtime.exec(Runtime.java:443)
at weblogic.utils.Executable.exec(Executable.java:144)
at weblogic.utils.Executable.exec(Executable.java:108)
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:545)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:372)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:202)
at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java:228)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:799)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
during deployment. And the answer was that the shell executing
the javac gets a command-line that is too long.
The problem appears when adding new beans (which bean is not
important, just the number of beans).
We're running WLS 6.0sp1 and WindowsNT 4.0 sp6.
Is there a way to get the command window to accept longer
command-lines? Is there some way to configure the WLS not
to include all files in a single javac-command?
TIA!
/Mikael Arctaedius??? I think he said that Windows doesn't support command lines over a certain
length and he gave you a suggestion as to how to work around it.
Bill
Mikael Arctaedius wrote:
In short, BEA does not support WLS under Windows?
That some news!
/Mikael Arctaedius
"Cameron Purdy" <[email protected]> wrote:
On Windows, use mappings or subst, change paths from
"i:\somedir\someotherdir\somelongerdir\whatever.jar" to "j:\whatever.jar".
Or do the build on Linux or Solaris and it will work.
I'm sorry that there is no other "solution"
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Mikael Arctaedius" <[email protected]> wrote in message
news:[email protected]...
I've read an old article describing this problem with getting thefollowing dump:
at java.lang.Win32Process.create(Native Method)
at java.lang.Win32Process.<init>(Win32Process.java:66)
at java.lang.Runtime.execInternal(Native Method)
at java.lang.Runtime.exec(Runtime.java:551)
at java.lang.Runtime.exec(Runtime.java:477)
at java.lang.Runtime.exec(Runtime.java:443)
at weblogic.utils.Executable.exec(Executable.java:144)
at weblogic.utils.Executable.exec(Executable.java:108)
atweblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.jav
a:545)
atweblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:372)
atweblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:202)
at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java:228)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:799)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
during deployment. And the answer was that the shell executing
the javac gets a command-line that is too long.
The problem appears when adding new beans (which bean is not
important, just the number of beans).
We're running WLS 6.0sp1 and WindowsNT 4.0 sp6.
Is there a way to get the command window to accept longer
command-lines? Is there some way to configure the WLS not
to include all files in a single javac-command?
TIA!
/Mikael Arctaedius -
Crystal Report not showing up during deployment for CRVS2010
Hi,
Have encountered problem when deploying Crystal Report using VB 2010. The report is able to show up during ASP.net development using VS 2010 but when i try to deploy on a IIS server, the report is just showing a blank page when trying to view using an Explorer on the client side. I'm using Window XP IIS 5.1 web server.
Have tried doing VB setup and installing the merge module CRruntime_13_0_1 but still not working.
Any help will be appreciated.
Thanks
KBWhile the supported platform text says that Microsoft IIS5.1 is supported, I'm a bit dubious as CR 2008 (v. 12.x) did not support IIS5.1. See [KB 1494954 - Crystal Reports 2008 DHTML viewer for VS .NET is blank when displayed on a web form|http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_bi/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333433393334333933353334%7D.do].
I'll check with Program Management and get back with a definitive answer.
Ludek
Follow us on Twitter http://twitter.com/SAPCRNetSup
Got Enhancement ideas? Try the [SAP Idea Place|https://ideas.sap.com/community/products_and_solutions/crystalreports] -
How to Deploy all mappings in a module using OMB+
Hi,
I am using OMB+ to deploy project from DEV to QA , i used a OMB+ script to do the export and one import script to do the import/deployment
both Export and Import are working fine , the problem is in the Deploy part of Import script,
in this script I am connecting to the Repository and importing the Project from DEV and then changed the Context to the module and then connected to the Control centre , when i tried to deploy the mapping i get the error saying the location is not registered to the module
ususally if i use the GUI i double click the module and add the location to the module, howcan i do that in OMB+ ,
Example script would help me a lot
and for deploying the mappings i am using
OMBCREATE TRANSIENT DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN' ADD ACTION 'MAP_DEPLOY' SET PROPERTIES (OPERATION) VALUES ('CREATE') SET REFERENCE MAPPING 'MAPPING NAME'
but i don't want to pass mapping names like this i just want to deploy all mappings in a single step
Please advice me
Thanks in Advance
Suresh
Edited by: Suresh_G on Sep 9, 2008 3:30 PMHi Mahesh,
here is my script,
# Connect to the repository
OMBCONNECT datarepdb/[email protected]:1535:ukfndr USE REPOSITORY 'owb_rep'
puts stdout {Connected to Repository }
#Importing the OWB Project
OMBIMPORT MDL_FILE 'C:/Temp/local/ORAFINDATAREPOSITORY.MDL' \
USE MERGE_MODE \
OUTPUT LOG 'C:/Temp/local//ORAFINDATAREPOSITORY_IMP.LOG'
puts stdout {Import Finished }
OMBCC '/ORAFINDATAREPOSITORY'
# Assign the location to the oracle module
OMBALTER ORACLE_MODULE 'DATAREPDB' SET REFERENCE LOCATION 'DATAREPDB_LOCATION'
OMBALTER ORACLE_MODULE 'DATAREPDB' SET PROPERTIES (DB_LOCATION) VALUES ('DATAREPDB_LOCATION')
puts stdout {location to the oracle module registered}
# Connect to Control Centre for Deployment
OMBCONNECT CONTROL_CENTER USE 'dugout'
puts stdout {Connected to Controle Centre}
OMBCC '/ORAFINDATAREPOSITORY/DATAREPDB'
#Starting the Deployment
puts stdout {Starting the Deployment}
OMBCREATE TRANSIENT DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN' ADD ACTION 'MAP_DEPLOY' SET PROPERTIES (OPERATION) VALUES ('CREATE') SET REFERENCE MAPPING 'XXDR_GL_BALANCE'
OMBDEPLOY DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN'
OMBCOMMIT
puts stdout {Deployed Mappings and Disconnecting }
OMBDISCONNECT
I embeded your script in mine but i was getting errors , i am still trying to resolve it, mine is a TCL script can u please suggest me where actually i should incorporate the ur code and to what level,
in my case we have just one module and need to deploy all the mappings in that module , the above script working fine but i don't want to give all names of mappings hardcoded.
Thanks in advance -
ClassCastException during deployment with more than one used entity
Hi,
i am still trying to get into NW development and got one more time stuck. I have a CE 7.1 SR5 project containing a dictionary, a bean module, an EAR project and a web dynpro project.
With the following two classes everything runs fine:
[AT]Entity
[AT]Table(name="TMP_USER")
[AT]NamedQueries(value={[AT]NamedQuery(name="doLogin", query="SELECT u FROM User u WHERE u.login = :login AND u.password = :password")})
public class User implements Serializable {
[AT]Id
private int id;
private String login;
private String password;
private static final long serialVersionUID = 1L;
public User() {
super();
// Omitted Accessors
[AT]Stateless(name="UserSessionBean")
[AT]WebService
public class UserSessionBean implements UserSessionLocal
[AT]PersistenceContext(unitName="DBAccess")
private EntityManager em;
public User doLogin(String login, String password)
Query query = em.createNamedQuery("doLogin");
query.setParameter("login", login);
query.setParameter("password", password);
try
return (User) query.getSingleResult();
catch(NoResultException e)
return null;
build, deploy, run in webservice navigator -> ok
Then i created a new entity:
[AT]Entity
[AT]Table(name="TMP_PROJECT")
[AT]NamedQueries(value={[AT]NamedQuery(name="findAllProjects", query="SELECT p FROM Project p")})
public class Project implements Serializable {
[AT]Id
private int id;
private int ownerid;
private String name;
private Timestamp creationtime;
private String description;
private int number;
private short subnumber;
private static final long serialVersionUID = 1L;
public Project() {
super();
Omitted Accessors
build, deploy, run in webservice navigator -> no problem.
Then i changed the UserSessionBean to:
[AT]Stateless(name="UserSessionBean")
[AT]WebService
public class UserSessionBean implements UserSessionLocal
[AT]PersistenceContext(unitName="DBAccess")
private EntityManager em;
public User doLogin(String login, String password)
Query query = em.createNamedQuery("doLogin");
query.setParameter("login", login);
query.setParameter("password", password);
try
return (User) query.getSingleResult();
catch(NoResultException e)
return null;
public Projecet testfunc()
return null;
And now during deployment there is an warning (in reality it´s an exception) and the bean does not work any more.
The exception is
1. Exception has been returned while the 'testproject.testcorp.de/testprojectear' was starting. Warning/Exception :
[ERROR CODE DPL.DS.6193] Error while ; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 7707450:com.sap.engine.services.deploy.container.DeploymentException:
at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.makeStartInitially(WebServicesDeployManager.java:693)
at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.makeStartInitially(StartInitiallyTransaction.java:184)
at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:145)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyGlobal(StartTransaction.java:449)
at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:437)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:178)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
Caused by: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Exception occured during web services deployment. Unable to generate serialization framework for web service UserSessionBeanService, application testproject.testcorp.de/testprojectear.
at com.sap.engine.services.webservices.server.deploy.ws.WSInitialStartProcess.generateJAXWSFramework(WSInitialStartProcess.java:360)
at com.sap.engine.services.webservices.server.deploy.ws.WSInitialStartProcess.generateJAXWSFramework(WSInitialStartProcess.java:220)
at com.sap.engine.services.webservices.server.deploy.ws.WSInitialStartProcess.execute(WSInitialStartProcess.java:140)
at com.sap.engine.services.webservices.server.deploy.WSBaseAbstractDProcess.makeProcess(WSBaseAbstractDProcess.java:316)
at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.makeStartInitially(WebServicesDeployManager.java:688)
... 37 more
Caused by: java.lang.ClassCastException: class com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl$5:library:jaxb20[AT]com.sap.engine.boot.loader.ResourceMultiParentClassLoader[AT]1489c06[AT]alive incompatible with class com.sun.xml.bind.v2.model.impl.ClassInfoImpl:library:jaxb20[AT]com.sap.engine.boot.loader.ResourceMultiParentClassLoader[AT]1489c06[AT]alive
at com.sun.xml.bind.v2.model.impl.ClassInfoImpl.getBaseClass(ClassInfoImpl.java:170)
at com.sun.xml.bind.v2.model.impl.RuntimeClassInfoImpl.getBaseClass(RuntimeClassInfoImpl.java:58)
at com.sun.xml.bind.v2.model.impl.RuntimeClassInfoImpl.getBaseClass(RuntimeClassInfoImpl.java:38)
at com.sun.xml.bind.v2.model.impl.ModelBuilder.getClassInfo(ModelBuilder.java:142)
at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:48)
at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:40)
at com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(ModelBuilder.java:189)
at com.sun.xml.bind.v2.model.impl.TypeRefImpl.calcRef(TypeRefImpl.java:56)
at com.sun.xml.bind.v2.model.impl.TypeRefImpl.getTarget(TypeRefImpl.java:33)
at com.sun.xml.bind.v2.model.impl.RuntimeTypeRefImpl.getTarget(RuntimeTypeRefImpl.java:22)
at com.sun.xml.bind.v2.model.impl.RuntimeTypeRefImpl.getTarget(RuntimeTypeRefImpl.java:15)
at com.sun.xml.bind.v2.model.impl.ElementPropertyInfoImpl$1.get(ElementPropertyInfoImpl.java:38)
at com.sun.xml.bind.v2.model.impl.ElementPropertyInfoImpl$1.get(ElementPropertyInfoImpl.java:41)
at java.util.AbstractList$Itr.next(AbstractList.java:422)
at com.sun.xml.bind.v2.model.impl.ModelBuilder.getClassInfo(ModelBuilder.java:139)
at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:48)
at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:40)
at com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(ModelBuilder.java:189)
at com.sun.xml.bind.v2.model.impl.TypeRefImpl.calcRef(TypeRefImpl.java:56)
at com.sun.xml.bind.v2.model.impl.TypeRefImpl.getTarget(TypeRefImpl.java:33)
at com.sun.xml.bind.v2.model.impl.RuntimeTypeRefImpl.getTarget(RuntimeTypeRefImpl.java:22)
at com.sun.xml.bind.v2.model.impl.RuntimeTypeRefImpl.getTarget(RuntimeTypeRefImpl.java:15)
at com.sun.xml.bind.v2.model.impl.ElementPropertyInfoImpl$1.get(ElementPropertyInfoImpl.java:38)
at com.sun.xml.bind.v2.model.impl.ElementPropertyInfoImpl$1.get(ElementPropertyInfoImpl.java:41)
at java.util.AbstractList$Itr.next(AbstractList.java:422)
at com.sun.xml.bind.v2.model.impl.ModelBuilder.getClassInfo(ModelBuilder.java:139)
at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:48)
at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:40)
at com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(ModelBuilder.java:189)
at com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(ModelBuilder.java:204)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:356)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:217)
at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:76)
at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:55)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:210)
at javax.xml.bind.ContextFinder.find(ContextFinder.java:368)
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:574)
at com.sap.engine.services.webservices.jaxws.j2w.JaxWsSchemaGenerator.genJaxbMappings(JaxWsSchemaGenerator.java:274)
at com.sap.engine.services.webservices.jaxws.j2w.JaxWsIMappingGenerator.generateWSDL(JaxWsIMappingGenerator.java:103)
at com.sap.engine.services.webservices.server.deploy.ws.WSInitialStartProcess.generateJAXWSFramework(WSInitialStartProcess.java:286)
... 41 more
I already downgraded my Java JRE/JDK to 1.5.0_15 as it was hinted here in the forum, but the problem persists. Any idea what is wrong?Thanks for the answer, but i am not using this wizard. Some how this project class must be flawed.
public User testfunc()
return null;
works, but changing to
public Project testfunc()
return null;
immediately leads to the above deployment error.
This is the offending class, it compiles without warning
package de.testcorp.testproject.beans;
import java.io.Serializable;
import java.sql.Timestamp;
import javax.persistence.*;
@Entity
@Table(name="TMP_PROJECT")
@NamedQueries(value={@NamedQuery(name="findAllProjects", query="SELECT p FROM Project p")})
public class Project implements Serializable {
@Id
private int id;
private int ownerid;
private String name;
private Timestamp creationtime;
private String description;
private int number;
private short subnumber;
private static final long serialVersionUID = 1L;
public Project() {
super();
public int getId() {
return this.id;
public void setId(int id) {
this.id = id;
public int getOwnerid() {
return this.ownerid;
public void setOwnerid(int ownerid) {
this.ownerid = ownerid;
public String getName() {
return this.name;
public void setName(String name) {
this.name = name;
public Timestamp getCreationtime() {
return this.creationtime;
public void setCreationtime(Timestamp creationtime) {
this.creationtime = creationtime;
public String getDescription() {
return this.description;
public void setDescription(String description) {
this.description = description;
public int getNumber() {
return this.number;
public void setNumber(int number) {
this.number = number;
public short getSubnumber() {
return this.subnumber;
public void setSubnumber(short subnumber) {
this.subnumber = subnumber; -
Error during deployment of Message Driven Bean
Environment: WLS 6.1SP3 on Win2K SP2, non-clustered.
I am getting some error (or perhaps warning) during deployment of Message
Driven Bean. Any one seen this before?
This error only comes on a machine with Dual Network card.
Thanks.
####<Dec 11, 2002 1:23:04 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
<system> <> <010008> <EJB Deploying file: AppRuntime.jar>
####<Dec 11, 2002 1:23:04 AM GMT> <Warning> <J2EE> <QAAPP01> <Makalu> <main>
<system> <> <160007> <You are running WebLogic Server with J2EE 1.3 features
enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP 1.2,
Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server 6.1
is of a non-final version of the appropriate specification. It is subject to
change in future releases once the specification becomes finalized. This may
cause application code developed for BEA WebLogic Server 6.1 that uses the
new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform
supported in future releases of BEA WebLogic Server.>
####<Dec 11, 2002 1:23:07 AM GMT> <Warning> <EJB> <QAAPP01> <Makalu> <main>
<system> <> <010061> <The Message-Driven EJB: ASYNCMessageDrivenBean is
unable to connect to the JMS destination: CQM_MessageQueue. The EJB
container will automatically attempt to re-establish the connection with the
JMS server. This warning may occur during WebLogic Cluster start-up if the
JMS destination is located on another server. When the JMS server connection
is re-established, the Message-Driven EJB will again receive JMS messages.
The Error was:
Unable to create a JNDI InitialContext to lookup the JMS destination. The
error was:
javax.naming.CommunicationException. Root exception is
java.net.ConnectException: t3://127.0.0.1:7001: Destination unreachable;
nested exception is:
java.net.ConnectException: Connection refused: connect; No available router
to destination
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
textFactoryDelegate.java:307)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
textFactoryDelegate.java:211)
at
weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
ory.java:149)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
at javax.naming.InitialContext.init(InitialContext.java:217)
at javax.naming.InitialContext.<init>(InitialContext.java:193)
at
weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageD
rivenBeanInfoImpl.java:641)
at
weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectio
nPoller.java:474)
at
weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller
.java:418)
at
weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSCon
nectionPoller.java:286)
at
weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanIn
foImpl.java:511)
at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
at weblogic.j2ee.Application.addComponent(Application.java:170)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:360)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
Target.java:285)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
eploymentTarget.java:239)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
entTarget.java:199)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:360)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy34.updateDeployments(Unknown Source)
at
weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
ServerMBean_CachingStub.java:2977)
at
weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
icationManager.java:372)
at
weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
r.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:360)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy49.start(Unknown Source)
at
weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
ApplicationManagerMBean_CachingStub.java:480)
at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
at weblogic.management.Admin.finish(Admin.java:644)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
at weblogic.Server.main(Server.java:35)
>
####<Dec 11, 2002 1:23:07 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
<system> <> <010009> <EJB Deployed EJB with JNDI name
ASYNCMessageDrivenBean.>
Hi Tom
Yes we do have an URL provided in the descriptor. It's
t3://jms.server.net:7001.
and the jms.server.net is resolved via a hosts file in Win2K
eg,
192.168.100.200 jms.server.net
You are right in saying that the loopback in a dual-net card is a problem.
But our solution
above solves the issue as long as your host file does not use 127.0.0.1 as
the IP.
We need the URL b/c depending on our client's deployment , the JMS Server
may be remote or may be local.
"Tom Barnes" <[email protected]> wrote in message
news:[email protected]...
> Hi x,
>
> Something to do with the loopback and dual-network cards is
> messin' with WLS' mind. I do not know what the problem is,
> but I can guess:
>
> You have specified an URL in the MDB descriptor when there
> is no need for one. If t3://127.0.0.1:7001 is in the same
> cluster the MDB is running in (I suspect this URL is
> actually the same WL server), then don't specify the URL.
> This URL is only useful for connecting an MDB to a JMS
> server that is outside local server and outside the cluster.
> The URL may be working on single-network card systems
> as perhaps then WL has enough info to guess that you
> actually mean the local WL server, and simply converts
> the context to a local context.
>
> Note that the URL option in the MDB descriptor is actually
> a WebLogic extension of J2EE.
>
> Tom
>
>
>
> x wrote:
> > Environment: WLS 6.1SP3 on Win2K SP2, non-clustered.
> >
> > I am getting some error (or perhaps warning) during deployment of
Message
> > Driven Bean. Any one seen this before?
> > This error only comes on a machine with Dual Network card.
> >
> > Thanks.
> >
> >
> >
> > ####<Dec 11, 2002 1:23:04 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
> > <system> <> <010008> <EJB Deploying file: AppRuntime.jar>
> > ####<Dec 11, 2002 1:23:04 AM GMT> <Warning> <J2EE> <QAAPP01> <Makalu>
<main>
> > <system> <> <160007> <You are running WebLogic Server with J2EE 1.3
features
> > enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP
1.2,
> > Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server
6.1
> > is of a non-final version of the appropriate specification. It is
subject to
> > change in future releases once the specification becomes finalized. This
may
> > cause application code developed for BEA WebLogic Server 6.1 that uses
the
> > new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform
> > supported in future releases of BEA WebLogic Server.>
> > ####<Dec 11, 2002 1:23:07 AM GMT> <Warning> <EJB> <QAAPP01> <Makalu>
<main>
> > <system> <> <010061> <The Message-Driven EJB: ASYNCMessageDrivenBean is
> > unable to connect to the JMS destination: CQM_MessageQueue. The EJB
> > container will automatically attempt to re-establish the connection with
the
> > JMS server. This warning may occur during WebLogic Cluster start-up if
the
> > JMS destination is located on another server. When the JMS server
connection
> > is re-established, the Message-Driven EJB will again receive JMS
messages.
> > The Error was:
> > Unable to create a JNDI InitialContext to lookup the JMS destination.
The
> > error was:
> > javax.naming.CommunicationException. Root exception is
> > java.net.ConnectException: t3://127.0.0.1:7001: Destination unreachable;
> > nested exception is:
> > java.net.ConnectException: Connection refused: connect; No available
router
> > to destination
> > at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
> > at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
> > at
> >
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
> > textFactoryDelegate.java:307)
> > at
> >
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
> > textFactoryDelegate.java:211)
> > at
> >
weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
> > ory.java:149)
> > at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
> > at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
> > at javax.naming.InitialContext.init(InitialContext.java:217)
> > at javax.naming.InitialContext.<init>(InitialContext.java:193)
> > at
> >
weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageD
> > rivenBeanInfoImpl.java:641)
> > at
> >
weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectio
> > nPoller.java:474)
> > at
> >
weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller
> > .java:418)
> > at
> >
weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSCon
> > nectionPoller.java:286)
> > at
> >
weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanIn
> > foImpl.java:511)
> > at
weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
> > at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
> > at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
> > at weblogic.j2ee.Application.addComponent(Application.java:170)
> > at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
> > at
> >
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
> > arget.java:360)
> > at
> >
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
> > Target.java:285)
> > at
> >
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
> > eploymentTarget.java:239)
> > at
> >
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
> > entTarget.java:199)
> > at java.lang.reflect.Method.invoke(Native Method)
> > at
> >
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
> > .java:636)
> > at
> >
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
> > 21)
> > at
> >
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
> > nImpl.java:360)
> > at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
> > at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
> > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
> > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
> > at $Proxy34.updateDeployments(Unknown Source)
> > at
> >
weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
> > ServerMBean_CachingStub.java:2977)
> > at
> >
weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
> > icationManager.java:372)
> > at
> >
weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
> > r.java:160)
> > at java.lang.reflect.Method.invoke(Native Method)
> > at
> >
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
> > .java:636)
> > at
> >
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
> > 21)
> > at
> >
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
> > nImpl.java:360)
> > at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
> > at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
> > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
> > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
> > at $Proxy49.start(Unknown Source)
> > at
> >
weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
> > ApplicationManagerMBean_CachingStub.java:480)
> > at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
> > at weblogic.management.Admin.finish(Admin.java:644)
> > at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
> > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
> > at weblogic.Server.main(Server.java:35)
> >
> > ####<Dec 11, 2002 1:23:07 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
> > <system> <> <010009> <EJB Deployed EJB with JNDI name
> > ASYNCMessageDrivenBean.>
> >
> >
>
-
Error while deploying BPEL Process(Error during deployment: Deployment Fail
Hi,
when i try to deploying 11.1.1.3 - bpel project with thirdpartyparty adapter from jdeveloper to weblogic server, I got the following error.
[04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
[04:53:50 PM] HTTP error code returned [500]
[04:53:50 PM] Error message from server:
Error during deployment: Deployment Failed: [JCABinding] [TPASOAProject.Service1/1.0]Unable to complete load due to: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
[04:53:50 PM] Check server log for more details.
[04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
[04:53:50 PM] #### Deployment incomplete. ####
[04:53:50 PM] Error deploying archive file:/C:/JDeveloper/mywork/Application16/TPASOAProject/deploy/sca_TPASOAProject_rev1.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
Please, any one can tell solution for this.
Thanks In advance
Amar.
Edited by: 897448 on Dec 13, 2011 8:48 PMHi,
when i try to deploying 11.1.1.3 - bpel project with thirdpartyparty adapter from jdeveloper to weblogic server, I got the following error.
[04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
[04:53:50 PM] HTTP error code returned [500]
[04:53:50 PM] Error message from server:
Error during deployment: Deployment Failed: [JCABinding] [TPASOAProject.Service1/1.0]Unable to complete load due to: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
[04:53:50 PM] Check server log for more details.
[04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
[04:53:50 PM] #### Deployment incomplete. ####
[04:53:50 PM] Error deploying archive file:/C:/JDeveloper/mywork/Application16/TPASOAProject/deploy/sca_TPASOAProject_rev1.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
Please, any one can tell solution for this.
Thanks In advance
Amar.
Edited by: 897448 on Dec 13, 2011 8:48 PM -
Error during deploying the java patches.
Hi gurus.
error during deploying jtechf patch.through SDM.when deploying SQL TRACE the probelm occured.SDM LOG
Dec 8, 2008 5:09:21 PM Info: Finished saving the repository
Dec 8, 2008 5:09:24 PM Info: Starting: Update: Selected software component 'SA
P_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.15.0.20080216073957''/'9' updates curren
tly deployed software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.12.0.
20070507085740''/'3'.
Dec 8, 2008 5:09:24 PM Error: Aborted: software component 'SAP_JTECHS'/'sap.co
m'/'SAP AG'/'1000.7.00.15.0.20080216073957''/'9':
Failed deployment of SDAs:
development component 'SQLTrace'/'sap.com'/'SAP AG'/'7.0013.20070703111935.0000'
/'9' : aborted -
Revision: 10459
Author: [email protected]
Date: 2009-09-21 08:42:44 -0700 (Mon, 21 Sep 2009)
Log Message:
Change to ensure ScriptNodes are no longer part of the node tree after interface compilation stage in order to avoid the extra code that was necessary to avoid tripping over them during type checking, etc.
Improving revision 10199 a bit, to allow for single line comments.
QE notes: None
Doc notes: None
Bugs: SDK-22027
Reviewer: Paul
Tests run: Checking, Compiler cyclones
Is noteworthy for integration: No
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-22027
Modified Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/AbstractSyntaxTreeUtil.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/InterfaceCompiler.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/AbstractBuilder.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/DocumentBuilder.javaIn general theory, one now has the Edit button for their posts, until someone/anyone Replies to it. I've had Edit available for weeks, as opposed to the old forum's ~ 30 mins.
That, however, is in theory. I've posted, and immediately seen something that needed editing, only to find NO Replies, yet the Edit button is no longer available, only seconds later. Still, in that same thread, I'd have the Edit button from older posts, to which there had also been no Replies even after several days/weeks. Found one that had to be over a month old, and Edit was still there.
Do not know the why/how of this behavior. At first, I thought that maybe there WAS a Reply, that "ate" my Edit button, but had not Refreshed on my screen. Refresh still showed no Replies, just no Edit either. In those cases, I just Reply and mention the [Edit].
Also, it seems that the buttons get very scrambled at times, and Refresh does not always clear that up. I end up clicking where I "think" the right button should be and hope for the best. Seems that when the buttons do bunch up they can appear at random around the page, often three atop one another, and maybe one way the heck out in left-field.
While I'm on a role, it would be nice to be able to switch between Flattened and Threaded Views on the fly. Each has a use, and having to go to Options and then come back down to the thread is a very slow process. Jive is probably incapable of this, but I can dream.
Hunt
Maybe you are looking for
-
Mail icon at class is not enabled
Hi All I am facing strange problem. For few classes link to email all the enrolled/attended people is not enabling. The only criteria for this link to be enabled is "there should be employees with status (Placed/Attended/Pending feedback). But this l
-
Table every row in new pages leaves a blank page at the end.
Hi All, I have a nested table in a output form. All I have in this form is a nested table nothing else. as per the requirement to have every new row in a new page, I set the after parameter to next page / next content area for the parent row paginati
-
LSO - WBT is showing in portal 31.12.9999
Dear All, We are facing one problem, When we are booking (WBT)course it is showing in the portal unlimited. How to control this one. Is there any possibility to change in BSP page. This booking periods in which table it will store. Please give me
-
Wonky Page Margins - Need Help!
When I create PDF documents from Microsoft programs, the top and bottom page margins display correctly, but print too high or low depending on the page content. Below is a typical example. This is how the page displays on the screen. Everything looks
-
Hi, How to export my Photoshop Elements 8 and Premiere 8 Elements from my old PC to my new PC
Hi, How to export my Photoshop Elements 8 and Premiere 8 Elements from my old PC to my new one - both are Windows 7???