XML File in Solution Manager

How to Generate XML file in solution manager for EHP5 upgrade

Hello,
You can find links to many interesting documents and also some troubleshooting guides at https://wiki.sdn.sap.com/wiki/display/SM/Maintenance+Optimizer
Best regards,
Miguel Ariñ

Similar Messages

MOPZ has issues calculating stack XML file in SOLUTION MANAGER

Hello,
We have a SOLUTION MANAGER system on NW 7.0 EHP1 SP stack level at initial support stack (ISS).
Recently we upgraded all our R/3 systems to ECC6.0 EHP4 SPS04 and now we are trying to upgrade the stack level to EHP4 SPS07. So we are trying to get a XML file from MOPZ but no luck.
The backend system has all the correct data updated in SMSY and all looks fine but while we try to calculate the stack for EHP4 SPS07 it ends with error like below mentioned.
Please look into the errors and throw some light if anyone has come across the same.
Error details:
System Messages
Type Message Text
Error The Installation/Upgrade Package for Add-on EA-APP L rel. 600 is not available
Error ABAP queue check failed
But the backend system has EA-APPL level at 604, we do not know why it is looking for installation/upgrade package for
EA-APPL 600.
Regards,
Yoganand.V

hi
can you check the sap note
1. Note 1277035 - Solution Manager: EHP4 product data missing
might be this could be the reason for your issue
or
check the thread already discussed the same and the solution also provided
[EHP4 upgrade error on SAPK-603DHINEAPS|EHP4 upgrade error on SAPK-603DHINEAPS]
////////////////It seems that there is a small bug in teh software vector for EA-PS.
Essentially, SAINT prevents you from going forward because it thinks that you don't have the correct version of EA-PS installed.
The solution for this is described in OSS Note: 1143022
"To import EA-PS in a system that already has the level EA-APPL 604, load the attached file ACP_EAPS.SAR into your system (SPAM-> Support Package -> Load Packages -> from Frontend) before you start the import using SAPehpi. Otherwise, an error may occur in the queue calculation, which can be solved by reloading the ACP"////////////////////////
check and update
Jansi

Error while Importing ResourceObject xml file in Deployment Manager

Hi Everyone,
I am getting this error while doing Import of HRPeopleSoftResourceObjects.xml ( A Resource Object xml file) in Deployment Manager. I am doing this step for Authoritative(Trusted Source) Reconciliation.
Error Says:- Attribute not present in EntityDefination of User :: ExpectedReturnDate.
ExpectedReturnDate is a UDF (Customize) field. I did Metadata and Sandbox import for this field to create this attribute in OIM. I can see this attribute on User Details screen as well as in User Table in OIM. So, ideally this error should not popup. I have to do this import for Reconciliation.
I pulled and checked all the xml files like(UserEO.xml.xml, userEO.xml.xml, userVO.xml, UserVO.xml.xml) from oracle.iam.console.identity.self-service.ear_V2.0_metadata1 and found ExpectedReturnDate field is available.
I am using: OIM Version - Oracle 11g Release 2
Database version - 11.2.0
Weblogic version - 10.3
Please let me know how to resolve this error.
Appreciate your response and support!
Warm Regards
Vijay Kumar

Appreciate your response Kevin!
I saw your response today. What you have suggested in your post make perfect sense to me.
Yesterday, I was able to create Reconciliation profile successfully. No idea how it worked so, didn't updated my post.
I tried to re-import the UDF, noticed ExpectedReturnDate attribute has little icon in fornt of it on deployment manager screen which says on mouse over "new field". No idea why as I didn't delete it from anywhere, perhaps it didn't get imported properly previously. I stepped ahead and clicked the import button on deployment manager but failed as it was throwing an exception which says udf_usr_expectedReturnDate is available in usr table. That makes sense to me as this column got created in usr table in OIM because of previous import and I didn't delete it either. This raised couple of doubts more as, along with this attribute there were other attributes in the same metadata xml file which were part of previous import and their respective columns were already created in usr table. Then why message poped-up for this field in particular? Anyway I went ahead with the import process.
Now I stopped all the server (Admin, SOA and OIM) and restarted them again and performed the same steps as mentioned above and this time it worked as expected. UDF file got imported successfully.
After this I went to Design Console verified all the fields and created the Reconciliation Profile. I checked OIM database and found RA_ProfileName recon tables got created.
As per your comment, Today I checked the RECON_USER_OLDSTATE table but this table is empty.
Still I have couple of doubts, if Reconciliation Profile got created it should create the xml file under metadata direcectory(in my case path should be: /apps/Oracle/Middleware/Oracle_IDM1/server/metadata/db). Please correct me if I am wrong? I hope it should be physical file not a logical file.
Once again thanks for your response!
Warm Regards
Vijay Kumar

Error while importing xml file in calc manager

Hi All,
I am having trouble in importing the xml file for calc manager. I have used the rules migrator utility to convert the .rle file into XML. Now when I import this xml file in the calc manager it gives me the following error- "An invalid application 'XML file name' was found on object Main_Global". Please let me know how should I import the xml file in calc manager and get it deployed. Thakns in advance for the help.
-Kamran

Hi All,
I am having trouble in importing the xml file for calc manager. I have used the rules migrator utility to convert the .rle file into XML. Now when I import this xml file in the calc manager it gives me the following error- "An invalid application 'XML file name' was found on object Main_Global". Please let me know how should I import the xml file in calc manager and get it deployed. Thakns in advance for the help.
-Kamran

XML Interface in Solution Manager

Hi All,
In Solution Documentation presentation, there are slides that give details on importing documentation from external sources like(Excel) into Solution Manager documentation. Has anyone done this task and what is the interface used to export to standard SAP XML format from EXCEL and import files from XML format into soution documentation (SOLAR01)?
Details from slides are:
Using a XML interface business process documentation of external sources like MS Excel, Lotus Notes can be efficiently imported in SAP Solution Manager
Data transfer process flow:
Detailed steps
1. Develop a data extractor program to convert MS Excel to XML document
- Create a program to extract content from data source. The extractor has to use the xml schema definitions provided by SAP
- Extract the data from the data source into XML format
Benefit
Quick and efficient method to transfer external documentation into SAP Solution Manager
Detailed steps
Use SAP Solution Manager interface to import XML documentation
- Import the data into SAP Solution Manager within SAP Solution Manager
- Verify the imported documentation
Thanks and regards,
Nischal

Hello,
You can find links to many interesting documents and also some troubleshooting guides at https://wiki.sdn.sap.com/wiki/display/SM/Maintenance+Optimizer
Best regards,
Miguel Ariñ

Display SXMB_MONI XML errors in Solution Manager (CEN)

Hello All,
Requirement is to display the XML error messages in SXMB_MONI in our Solution Manager (CEN)? Could you please let me know the major steps that would be involved on the same?
Please share your thoughts!
Thank You,
Antarpreet

My apologies not reading it properly....
Solution manager also usess the same concepts of the CCMS as we do it in XI, so you can setup the XI envinorment details in solution manager and try to capture the alerts....
Here are the Steps:
Prereq:
All Satellite systems connected from Solution Manager on the "Transaction SMSY" screen.
Prepare RFC connections between Solution Manager and Satellite systems for data collection ( RZ20 Data collection RFCs)
Steps:
1. Register "SAPCCMSR" and "SAPCCM4.X" on Sattilite Systems to report ABAP and Java stacks in local systems and report to Solution manager System
2. On Solution Manager System ( Acting as Central System) configure CCMS monitoring sets fromRZ20.
3. RZ21 --> configure CCMS pings alert monitoring.
all info with step by step guide avalible from Solution Manager configuration guides and http://service.sap.com/rkt
( This ref from solution manager forum)
check this link also:
http://www.scribd.com/doc/7858198/Solution-Manager-SAP-NW2004S-Monitoring-Setup-Guide-SP12

Need ur help in downloading sim files for solution manager

Hi All,
Couple of days before i have downloaded one sim file from service market place which was very nice about initial configuration of solution manager. But my pc hard disk damaged, again i was searching for sim file but i dint get it.
I have digged service.sap.com/rkt and service.sap.com/rkt-solman, but i dint find.
I will be glad & very thankful if some one can post me sim url, as its must for me...
Waiting for ur positive replies and support

Hi Mahesh,
Most of them from Zip only, if you unzip you may get the Sim files or the flash files (which you can run through IE)
all solman related sim available in service.sap.com\rkt-solman -> under the defined clasification. Hope you must get the file
while checking I got this file [Initial and basic config|https://websmp210.sap-ag.de/~sapidb/011000358700000872242009E/index.htm]
hope this too help
Thanks,
Jansi

SAP GUI 7.10 - Issue reading files from Solution Manager

Hi everyone,
We have just installed SAP GUI 7.10 on our PC and have tried to open documents from Solution Manager.
On both Display and Change mode we are getting "The document cannot be displayed" (SOLAR_DOC021)
Can you suggest anything regarding the source of the problem? Any quick resolution?
Thank you
Corinne

Found it myself. Tricky indeed.
http://service.sap.com/patches
- Search for Support Packages and Patches
- Enter Search Term "SAP GUI"
- Select SAP GUI FOR WINDOWS
- Select SAP GUI FOR WINDOWS 7.10 CORE
- Select SAP GUI FOR WINDOWS 7.10 CORE, on the next page also
- Select Win 32
- Arrive at avail. downloads
Regards,
Nathan

Do i required to generate XML file for JAVA upgrade.

Dear frnds,
I am in process of upgrading EP 6.0 to EP 7.0 EHP1 for SR1.
I am following document Upgrade Guide SAP NetWeaver 7.0 Java Including Enhancement Package 1
As of media list guide i have selected .
51036889_1/2 for UPG MASTER BS7 SR1
51037093_1,2,3 for NW 7.0 EHP1 SR1 java SW components 1/2
51036767_2 for BS7 UC kernel 7.01 AIX 64 bit.
Well, i have a query here when i am doing upgrade on ABAP stack ECC 5.0 to ECC 6.0 EHP4 SR1 i alowed to select required compoenets , which eventually will generate mea XML file in Solution manager system.
But, When i have planned to UPGRADE only JAVA Stack for EP 6.0 to EP 7.0 EHP1 SR1. When i selected my system in Solution manager i am not getting option for UPGRADE.
If it is so how about my XML file during JAVA upgrade is not mandatory or not .. Please advice me on this.
regards,
rahul

Hi Rahul,
Yes, for Java Upgrade to EHP1 you need xml file. Normally you should be able to download xml file from solution manager from MOPZ.
If you are not able to download it from solman then you can also download the xml file from service market place and this is only for EHP1. Follow below procedure to download xml file from SMP for EHP1:
Go to https://websmp205.sap-ag.de/sp-stacks
Click on SP Stack download.
Select SP Stack Netweaver 7.0 (New window will open)
Then on New Window Select Source Stack, Target Stack and usgae type. Then Click Next.
On Next screen Select Kernel and IGS. Then Go Next.
On that screen you will get a option to Save as File. Then save as xml.
This is the xml file that you can use in upgrade.
For EHP4 you cannot download it from service market place.
Thanks
Sunny

Solution Manager trace file ? Details of all systems messages ?

Hi,
I had developed custom applications involving different systems like IDES, R/3, File system and web services and BPM scenarios.
These systems are integrated with XI, and now I want to monitor the message exchanges between these systems.
I need all information (in form of txt or log trace file) containing
which systems are involved. Parameters used during communications data exchanged between them or message header, content of the messages etc.
As far as I know log files contain lot of information about user activities like transactions executed, messages exchanged between systems etc......I already tried to monitor the log files at XI level, but it contain very less information about the executions.
Solution manager and remote systems configurations are already done.
I have the following questions.....
1) Will Solution manager be the right choice to monitor such information ? If yes, then where and how ?
2) Is there any combined log file in solution manager which contain all log information about the connected systems ?
3) Where I can find the log files of solution manager ? (Is there a single file which contains all information?)
4) How communication (message exchanges) between composite applications is monitored in SAP ?
How to switch on tracing for Log file (which trace level and what settings), offcourse it will generate lot of data
Regards,
hussaan

Hi,
Please download that attachment "scripts_1139623.sar" provided in SAP Note 1139623 - Using transaction RZ20 to monitor remote Oracle databases.
Upon extraction of scripts_1139623.sar the following files you will get.
rz20_nonabap.sql
dbcheckora10_oltp.sql
dbcheckora.sql
Then Perform the below mentioned Steps to resolve your issue.
Step 1: Create tables DBCHECKORA and DBMSGORA:
sqlplus SAPSR3DB/<pwd>
SQL> @rz20_nonabap.sql
Step 2: Fill the table DBCHECKORA:
sqlplus SAPSR3DB/<pwd>
SQL> @dbcheckora10_oltp
Step 3: Create the synonyms (as user ora<sid>):
brconnect -u / -c -f crsyn -o SAPSR3DB
sqlplus "/as sysdba"
CREATE PUBLIC SYNONYM SAP_DBSTATC FOR SAPSR3DB.DBSTATC;
CREATE PUBLIC SYNONYM SAP_DBCHECKORA FOR SAPSR3DB.DBCHECKORA;
CREATE PUBLIC SYNONYM SAP_DBMSGORA FOR SAPSR3DB.DBMSGORA;
Step 4: Grant Privileges for OPS$<SID>ADM User for the above created Tables
sqlplus "/as sysdba"
grant all on SAPSR3DB.DBSTATC to OPS$<SID>ADM;
grant all on SAPSR3DB.DBCHECKORA to OPS$<SID>ADM;
grant all on SAPSR3DB.DBMSGORA to OPS$<SID>ADM;
grant all on SAPSR3DB.DBSTAIHORA to OPS$<SID>ADM;
grant all on SAPSR3DB.DBSTATHORA to OPS$<SID>ADM;
grant all on SAPSR3DB.DBSTATIORA to OPS$<SID>ADM;
grant all on SAPSR3DB.DBSTATTORA to OPS$<SID>ADM;
commit;
Step 5:
Now after successful execution of above mentioned Steps , in DBACOCKPIT (system configuration), try to save the Remote DB entry with "Collect Alert Data". It will be saved without any error.
If you find any errors, post the error contents as a reply of this thread message.
Regards,
Bhavik G. Shroff

Source XML File Issue....

Hi All,
I am importing a source xml file using import manager.But the Number of root nodes changes in the source file changes when i import a xml file with only 1 record and multiple record.So I am unable to maintain a same map for the same xml file with different records.I guess something is wrong in my xml structure.
This is my source xml file:
>><?xml version="1.0" encoding="utf-8" ?>
>><ns1:MT_MDM_003_Shipping xmlns:ns1="urn:HaworthInc-com:Customer_Master">
>><Record>
>><Sales_Organization>1001</Sales_Organization>
>><Distribution_Channel>00</Distribution_Channel>
>></Record>
>><Record>
>><Sales_Organization>1001</Sales_Organization>
>><Distribution_Channel>00</Distribution_Channel>
>></Record>
>></ns1:MT_MDM_003_Shipping>
If i use the above file in the import manager I am seeing the Source dropdown (Source Hierarchy) where we select the source file as
>>None
>>ns1:MT_MDM_003_Shipping
>>Records
If i use the same import file with just 1 record as follows
>><?xml version="1.0" encoding="utf-8" ?>
>><ns1:MT_MDM_003_Shipping xmlns:ns1="urn:HaworthInc-com:Customer_Master">
>><Record>
>><Sales_Organization>1001</Sales_Organization>
>><Distribution_Channel>00</Distribution_Channel>
>></Record>
>></ns1:MT_MDM_003_Shipping>
If i use the above file in the import manager Now I am seeing the Source dropdown (Source Hierarchy) where we select the source file as only.Records is missing
>>None
>>ns1:MT_MDM_003_Shipping
>>Records (This is missing now)
Since I am missing the Records I have to create the different map for the same file.
Is there anything missing in the XML???Or the XML structure is wrong????
Any Help greatly appreciated.

Thanks for the reply,
I am running into this error now,when I use schema gainst the xml file...
Logon Error: Cannot load xml file
Error:
COM error 80004005 Unspecified error
source = msxml4.dll Description = file:///c:/.........
The "namespace provided differs from the schema's 'urn:Test-com:Customer_Master' targetNamespace
XML File:
<?xml version="1.0" encoding="UTF-8" ?>
<ns0:Import_File_Format_008_Correspondence xmlns:ns0="urn:Test-com:Customer_Master">
<Record>
<Customer_Nr>ZTEST001</Customer_Nr>
<Company_Code>1001</Company_Code>
<Acctg_clerk>03</Acctg_clerk>
<Bank_statement>1</Bank_statement>
<Acct_at_cust>ZZZZ1234</Acct_at_cust>
<Decentralized_processing>x</Decentralized_processing>
<Coll_Invoice_variant>z</Coll_Invoice_variant>
<Customer_user>ZCUST USER</Customer_user>
<Actclk_telno>CLERK TEL NR</Actclk_telno>
<Clerks_fax>12345678</Clerks_fax>
<Clerks_internet>clerk internet</Clerks_internet>
<Account_memo>account memo</Account_memo>
<Dunn_Procedure>1000</Dunn_Procedure>
<Dunning_block>A</Dunning_block>
<Dunnrecipient>CP3016</Dunnrecipient>
<Legdunnproc>04/22/2008</Legdunnproc>
<Last_dunned>04/21/2008</Last_dunned>
<Dunning_level />
<Dunning_clerk>06</Dunning_clerk>
</Record>
</ns0:Import_File_Format_008_Correspondence>
XSD File:
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns="urn:Test-com:Customer_Master" xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:Test-com:Customer_Master">
<xsd:element name="MT_MDM_008_Correspondence" type="DT_MDM_008_Correspondence" />
<xsd:complexType name="DT_MDM_008_Correspondence">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">51f4f670330e11ddabec00112539c3ab</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="Record" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">bcb36bb01c4111ddabe302004c4f4f50</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Customer_Nr" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">bcb36bb11c4111ddccfa02004c4f4f50</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Company_Code" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">bcb36bb21c4111dd818902004c4f4f50</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Acctg_clerk" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">bcb36bb31c4111dda34102004c4f4f50</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Bank_statement" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">bcb36bb41c4111dda01702004c4f4f50</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Acct_at_cust" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">bcb36bb51c4111dd817202004c4f4f50</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Decentralized_processing" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">bcb36bb61c4111ddb52602004c4f4f50</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Coll_Invoice_variant" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">bcb36bb71c4111ddca1902004c4f4f50</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Customer_user" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">bcb36bb81c4111ddb7a302004c4f4f50</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Actclk_telno" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">bcb36bb91c4111ddca3502004c4f4f50</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Clerks_fax" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">bcb36bba1c4111ddaad102004c4f4f50</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Clerks_internet" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">bcb36bbb1c4111dd956902004c4f4f50</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Account_memo" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">bcb36bbc1c4111ddb20902004c4f4f50</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Dunn_Procedure" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">bcb36bbd1c4111dd87e302004c4f4f50</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Dunning_block" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">bcb36bbe1c4111dd9aaa02004c4f4f50</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Dunnrecipient" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">bcb36bbf1c4111dda84302004c4f4f50</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Legdunnproc" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">bcb36bc01c4111ddae5402004c4f4f50</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Last_dunned" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">bcb36bc11c4111dd82e802004c4f4f50</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Dunning_level" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">bcb36bc21c4111ddc26a02004c4f4f50</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Dunning_clerk" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">bcb36bc31c4111ddce7f02004c4f4f50</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

Creating sample XML file from Oracle Reports

I did a search and could not find a good answer - hopefully this is not a dumb question.
We are getting around to evaluating this tool, and I have looked at the whitepapers/user guides. I viewed the flash demo on how to build a template using the add-in. All of this seems really easy to do once you have the XML file generated.
We have a custom report that outputted to PDF. Its a very simple report, so I went ahead and switch the output type to XML. When I go to view the file through the View Output button, it gives me an error about not being able to view it - the error says it cannot display the XML data with the current style sheet - gives a line number for the temporary file and thats about it.
Question is this - should I be able to see the XML file through concurrent manager, or do I physically have to go the ouput directory and grab the file? I understand the whole process of hooking up a template to a concurrent program once I create it, but I figure having the data would make creating the template easier. Sort of a chicken and the egg things.
Thanks!

That sounds like a browser issue.
once you flip the output to XML the 'Output' file from the concurrent manager will now be XML, try doing a save as rather than opening directly or use Tools>Copy file.
Regards, Tim

OIM server crashes while Importing OIM AD connector config XML files

while installing OIM connector for Microsoft Active directory on the 2nd step of installation "Import of Connector XML Files (Using Deployment Manager)" Installation fails and OIM server crashes... my OIM server version is 11.1.1.3.0 and Connector is ActiveDirectory 9.1.1.5.0
Here is oim_server1-diagnostic log file
[2012-01-10T17:23:10.450+05:00] [oim_server1] [ERROR] [] [XELLERATE.ADAPTERS] [tid: [ACTIVE].ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: XELSYSADM] [ecid: 0000JJ7ZjsLFW7WFLz3V8A1F31xJ00006f,0] [APP: oim#11.1.1.3.0] [dcid: 80666d38c1d0770e:-122ffcd8:134c75e0aa6:-7ffd-00000000000001e9] Class/Method: tcAdpUtils/compileAdapter encounter some problems: Could not compile adapter : adpADCSMOVEGROUP
[2012-01-10T17:23:10.465+05:00] [oim_server1] [ERROR] [] [XELLERATE.ADAPTERS] [tid: [ACTIVE].ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: XELSYSADM] [ecid: 0000JJ7ZjsLFW7WFLz3V8A1F31xJ00006f,0] [APP: oim#11.1.1.3.0] [dcid: 80666d38c1d0770e:-122ffcd8:134c75e0aa6:-7ffd-00000000000001e9] Class/Method: tcAdpUtils/compileAdapter encounter some problems: Compile failed on Tue Jan 10 17:23:10 UZT 2012[[
error: Exception thrown while constructing Processor object: null
----------------SOURCE FILE
1: /* Copyright (c) 2001 - 2007, Oracle Corporation. All rights reserved.
2: */
3: package com.thortech.xl.adapterGlue.ScheduleItemEvents;
4: import com.thortech.xl.dataobj.*;
5: //import com.thortech.xl.adapterGlue.*;
6: //import com.thortech.xl.dataobj.tcDataSet;
7: import java.io.IOException;
8: import java.util.*;
9: import java.io.FileWriter;
10: import java.io.File;
11: import java.sql.Timestamp;
12: import java.text.DateFormat;
13: import com.thortech.xl.dataobj.util.tcAdapterTaskException;
14: import com.thortech.xl.dataobj.util.*;
15: import com.thortech.xl.dataobj.util.tcJarEntryClassLoader;
16: import com.thortech.xl.remotemanager.*;
17: import java.rmi.*;
18: import java.net.URL;
19: import java.lang.reflect.Constructor;
20: import java.lang.reflect.Method;
21: import java.lang.reflect.Modifier;
22: import java.lang.reflect.InvocationTargetException;
23: import java.lang.reflect.Field;
24: import java.net.*;
25:
26: public class adpADCSMOVEGROUP extends com.thortech.xl.adapterfactory.events.tcAdpEvent {
27: public adpADCSMOVEGROUP() {
28: super();
29: setEventName("ADCS Move Group");
30: }
31:
32: Hashtable ihTaskRetVals = new Hashtable();
33:
34: // Adapter Variables
35: String OrgName; // Organization Name
36: String sConfigurationLookUp; // ADParameterLookUp
37: long ADServer; // AD Server
38: String ObjectGUID; // ObjectGUID
39:
40: //Persistant Objects
41: Object ADconsObj;
42: Class clsAD;
43:
44: //Variables needed for class loader
45: String sURL;
46: URL url1;
47: URL[] aURL;
48: ClassLoader moURLClassLoader;
49: Class moTargetClass;
50: Object[] maoConstructorArgs;
51: Class[] masConParamTypes;
52: Constructor moCons;
53:
54: protected void implementation() throws Exception {
55:
56: try {
57:
58: if (! initAdapter("ADCS Move Group"))
59: return;
60:
61: // Run Time Variables
62: OrgName = getRunTimeValue("OrgName").toString();
63: sConfigurationLookUp = getRunTimeValue("sConfigurationLookUp").toString();
64: ADServer = ((Long)getRunTimeValue("ADServer")).longValue();
65: ObjectGUID = getRunTimeValue("ObjectGUID").toString();
66:
67: //Initialize persistant object "AD"
68: clsAD = Class.forName("com.thortech.xl.integration.ActiveDirectory.tcUtilADTasks");
69: maoConstructorArgs = new Object[]{getITAttrVal(ADServer, "Server Address"), getITAttrVal(ADServer, "Root Context"), getITAttrVal(ADServer, "Admin FQDN"), getITAttrVal(ADServer, "Admin Password"), getITAttrVal(ADServer, "Use SSL"), getITAttrVal(ADServer, "Port Number"), getITAttrVal(ADServer, "Invert Display Name"), "yes", sConfigurationLookUp, getDataBase()};
70: masConParamTypes = new Class[]{String.class, String.class, String.class, String.class, String.class, String.class, String.class, String.class, String.class, Class.forName("com.thortech.xl.dataaccess.tcDataProvider")};
71: moCons = clsAD.getConstructor(masConParamTypes);
72: ADconsObj = moCons.newInstance(maoConstructorArgs);
73:
74:
75: // Execute Tasks and store results in Hashtable...
76:
77: ihTaskRetVals.put("MOVEGROUP", MOVEGROUP());
78: // Output mapping for Task MOVEGROUP
79: setAdpRetVal(ihTaskRetVals.get("MOVEGROUP"), "String");
80:
81:
82: finalizeAdapter();
83:
84: } catch (tcAdapterTaskException e) {
85: e.printStackTrace();
86: updateSchItem("R", e.getMessage(), e.getReason());
87: return;
88: } catch (Exception e) {
89: e.printStackTrace();
90: updateSchItem("R", e.getMessage(), getReason("", e));
91: return;
92: }
93:
94: }
95:
96: // *** Move Group ***
97: private Object MOVEGROUP() throws Exception {
98: Object oRetVal = "";
99:
100: Object objCons;
101: String sTaskName = "Move Group";
102: try {
103:
104: System.out.println("Running Move Group");
105:
106: //This method uses persistent object "AD"
107:
108: // Initialize method
109: Class[] moMethodParmTypes = new Class[] {String.class, String.class, Class.forName("com.thortech.xl.dataaccess.tcDataProvider")};
110: Object[] moMethodParams = new Object[] {OrgName, ObjectGUID, getDataBase()};
111: Method moMethod = clsAD.getMethod("moveGroup", moMethodParmTypes);
112:
113: // Check for static method
114: if (Modifier.isStatic(moMethod.getModifiers()))
115: ADconsObj = null;
116:
117: // Invoke method
118: oRetVal = moMethod.invoke(ADconsObj, moMethodParams);
119:
120: } catch (Exception e) {
121: e.printStackTrace();
122: if (e instanceof InvocationTargetException) {
123: Throwable t = ((InvocationTargetException)e).getTargetException();
124: throw new tcAdapterTaskException("adpADCSMOVEGROUP", "Move Group", t.getMessage(), "", "");
125: } else {
126: throw new tcAdapterTaskException("adpADCSMOVEGROUP", "Move Group", e.getMessage(), "", "");
127: }
128: }
129: return returnVal(oRetVal);
130: }
131: }
----------------COMMAND LINE javac -classpath C:\Oracle\MIDDLE~1\WLSERV~1.3\server\ext\jdbc\oracle\11g\ojdbc6dms.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\user-patch.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\soa-startup.jar;;C:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_oepe1033\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_ocp353\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\JDK160~1\lib\tools.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.3.0.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1/lib/ant-all.jar;C:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\oracle.soa.common.adapters_11.1.1\oracle.soa.common.adapters.jar;C:\Oracle\MIDDLE~1\ORACLE~1\soa\modules\commons-cli-1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1\soa\modules\oracle.soa.mgmt_11.1.1\soa-infra-mgmt.jar;C:\Oracle\Middleware\Oracle_IDM1\oam\agent\modules\oracle.oam.wlsagent_11.1.1\oam-wlsagent.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.xdk_11.1.0\xsu12.jar;C:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules.xquery_10.3.1.0.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\db2jcc4.jar;C:\Oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\soa-infra;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\fabric-url-handler_11.1.1.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\quartz-all-1.6.5.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\oracle.soa.fabric_11.1.1\oracle.soa.fabric.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\oracle.soa.adapter_11.1.1\oracle.soa.adapter.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\oracle.soa.b2b_11.1.1\oracle.soa.b2b.jar;C:\Oracle\Middleware\Oracle_IDM1\server\lib\oim-manifest.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrf.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\derby\lib\derbyclient.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\xqrl.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-async.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-auth-client.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-auth-server.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-authz-service.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-configmbeans.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-context.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-entitymgr.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-kernel.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-pluginframework.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-utils.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-workflowservice.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-toplinksession.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlAdapterUtilities.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlAPI.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlAttestation.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlAuditor.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlAuthentication.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlBackOfficeBeans.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlBackofficeClient.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlCache.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlCrypto.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlDataObjectBeans.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlDataObjects.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlDDM.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlGenConnector.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xliGCProviders.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlInputPreprocessor.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlLogger.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlRemoteManager.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlRequestPreview.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlScheduler.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlUtils.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlVO.jar -d C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\\oracle\oim\adapters C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\\oracle\oim\adapters\adpADCSMOVEGROUP.java
[2012-01-10T17:23:14.075+05:00] [oim_server1] [NOTIFICATION] [] [oracle.iam.configservice.impl] [tid: [ACTIVE].ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: XELSYSADM] [ecid: 0000JJ7ZjsLFW7WFLz3V8A1F31xJ00006f,0] [APP: oim#11.1.1.3.0] [dcid: 80666d38c1d0770e:-122ffcd8:134c75e0aa6:-7ffd-00000000000001e9] Inside PostImport method of UserManagementPostImportForDm
[2012-01-10T17:23:14.450+05:00] [oim_server1] [ERROR] [] [oracle.iam.configservice.impl] [tid: [ACTIVE].ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: XELSYSADM] [ecid: 0000JJ7ZjsLFW7WFLz3V8A1F31xJ00006f,0] [APP: oim#11.1.1.3.0] [dcid: 80666d38c1d0770e:-122ffcd8:134c75e0aa6:-7ffd-00000000000001e9] The attribute ObjectGUID does not exist!
[2012-01-10T17:23:15.075+05:00] [oim_server1] [NOTIFICATION] [IAM-0080013] [oracle.iam.platform.kernel.impl] [tid: [ACTIVE].ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: XELSYSADM] [ecid: 0000JJ7ZjsLFW7WFLz3V8A1F31xJ00006f,0] [APP: oim#11.1.1.3.0] [dcid: 80666d38c1d0770e:-122ffcd8:134c75e0aa6:-7ffd-00000000000001e9] [arg: 30] [arg: 0] [arg: oracle.iam.platform.entitymgr.vo.EntityMetadata] [arg: MODIFY] Kernel executing default validation with process id, event id, entity and operation 30.0.oracle.iam.platform.entitymgr.vo.EntityMetadata.MODIFY
[2012-01-10T17:23:15.090+05:00] [oim_server1] [NOTIFICATION] [IAM-0080014] [oracle.iam.platform.kernel.impl] [tid: [ACTIVE].ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: XELSYSADM] [ecid: 0000JJ7ZjsLFW7WFLz3V8A1F31xJ00006f,0] [APP: oim#11.1.1.3.0] [dcid: 80666d38c1d0770e:-122ffcd8:134c75e0aa6:-7ffd-00000000000001e9] [arg: 30] [arg: 30] [arg: oracle.iam.platform.entitymgr.vo.EntityMetadata] [arg: MODIFY] [arg: /file/User.xml] Kernel executing default action handler with process id, event id, entity and operation 30.30.oracle.iam.platform.entitymgr.vo.EntityMetadata.MODIFY.entityId=/file/User.xml

There are different log handlers and loggers with different properties what are XELLRATE.DDM's properties
here is the logging.xml file
<?xml version="1.0" encoding="UTF-8"?>
<logging_configuration>
<log_handlers>
<log_handler name='console-handler' class='oracle.core.ojdl.logging.ConsoleHandler' formatter='oracle.core.ojdl.weblogic.ConsoleFormatter' level='WARNING:32'/>
<log_handler name='odl-handler' class='oracle.core.ojdl.logging.ODLHandlerFactory' filter='oracle.dfw.incident.IncidentDetectionLogFilter'>
<property name='path' value='${domain.home}/servers/${weblogic.Name}/logs/${weblogic.Name}-diagnostic.log'/>
<property name='maxFileSize' value='10485760'/>
<property name='maxLogSize' value='104857600'/>
<property name='encoding' value='UTF-8'/>
<property name='useThreadName' value='true'/>
<property name='supplementalAttributes' value='J2EE_APP.name,J2EE_MODULE.name,WEBSERVICE.name,WEBSERVICE_PORT.name,composite_instance_id,component_instance_id,composite_name,component_name'/>
</log_handler>
<log_handler name='wls-domain' class='oracle.core.ojdl.weblogic.DomainLogHandler' level="WARNING"/>
<log_handler name='owsm-message-handler' class='oracle.core.ojdl.logging.ODLHandlerFactory'>
<property name='path' value='${domain.home}/servers/${weblogic.Name}/logs/owsm/msglogging'/>
<property name='maxFileSize' value='10485760'/>
<property name='maxLogSize' value='104857600'/>
<property name='encoding' value='UTF-8'/>
<property name='supplementalAttributes' value='J2EE_APP.name,J2EE_MODULE.name,WEBSERVICE.name,WEBSERVICE_PORT.name'/>
</log_handler>
<log_handler name='em-log-handler' level='NOTIFICATION:32' class='oracle.core.ojdl.logging.ODLHandlerFactory' filter='oracle.dfw.incident.IncidentDetectionLogFilter'>
<property name='path' value='${domain.home}/servers/${weblogic.Name}/sysman/log/emoms.log'/>
<property name='format' value='ODL-Text'/>
<property name='useThreadName' value='true'/>
<property name='maxFileSize' value='5242880'/>
<property name='maxLogSize' value='52428800'/>
<property name='encoding' value='UTF-8'/>
</log_handler>
<log_handler name='em-trc-handler' level='TRACE:32' class='oracle.core.ojdl.logging.ODLHandlerFactory'>
<property name='logreader:' value='off'/>
<property name='path' value='${domain.home}/servers/${weblogic.Name}/sysman/log/emoms.trc'/>
<property name='format' value='ODL-Text'/>
<property name='useThreadName' value='true'/>
<property name='locale' value='en'/>
<property name='maxFileSize' value='5242880'/>
<property name='maxLogSize' value='52428800'/>
<property name='encoding' value='UTF-8'/>
</log_handler>
</log_handlers>
<loggers>
<logger name="" level="WARNING:1">
<handler name="odl-handler"/>
<handler name="wls-domain"/>
<handler name="console-handler"/>
</logger>
<logger name="oracle" level="NOTIFICATION:1"/>
<logger name="oracle.adf"/>
<logger name="oracle.adf.desktopintegration"/>
<logger name="oracle.adf.faces"/>
<logger name="oracle.adf.controller"/>
<logger name="oracle.adfinternal"/>
<logger name="oracle.adfinternal.controller"/>
<logger name="oracle.jbo"/>
<logger name="oracle.adfdt"/>
<logger name="oracle.adfdtinternal"/>
<logger name="oracle.bam"/>
<logger name="oracle.bam.common"/>
<logger name="oracle.bam.system"/>
<logger name="oracle.bam.middleware"/>
<logger name="oracle.bam.adc.security"/>
<logger name="oracle.bam.common.security"/>
<logger name="oracle.bam.adc.ejb.BamAdcServerBean"/>
<logger name="oracle.bam.reportcache.ejb.ReportCacheServerBean"/>
<logger name="oracle.bam.eventengine.ejb.EventEngineServerBean"/>
<logger name="oracle.bam.ems.ejb.EMSServerBean"/>
<logger name="oracle.bam.adc.api"/>
<logger name="oracle.bam.adc"/>
<logger name="oracle.bam.eventengine"/>
<logger name="oracle.bam.ems"/>
<logger name="oracle.bam.webservices"/>
<logger name="oracle.bam.web"/>
<logger name="oracle.bam.reportcache"/>
<logger name="oracle.bpm"/>
<logger name="oracle.bpm.analytics"/>
<logger name="oracle.integration"/>
<logger name="oracle.integration.platform.blocks.cluster"/>
<logger name="oracle.integration.platform.blocks.deploy.coordinator"/>
<logger name="oracle.integration.platform.blocks.event.saq"/>
<logger name="oracle.integration.platform.blocks.java"/>
<logger name="oracle.integration.platform.faultpolicy"/>
<logger name="oracle.integration.platform.testfwk"/>
<logger name="oracle.soa"/>
<logger name="oracle.soa.adapter"/>
<logger name="oracle.soa.b2b"/>
<logger name="oracle.soa.b2b.apptransport"/>
<logger name="oracle.soa.b2b.engine"/>
<logger name="oracle.soa.b2b.repository"/>
<logger name="oracle.soa.b2b.transport"/>
<logger name="oracle.soa.b2b.ui"/>
<logger name="oracle.soa.bpel"/>
<logger name="oracle.soa.bpel.console"/>
<logger name="oracle.soa.bpel.engine"/>
<logger name="oracle.soa.bpel.engine.activation"/>
<logger name="oracle.soa.bpel.engine.agents"/>
<logger name="oracle.soa.bpel.engine.bpel"/>
<logger name="oracle.soa.bpel.engine.compiler"/>
<logger name="oracle.soa.bpel.engine.data"/>
<logger name="oracle.soa.bpel.engine.delivery"/>
<logger name="oracle.soa.bpel.engine.deployment"/>
<logger name="oracle.soa.bpel.engine.dispatch"/>
<logger name="oracle.soa.bpel.engine.sensor"/>
<logger name="oracle.soa.bpel.engine.translation"/>
<logger name="oracle.soa.bpel.engine.ws"/>
<logger name="oracle.soa.bpel.engine.xml"/>
<logger name="oracle.soa.bpel.entity"/>
<logger name="oracle.soa.bpel.jpa"/>
<logger name="oracle.soa.bpel.system"/>
<logger name="oracle.soa.dvm"/>
<logger name="oracle.soa.management.facade.api"/>
<logger name="oracle.soa.mediator"/>
<logger name="oracle.soa.mediator.common"/>
<logger name="oracle.soa.mediator.common.cache"/>
<logger name="oracle.soa.mediator.common.error"/>
<logger name="oracle.soa.mediator.common.error.recovery"/>
<logger name="oracle.soa.mediator.common.message"/>
<logger name="oracle.soa.mediator.dispatch"/>
<logger name="oracle.soa.mediator.dispatch.resequencer.toplink"/>
<logger name="oracle.soa.mediator.filter"/>
<logger name="oracle.soa.mediator.instance"/>
<logger name="oracle.soa.mediator.management"/>
<logger name="oracle.soa.mediator.metadata"/>
<logger name="oracle.soa.mediator.monitor"/>
<logger name="oracle.soa.mediator.resequencer"/>
<logger name="oracle.soa.mediator.resequencer.besteffort"/>
<logger name="oracle.soa.mediator.resequencer.fifo"/>
<logger name="oracle.soa.mediator.resequencer.standard"/>
<logger name="oracle.soa.mediator.service"/>
<logger name="oracle.soa.mediator.serviceEngine"/>
<logger name="oracle.soa.mediator.transformation"/>
<logger name="oracle.soa.mediator.utils"/>
<logger name="oracle.soa.mediator.validation"/>
<logger name="oracle.soa.scheduler"/>
<logger name="oracle.soa.services.common"/>
<logger name="oracle.soa.services.identity"/>
<logger name="oracle.soa.services.notification"/>
<logger name="oracle.soa.services.rules"/>
<logger name="oracle.soa.services.rules.obrtrace"/>
<logger name="oracle.soa.services.workflow"/>
<logger name="oracle.soa.services.workflow.common"/>
<logger name="oracle.soa.services.workflow.evidence"/>
<logger name="oracle.soa.services.workflow.metadata"/>
<logger name="oracle.soa.services.workflow.persistency"/>
<logger name="oracle.soa.services.workflow.query"/>
<logger name="oracle.soa.services.workflow.report"/>
<logger name="oracle.soa.services.workflow.runtimeconfig"/>
<logger name="oracle.soa.services.workflow.soa"/>
<logger name="oracle.soa.services.workflow.task"/>
<logger name="oracle.soa.services.workflow.task.dispatch"/>
<logger name="oracle.soa.services.workflow.task.routing"/>
<logger name="oracle.soa.services.workflow.user"/>
<logger name="oracle.soa.services.workflow.verification"/>
<logger name="oracle.soa.services.workflow.worklist"/>
<logger name="oracle.soa.services.workflow.performance"/>
<logger name="oracle.soa.services.cmds"/>
<logger name="oracle.soa.wsif"/>
<logger name="oracle.soa.xref"/>
<logger name="oracle.sdp"/>
<logger name="oracle.sdpinternal"/>
<logger name="oracle.sdp.owlcs.customer"/>
<logger name="oracle.sdp.owlcs.config"/>
<logger name="oracle.sdp.owlcs.timer"/>
<logger name="oracle.sdp.messaging"/>
<logger name="oracle.sdp.messaging.client"/>
<logger name="oracle.sdp.messaging.driver"/>
<logger name="oracle.sdp.messaging.engine"/>
<logger name="oracle.sdp.messaging.parlayx"/>
<logger name="oracle.sdp.messaging.server"/>
<logger name="oracle.wsm"/>
<logger name="oracle.wsm.msg.logging" level="NOTIFICATION:1" useParentHandlers="false">
<handler name="owsm-message-handler"/>
<handler name="wls-domain"/>
</logger>
<logger name='oracle.sysman' level='NOTIFICATION:32' useParentHandlers='false'>
<handler name='em-log-handler'/>
<handler name='em-trc-handler'/>
</logger>
</loggers>
</logging_configuration>

Solution Manager project export / import

Hi,
is there any possibility to export the project files from Solution Manager, change some data in an other program and then import them back to solution manager? This whole import/export process should work automatically.
The entire thing is to avoid that the users have to work with the Solution Manager instead of their usual and well known programs for project management.
Regards

Hi Andreas,
Currently there is no possibility to perform this.
kind regards,
Fabricius

Importing OIM AD connector config XML files

Hello All,
I am importing the AD connector files in the OIM admin and user console.
After selecting the AD connector files, in step 2 i need the perform 3 operations as stated below.
My operation fails when I try to import XML files using deployment manager. I am able to see the import screen and there it says you cannot perform this operation.
I get this error:
Step 2      :      Connector Installation
ActiveDirectory      9.1.1.4      Installation Status      :      Failed
     PASSED Configuration of Connector Libraries
     FAILED Import of Connector XML Files (Using Deployment Manager)
          Compilation of Adapter Definitions
The error stated is : DOBJ.XML_IMPORT_ERROR
ORA-00904: "OBJ_OFFLINED": invalid identifier
Thanks in advance for your help.
Regards,
VSN

Hello all,
I was able to figure out the answer for my question on the xml import error.
It was due to improper patching of OIM server.
This error can be confirmed if you check the OBJ table, it will not have a column name called OBJ_OFFLINE.
So apply all the patches from scratch and in sequence.
_VSN

XML File in Solution Manager

Similar Messages

Maybe you are looking for