3rd party storage: AoE/Coraid integration

#### LONG POST 1/3 ####
Hi,
We are working on AoE/Coraid (3rd party storage driver) integration within Oracle VM 3.x, we think that will be of use for the community and we'll love to share our work.
But we discovered some issues and hope to have some help via this forum.
So, to let you know how far we are and the current issue we have :
1/ Our AoE RPM package is done (using SDK 3.0.2, waiting for 3.0.3 to be release) :
# uname -a
Linux ovm1 2.6.32.21-41xen #1 SMP Fri Sep 9 00:47:51 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux
# rpm -qa | grep aoe
aoe-6-78
2/ Our AoE init script is activated on boot and work as expected :
# aoe-version
aoetools:     32
installed aoe driver:     78
running aoe driver:     78
# aoe-stat
e66.3 2000.398GB eth1 1024 up
** First issue SOLVED :
But ovs-agent complain each time we try to discover a server using Oracle Manager (running version 3.0.3 in case it may have an impact?) :
[2012-01-19 03:11:39 30488] DEBUG (OVSCommons:124) discover_server: ()
[2012-01-19 03:11:39 30488] WARNING (host:443) cannot get core api version: [Errno 2] No such file or directory: '/usr/lib/python2.4/site-packages/version.properties'
[2012-01-19 03:11:39 30488] DEBUG (OVSCommons:132) discover_server: call completed.
[2012-01-19 03:11:40 30504] DEBUG (OVSCommons:124) discover_hardware: ()
[2012-01-19 03:11:40 30504] ERROR (OVSCommons:143) catch_error: ERROR 0 @ 244 find_aoe_disks() Problems extracting AOE disk info
Traceback (most recent call last):
File "/usr/lib64/ovs-storage-utils/storage_tech/st_ATAoverEthernet.py", line 178, in find_aoe_disks
stdout_LIST, stderr_LIST, exitStatus, deltaTime = vi_utils.vi_exe_sync( vi_errorAndLog_obj, [ 'ata_id', '--export', aoe_devPath ], 10 )
File "/usr/lib64/ovs-storage-utils/vi_utils/vi_process.py", line 615, in vi_exe_sync
theChild     = VI_Process_OBJ( vi_errorAndLog_obj, False, args, relativeTimeoutInSecs, inputData_LIST )
File "/usr/lib64/ovs-storage-utils/vi_utils/vi_process.py", line 106, in __init__
,     0 )                    # creationflags               :: Windows only CreateProcess flag
File "/usr/lib64/python2.4/subprocess.py", line 550, in __init__
errread, errwrite)
File "/usr/lib64/python2.4/subprocess.py", line 1000, in executechild
raise child_exception
OSError: [Errno 2] No such file or directory
Runtime errors occured [1]
Traceback (most recent call last):
File "/opt/ovs-agent-3.0/OVSCommons.py", line 141, in wrapper
return func(*args)
File "/opt/ovs-agent-3.0/OVSDiscoverHardware.py", line 81, in discover_hardware
raise Exception(scsi_logmsg)
Exception: ERROR 0 @ 244 find_aoe_disks() Problems extracting AOE disk info
Traceback (most recent call last):
File "/usr/lib64/ovs-storage-utils/storage_tech/st_ATAoverEthernet.py", line 178, in find_aoe_disks
stdout_LIST, stderr_LIST, exitStatus, deltaTime = vi_utils.vi_exe_sync( vi_errorAndLog_obj, [ 'ata_id', '--export', aoe_devPath ], 10 )
File "/usr/lib64/ovs-storage-utils/vi_utils/vi_process.py", line 615, in vi_exe_sync
theChild     = VI_Process_OBJ( vi_errorAndLog_obj, False, args, relativeTimeoutInSecs, inputData_LIST )
File "/usr/lib64/ovs-storage-utils/vi_utils/vi_process.py", line 106, in __init__
,     0 )                    # creationflags               :: Windows only CreateProcess flag
File "/usr/lib64/python2.4/subprocess.py", line 550, in __init__
errread, errwrite)
File "/usr/lib64/python2.4/subprocess.py", line 1000, in executechild
raise child_exception
OSError: [Errno 2] No such file or directory
Runtime errors occured [1]
We just discovered the st_ATAoverEthernet.py but it look like it is not able to see the available AoE LUNs.
Is the script author (Mr Joshua Nicholas) working for Oracle ???
We just fixed the issue above in file /usr/lib64/ovs-storage-utils/storage_tech/st_ATAoverEthernet.py :
the subprocess call the "ata_id" but this program isn't in PATH !
To test, we did this patch :
diff -upr /usr/lib64/ovs-storage-utils/storage_tech/st_ATAoverEthernet.py.orig /usr/lib64/ovs-storage-utils/storage_tech/st_ATAoverEthernet.py
# diff -upr st_ATAoverEthernet.py.orig st_ATAoverEthernet.py
--- st_ATAoverEthernet.py.orig 2012-01-19 16:23:04.000000000 +0100
+++ st_ATAoverEthernet.py 2012-01-19 11:30:45.000000000 +0100
@@ -175,7 +175,7 @@ def find_aoe_disks( vi_errorAndLog_obj,
aoe_disk_interface = aoe_stat_line_components[2]
aoe_disk_interface_status = aoe_stat_line_components[4]
- stdout_LIST, stderr_LIST, exitStatus, deltaTime = vi_utils.vi_exe_sync( vi_errorAndLog_obj, [ 'ata_id', '--export', aoe_devPath ], 10 )
+ stdout_LIST, stderr_LIST, exitStatus, deltaTime = vi_utils.vi_exe_sync( vi_errorAndLog_obj, [ '/lib/udev/ata_id', '--export', aoe_devPath ], 10 )
serial_cmpldRegEx = re.compile( '^ID_SERIAL=\s*' )
rev_cmpldRegEx = re.compile( '^ID_REVISION=\s*' )
It works, so finaly, we rollback to the last version of st_ATAoverEthernet.py and just (re)created the symlink : /sbin/ata_id -> /lib/udev/ata_id
No more error messages in /var/log/ovs-agent.log as you can see :
[2012-01-19 16:27:05 2607] DEBUG (OVSCommons:124) discover_server: ()
[2012-01-19 16:27:05 2607] WARNING (host:443) cannot get core api version: [Errno 2] No such file or directory: '/usr/lib/python2.4/site-packages/version.properties'
[2012-01-19 16:27:05 2607] DEBUG (OVSCommons:132) discover_server: call completed.
[2012-01-19 16:27:06 2623] DEBUG (OVSCommons:124) discover_hardware: ()
[2012-01-19 16:27:06 2623] DEBUG (OVSCommons:132) discover_hardware: call completed.
[2012-01-19 16:27:07 2672] DEBUG (OVSCommons:124) discover_network: ()
[2012-01-19 16:27:07 2672] DEBUG (OVSCommons:132) discover_network: call completed.
[2012-01-19 16:27:08 2673] DEBUG (OVSCommons:124) discover_storage_plugins: ()
[2012-01-19 16:27:08 2673] DEBUG (OVSCommons:132) discover_storage_plugins: call completed.
[2012-01-19 16:27:08 2674] DEBUG (OVSCommons:124) discover_physical_luns: ('',)
[2012-01-19 16:27:08 2674] DEBUG (OVSCommons:132) discover_physical_luns: call completed.
1/2 CONTINUE ON THE SECOND POST
Edited by: 904919 on Jan 19, 2012 7:04 PM

3/3 END OF THE POST
Write Methods Invoked
Class=InternalJobDbImpl vessel_id=6511 method=addTransactionIdentifier accessLevel=6
Class=DiscoverManagerDbImpl vessel_id=165 method=discoverServer accessLevel=6
Class=InternalJobDbImpl vessel_id=6511 method=setCompletedStep accessLevel=6
Class=InternalJobDbImpl vessel_id=6511 method=setAssociatedHandles accessLevel=6
Class=InternalJobDbImpl vessel_id=6511 method=setContext accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setName accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setFoundryContext accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=onPersistableCreate accessLevel=6
Class=HashMapDbImpl vessel_id=6528 method=remove accessLevel=6
Class=LocalStorageInitiatorDbImpl vessel_id=6529 method=setName accessLevel=6
Class=LocalStorageInitiatorDbImpl vessel_id=6529 method=setFoundryContext accessLevel=6
Class=LocalStorageInitiatorDbImpl vessel_id=6529 method=onPersistableCreate accessLevel=6
Class=LocalStorageInitiatorDbImpl vessel_id=6529 method=setLifecycleState accessLevel=6
Class=LocalStorageInitiatorDbImpl vessel_id=6529 method=setRollbackLifecycleState accessLevel=6
Class=InternalPortDbImpl vessel_id=6535 method=setName accessLevel=6
Class=InternalPortDbImpl vessel_id=6535 method=setFoundryContext accessLevel=6
Class=InternalPortDbImpl vessel_id=6535 method=onPersistableCreate accessLevel=6
Class=PortDownEventDbImpl vessel_id=6541 method=notify accessLevel=6
Class=InternalPortDbImpl vessel_id=6535 method=setLifecycleState accessLevel=6
Class=InternalPortDbImpl vessel_id=6535 method=setRollbackLifecycleState accessLevel=6
Class=InternalPortDbImpl vessel_id=6535 method=setNumber accessLevel=6
Class=InternalPortDbImpl vessel_id=6535 method=setServer accessLevel=6
Class=RootStatisticLogDbImpl vessel_id=117 method=createStatisticSubjectLog accessLevel=6
Class=StatisticSubjectLogDbImpl vessel_id=6542 method=setStatisticSubject accessLevel=6
Class=StatisticSubjectLogDbImpl vessel_id=6542 method=createAllStatisticTypeLogs accessLevel=6
Class=StatisticTypeLogDbImpl vessel_id=6544 method=setType accessLevel=6
Class=StatisticTypeLogDbImpl vessel_id=6546 method=setType accessLevel=6
Class=StatisticTypeLogDbImpl vessel_id=6548 method=setType accessLevel=6
Class=StatisticTypeLogDbImpl vessel_id=6550 method=setType accessLevel=6
Class=StatisticTypeLogDbImpl vessel_id=6552 method=setType accessLevel=6
Class=StatisticTypeLogDbImpl vessel_id=6554 method=setType accessLevel=6
Class=StatisticTypeLogDbImpl vessel_id=6556 method=setType accessLevel=6
Class=StatisticTypeLogDbImpl vessel_id=6558 method=setType accessLevel=6
Class=StatisticTypeLogDbImpl vessel_id=6560 method=setType accessLevel=6
Class=StatisticTypeLogDbImpl vessel_id=6562 method=setType accessLevel=6
Class=StatisticTypeLogDbImpl vessel_id=6564 method=setType accessLevel=6
Class=StatisticTypeLogDbImpl vessel_id=6566 method=setType accessLevel=6
Class=StatisticTypeLogDbImpl vessel_id=6568 method=setType accessLevel=6
Class=StatisticTypeLogDbImpl vessel_id=6570 method=setType accessLevel=6
Class=StatisticTypeLogDbImpl vessel_id=6572 method=setType accessLevel=6
Class=StatisticTypeLogDbImpl vessel_id=6574 method=setType accessLevel=6
Class=StatisticTypeLogDbImpl vessel_id=6576 method=setType accessLevel=6
Class=ServerStoppedEventDbImpl vessel_id=6578 method=notify accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setLifecycleState accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setRollbackLifecycleState accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setType accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setEncodedAgentPassword accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setManagementInternetProtocolAddress accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setAgentVersion accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setBootGeneration accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setRpmVersion accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setOvmVersion accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setHostKernelRelease accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setHostKernelVersion accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setHostname accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setManagerUuid accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setPythonBindingVersion accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=createHypervisor accessLevel=6
Class=XenHypervisorDbImpl vessel_id=6581 method=setName accessLevel=6
Class=XenHypervisorDbImpl vessel_id=6581 method=setFoundryContext accessLevel=6
Class=XenHypervisorDbImpl vessel_id=6581 method=onPersistableCreate accessLevel=6
Class=XenHypervisorDbImpl vessel_id=6581 method=setLifecycleState accessLevel=6
Class=XenHypervisorDbImpl vessel_id=6581 method=setRollbackLifecycleState accessLevel=6
Class=XenHypervisorDbImpl vessel_id=6581 method=setServer accessLevel=6
Class=XenHypervisorDbImpl vessel_id=6581 method=setCompiler accessLevel=6
Class=XenHypervisorDbImpl vessel_id=6581 method=setCompiledBy accessLevel=6
Class=XenHypervisorDbImpl vessel_id=6581 method=setCompileDomain accessLevel=6
Class=XenHypervisorDbImpl vessel_id=6581 method=setCompiledDate accessLevel=6
Class=XenHypervisorDbImpl vessel_id=6581 method=setVersion accessLevel=6
Class=XenHypervisorDbImpl vessel_id=6581 method=clearCapabilities accessLevel=6
Class=XenHypervisorDbImpl vessel_id=6581 method=addCapability accessLevel=6
Class=XenHypervisorDbImpl vessel_id=6581 method=addCapability accessLevel=6
Class=XenHypervisorDbImpl vessel_id=6581 method=addCapability accessLevel=6
Class=XenHypervisorDbImpl vessel_id=6581 method=addCapability accessLevel=6
Class=XenHypervisorDbImpl vessel_id=6581 method=addCapability accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=removeAllNtpServers accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=addNtpServer accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=addNtpServer accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=addNtpServer accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setStatisticInterval accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=lock accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setProductName accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setManufacturer accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setProductSerialNumber accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setSimpleName accessLevel=6
Class=InternalPortDbImpl vessel_id=6535 method=setSimpleName accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setMemory accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setProcessorSpeed accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setNoExecuteFlag accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setNumberOfThreadsPerCore accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setNumberOfProcessorSockets accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setNumberOfCoresPerProcessorSocket accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setNumberOfProcessorCores accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setNumberOfEnabledProcessorCores accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setNumberOfPopulatedProcessorSockets accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=createProcessor accessLevel=6
Class=ProcessorDbImpl vessel_id=6587 method=setName accessLevel=6
Class=ProcessorDbImpl vessel_id=6587 method=setFoundryContext accessLevel=6
Class=ProcessorDbImpl vessel_id=6587 method=onPersistableCreate accessLevel=6
Class=ProcessorDbImpl vessel_id=6587 method=setLifecycleState accessLevel=6
Class=ProcessorDbImpl vessel_id=6587 method=setRollbackLifecycleState accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=createProcessor accessLevel=6
Class=ProcessorDbImpl vessel_id=6593 method=setName accessLevel=6
Class=ProcessorDbImpl vessel_id=6593 method=setFoundryContext accessLevel=6
Class=ProcessorDbImpl vessel_id=6593 method=onPersistableCreate accessLevel=6
Class=ProcessorDbImpl vessel_id=6593 method=setLifecycleState accessLevel=6
Class=ProcessorDbImpl vessel_id=6593 method=setRollbackLifecycleState accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=createProcessor accessLevel=6
Class=ProcessorDbImpl vessel_id=6598 method=setName accessLevel=6
Class=ProcessorDbImpl vessel_id=6598 method=setFoundryContext accessLevel=6
Class=ProcessorDbImpl vessel_id=6598 method=onPersistableCreate accessLevel=6
Class=ProcessorDbImpl vessel_id=6598 method=setLifecycleState accessLevel=6
Class=ProcessorDbImpl vessel_id=6598 method=setRollbackLifecycleState accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=createProcessor accessLevel=6
Class=ProcessorDbImpl vessel_id=6603 method=setName accessLevel=6
Class=ProcessorDbImpl vessel_id=6603 method=setFoundryContext accessLevel=6
Class=ProcessorDbImpl vessel_id=6603 method=onPersistableCreate accessLevel=6
Class=ProcessorDbImpl vessel_id=6603 method=setLifecycleState accessLevel=6
Class=ProcessorDbImpl vessel_id=6603 method=setRollbackLifecycleState accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setBIOSReleaseDate accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setBIOSVendor accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setBIOSVersion accessLevel=6
Class=ProcessorDbImpl vessel_id=6587 method=setFamily accessLevel=6
Class=ProcessorDbImpl vessel_id=6587 method=setManufacturer accessLevel=6
Class=ProcessorDbImpl vessel_id=6587 method=setLevelOneCacheSize accessLevel=6
Class=ProcessorDbImpl vessel_id=6587 method=setLevelTwoCacheSize accessLevel=6
Class=ProcessorDbImpl vessel_id=6587 method=setLevelThreeCacheSize accessLevel=6
Class=ProcessorDbImpl vessel_id=6593 method=setFamily accessLevel=6
Class=ProcessorDbImpl vessel_id=6593 method=setManufacturer accessLevel=6
Class=ProcessorDbImpl vessel_id=6593 method=setLevelOneCacheSize accessLevel=6
Class=ProcessorDbImpl vessel_id=6593 method=setLevelTwoCacheSize accessLevel=6
Class=ProcessorDbImpl vessel_id=6593 method=setLevelThreeCacheSize accessLevel=6
Class=ProcessorDbImpl vessel_id=6598 method=setFamily accessLevel=6
Class=ProcessorDbImpl vessel_id=6598 method=setManufacturer accessLevel=6
Class=ProcessorDbImpl vessel_id=6598 method=setLevelOneCacheSize accessLevel=6
Class=ProcessorDbImpl vessel_id=6598 method=setLevelTwoCacheSize accessLevel=6
Class=ProcessorDbImpl vessel_id=6598 method=setLevelThreeCacheSize accessLevel=6
Class=ProcessorDbImpl vessel_id=6603 method=setFamily accessLevel=6
Class=ProcessorDbImpl vessel_id=6603 method=setManufacturer accessLevel=6
Class=ProcessorDbImpl vessel_id=6603 method=setLevelOneCacheSize accessLevel=6
Class=ProcessorDbImpl vessel_id=6603 method=setLevelTwoCacheSize accessLevel=6
Class=ProcessorDbImpl vessel_id=6603 method=setLevelThreeCacheSize accessLevel=6
Class=ProcessorDbImpl vessel_id=6587 method=setFlags accessLevel=6
Class=ProcessorDbImpl vessel_id=6587 method=setModelName accessLevel=6
Class=ProcessorDbImpl vessel_id=6587 method=setVendorId accessLevel=6
Class=ProcessorDbImpl vessel_id=6587 method=setCpuFamily accessLevel=6
Class=ProcessorDbImpl vessel_id=6587 method=setCpuModel accessLevel=6
Class=ProcessorDbImpl vessel_id=6593 method=setFlags accessLevel=6
Class=ProcessorDbImpl vessel_id=6593 method=setModelName accessLevel=6
Class=ProcessorDbImpl vessel_id=6593 method=setVendorId accessLevel=6
Class=ProcessorDbImpl vessel_id=6593 method=setCpuFamily accessLevel=6
Class=ProcessorDbImpl vessel_id=6593 method=setCpuModel accessLevel=6
Class=ProcessorDbImpl vessel_id=6598 method=setFlags accessLevel=6
Class=ProcessorDbImpl vessel_id=6598 method=setModelName accessLevel=6
Class=ProcessorDbImpl vessel_id=6598 method=setVendorId accessLevel=6
Class=ProcessorDbImpl vessel_id=6598 method=setCpuFamily accessLevel=6
Class=ProcessorDbImpl vessel_id=6598 method=setCpuModel accessLevel=6
Class=ProcessorDbImpl vessel_id=6603 method=setFlags accessLevel=6
Class=ProcessorDbImpl vessel_id=6603 method=setModelName accessLevel=6
Class=ProcessorDbImpl vessel_id=6603 method=setVendorId accessLevel=6
Class=ProcessorDbImpl vessel_id=6603 method=setCpuFamily accessLevel=6
Class=ProcessorDbImpl vessel_id=6603 method=setCpuModel accessLevel=6
Class=CpuCompatibilityGroupDbImpl vessel_id=6608 method=setName accessLevel=6
Class=CpuCompatibilityGroupDbImpl vessel_id=6608 method=setFoundryContext accessLevel=6
Class=CpuCompatibilityGroupDbImpl vessel_id=6608 method=onPersistableCreate accessLevel=6
Class=CpuCompatibilityGroupDbImpl vessel_id=6608 method=setLifecycleState accessLevel=6
Class=CpuCompatibilityGroupDbImpl vessel_id=6608 method=setRollbackLifecycleState accessLevel=6
Class=CpuCompatibilityGroupDbImpl vessel_id=6608 method=setSimpleName accessLevel=6
Class=CpuCompatibilityGroupDbImpl vessel_id=6608 method=addServer accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setCpuCompatibilityGroup accessLevel=6
Class=CpuCompatibilityGroupDbImpl vessel_id=6608 method=addServer accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=createStorageInitiator accessLevel=6
Class=IscsiStorageInitiatorDbImpl vessel_id=6613 method=setName accessLevel=6
Class=IscsiStorageInitiatorDbImpl vessel_id=6613 method=setFoundryContext accessLevel=6
Class=IscsiStorageInitiatorDbImpl vessel_id=6613 method=onPersistableCreate accessLevel=6
Class=IscsiStorageInitiatorDbImpl vessel_id=6613 method=setLifecycleState accessLevel=6
Class=IscsiStorageInitiatorDbImpl vessel_id=6613 method=setRollbackLifecycleState accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=lock accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=createNetworkPort accessLevel=6
Class=EthernetPortDbImpl vessel_id=6619 method=setName accessLevel=6
Class=EthernetPortDbImpl vessel_id=6619 method=setFoundryContext accessLevel=6
Class=EthernetPortDbImpl vessel_id=6619 method=onPersistableCreate accessLevel=6
Class=PortDownEventDbImpl vessel_id=6625 method=notify accessLevel=6
Class=EthernetPortDbImpl vessel_id=6619 method=setLifecycleState accessLevel=6
Class=EthernetPortDbImpl vessel_id=6619 method=setRollbackLifecycleState accessLevel=6
Class=EthernetPortDbImpl vessel_id=6619 method=setSimpleName accessLevel=6
Class=EthernetPortDbImpl vessel_id=6619 method=setNumber accessLevel=6
Class=EthernetPortDbImpl vessel_id=6619 method=setServer accessLevel=6
Class=EthernetPortDbImpl vessel_id=6619 method=setInterfaceName accessLevel=6
Class=EthernetPortDbImpl vessel_id=6619 method=setMediaAccessControlAddress accessLevel=6
Class=EthernetPortDbImpl vessel_id=6619 method=setMediaTransferUnit accessLevel=6
Class=EthernetPortDbImpl vessel_id=6619 method=setDetails accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=createNetworkPort accessLevel=6
Class=EthernetPortDbImpl vessel_id=6627 method=setName accessLevel=6
Class=EthernetPortDbImpl vessel_id=6627 method=setFoundryContext accessLevel=6
Class=EthernetPortDbImpl vessel_id=6627 method=onPersistableCreate accessLevel=6
Class=PortDownEventDbImpl vessel_id=6632 method=notify accessLevel=6
Class=EthernetPortDbImpl vessel_id=6627 method=setLifecycleState accessLevel=6
Class=EthernetPortDbImpl vessel_id=6627 method=setRollbackLifecycleState accessLevel=6
Class=EthernetPortDbImpl vessel_id=6627 method=setSimpleName accessLevel=6
Class=EthernetPortDbImpl vessel_id=6627 method=setNumber accessLevel=6
Class=EthernetPortDbImpl vessel_id=6627 method=setServer accessLevel=6
Class=EthernetPortDbImpl vessel_id=6627 method=setInterfaceName accessLevel=6
Class=EthernetPortDbImpl vessel_id=6627 method=setMediaAccessControlAddress accessLevel=6
Class=EthernetPortDbImpl vessel_id=6627 method=setMediaTransferUnit accessLevel=6
Class=EthernetPortDbImpl vessel_id=6627 method=setDetails accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=createNetworkPort accessLevel=6
Class=BondPortDbImpl vessel_id=6634 method=setName accessLevel=6
Class=BondPortDbImpl vessel_id=6634 method=setFoundryContext accessLevel=6
Class=BondPortDbImpl vessel_id=6634 method=onPersistableCreate accessLevel=6
Class=PortDownEventDbImpl vessel_id=6641 method=notify accessLevel=6
Class=BondPortDbImpl vessel_id=6634 method=setLifecycleState accessLevel=6
Class=BondPortDbImpl vessel_id=6634 method=setRollbackLifecycleState accessLevel=6
Class=BondPortDbImpl vessel_id=6634 method=setSimpleName accessLevel=6
Class=BondPortDbImpl vessel_id=6634 method=setNumber accessLevel=6
Class=BondPortDbImpl vessel_id=6634 method=setServer accessLevel=6
Class=BondPortDbImpl vessel_id=6634 method=addJobOperation accessLevel=6
Class=BondPortDbImpl vessel_id=6634 method=setInterfaceName accessLevel=6
Class=BondPortDbImpl vessel_id=6634 method=setInternetProtocolAddress accessLevel=6
Class=BondPortDbImpl vessel_id=6634 method=setNetmask accessLevel=6
Class=BondPortDbImpl vessel_id=6634 method=setAddressType accessLevel=6
Class=BondPortDbImpl vessel_id=6634 method=addEthernetPort accessLevel=6
Class=EthernetPortDbImpl vessel_id=6619 method=setBondPort accessLevel=6
Class=BondPortDbImpl vessel_id=6634 method=setMediaAccessControlAddress accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=setManagementMediaAccessControlAddress accessLevel=6
Class=EthernetNetworkDbImpl vessel_id=2837 method=addNetworkPort accessLevel=6
Class=BondPortDbImpl vessel_id=6634 method=setNetworkPortGroup accessLevel=6
Class=BondPortDbImpl vessel_id=6634 method=setJobAsset accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=lock accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=addPlugin accessLevel=6
Class=FileSystemPluginDbImpl vessel_id=2878 method=addServer accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=addPlugin accessLevel=6
Class=StorageArrayPluginDbImpl vessel_id=2843 method=addServer accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=addPlugin accessLevel=6
Class=FileSystemPluginDbImpl vessel_id=2872 method=addServer accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=createLocalFileServer accessLevel=6
Class=LocalFileServerDbImpl vessel_id=6644 method=setName accessLevel=6
Class=LocalFileServerDbImpl vessel_id=6644 method=setFoundryContext accessLevel=6
Class=LocalFileServerDbImpl vessel_id=6644 method=onPersistableCreate accessLevel=6
Class=LocalFileServerDbImpl vessel_id=6644 method=setLifecycleState accessLevel=6
Class=LocalFileServerDbImpl vessel_id=6644 method=setRollbackLifecycleState accessLevel=6
Class=LocalFileServerDbImpl vessel_id=6644 method=setStoragePlugin accessLevel=6
Class=FileSystemPluginDbImpl vessel_id=2878 method=addStorageServer accessLevel=6
Class=LocalFileServerDbImpl vessel_id=6644 method=setAdminHostname accessLevel=6
Class=LocalFileServerDbImpl vessel_id=6644 method=setAdminUsername accessLevel=6
Class=LocalFileServerDbImpl vessel_id=6644 method=setAdminPassword accessLevel=6
Class=LocalFileServerDbImpl vessel_id=6644 method=setSimpleName accessLevel=6
Class=LocalFileServerDbImpl vessel_id=6644 method=setServer accessLevel=6
Class=LocalFileServerDbImpl vessel_id=6644 method=setSimpleName accessLevel=6
Class=LocalFileServerDbImpl vessel_id=6644 method=setValidated accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=lock accessLevel=6
Class=ServerDbImpl vessel_id=6521 method=createLocalStorageArray accessLevel=6
Class=LocalStorageArrayDbImpl vessel_id=6649 method=setName accessLevel=6
Class=LocalStorageArrayDbImpl vessel_id=6649 method=setFoundryContext accessLevel=6
Class=LocalStorageArrayDbImpl vessel_id=6649 method=onPersistableCreate accessLevel=6
Class=LocalStorageArrayDbImpl vessel_id=6649 method=setLifecycleState accessLevel=6
Class=LocalStorageArrayDbImpl vessel_id=6649 method=setRollbackLifecycleState accessLevel=6
Class=LocalStorageArrayDbImpl vessel_id=6649 method=setStoragePlugin accessLevel=6
Class=StorageArrayPluginDbImpl vessel_id=2843 method=addStorageServer accessLevel=6
Class=LocalStorageArrayDbImpl vessel_id=6649 method=setValidated accessLevel=6
Class=LocalStorageArrayDbImpl vessel_id=6649 method=setSimpleName accessLevel=6
Class=LocalStorageArrayDbImpl vessel_id=6649 method=createVolumeGroup accessLevel=6
Class=VolumeGroupDbImpl vessel_id=6655 method=setName accessLevel=6
Class=VolumeGroupDbImpl vessel_id=6655 method=setFoundryContext accessLevel=6
Class=VolumeGroupDbImpl vessel_id=6655 method=onPersistableCreate accessLevel=6
Class=VolumeGroupDbImpl vessel_id=6655 method=setLifecycleState accessLevel=6
Class=VolumeGroupDbImpl vessel_id=6655 method=setRollbackLifecycleState accessLevel=6
Class=VolumeGroupDbImpl vessel_id=6655 method=setStorageArray accessLevel=6
Class=VolumeGroupDbImpl vessel_id=6655 method=setSimpleName accessLevel=6
Class=StorageElementDbImpl vessel_id=6660 method=setName accessLevel=6
Class=StorageElementDbImpl vessel_id=6660 method=setFoundryContext accessLevel=6
Class=StorageElementDbImpl vessel_id=6660 method=onPersistableCreate accessLevel=6
Class=StorageElementDbImpl vessel_id=6660 method=setLifecycleState accessLevel=6
Class=StorageElementDbImpl vessel_id=6660 method=setRollbackLifecycleState accessLevel=6
Class=StorageElementDbImpl vessel_id=6660 method=setPage83Id accessLevel=6
Class=StorageElementDbImpl vessel_id=6660 method=setVolumeGroup accessLevel=6
Class=VolumeGroupDbImpl vessel_id=2856 method=addStorageElement accessLevel=6
Class=StorageElementDbImpl vessel_id=6660 method=setVendor accessLevel=6
Class=StorageElementDbImpl vessel_id=6660 method=setUserFriendlyName accessLevel=6
Class=StorageElementDbImpl vessel_id=6660 method=setSimpleName accessLevel=6
Class=StorageElementDbImpl vessel_id=6660 method=setSize accessLevel=6
Class=StorageElementDbImpl vessel_id=6660 method=setStorageElementType accessLevel=6
Class=InternalJobDbImpl vessel_id=6511 method=setFailedOperation accessLevel=6
Class=DiscoverManagerDbImpl vessel_id=165 method=nextJobOperation accessLevel=6
Completed Step: ROLLBACK
Job failed commit (internal) due to OVMAPI_6055E Discover target: ovm1, Discover failed with error: java.lang.NullPointerException
at com.oracle.ovm.mgr.discover.ovm.ServerPhysicalLunDiscoverHandler.sanAddMissingStoragePath(ServerPhysicalLunDiscoverHandler.java:371)
at com.oracle.ovm.mgr.discover.ovm.ServerPhysicalLunDiscoverHandler.sanDiskProcess(ServerPhysicalLunDiscoverHandler.java:243)
at com.oracle.ovm.mgr.discover.ovm.ServerPhysicalLunDiscoverHandler.process(ServerPhysicalLunDiscoverHandler.java:195)
at com.oracle.ovm.mgr.discover.ovm.DiscoverHandler.execute(DiscoverHandler.java:55)
at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:442)
at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:427)
at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:412)
at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDefaultDiscover(DiscoverEngine.java:381)
at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverNewServer(DiscoverEngine.java:360)
at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverServer(DiscoverEngine.java:272)
at com.oracle.ovm.mgr.op.manager.DiscoverManagerServerDiscover.action(DiscoverManagerServerDiscover.java:48)
at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:193)
at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:264)
at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1090)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:247)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:207)
at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:751)
at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:401)
at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:459)
at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
at java.lang.Thread.run(Thread.java:662)
Thu Jan 19 16:35:04 CET 2012
com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_6055E Discover target: ovm1, Discover failed with error: java.lang.NullPointerException
at com.oracle.ovm.mgr.discover.ovm.ServerPhysicalLunDiscoverHandler.sanAddMissingStoragePath(ServerPhysicalLunDiscoverHandler.java:371)
at com.oracle.ovm.mgr.discover.ovm.ServerPhysicalLunDiscoverHandler.sanDiskProcess(ServerPhysicalLunDiscoverHandler.java:243)
at com.oracle.ovm.mgr.discover.ovm.ServerPhysicalLunDiscoverHandler.process(ServerPhysicalLunDiscoverHandler.java:195)
at com.oracle.ovm.mgr.discover.ovm.DiscoverHandler.execute(DiscoverHandler.java:55)
at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:442)
at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:427)
at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:412)
at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDefaultDiscover(DiscoverEngine.java:381)
at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverNewServer(DiscoverEngine.java:360)
at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverServer(DiscoverEngine.java:272)
at com.oracle.ovm.mgr.op.manager.DiscoverManagerServerDiscover.action(DiscoverManagerServerDiscover.java:48)
at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:193)
at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:264)
at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1090)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:247)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:207)
at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:751)
at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:401)
at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:459)
at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
at java.lang.Thread.run(Thread.java:662)
Thu Jan 19 16:35:04 CET 2012
at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:457)
at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:427)
at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:412)
at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDefaultDiscover(DiscoverEngine.java:381)
at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverNewServer(DiscoverEngine.java:360)
at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverServer(DiscoverEngine.java:272)
at com.oracle.ovm.mgr.op.manager.DiscoverManagerServerDiscover.action(DiscoverManagerServerDiscover.java:48)
at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:193)
at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:264)
at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1090)
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:597)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:247)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:207)
at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:751)
at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:401)
at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:459)
at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
at java.lang.Thread.run(Thread.java:662)
End of Job
If anyone have any suggestions... ?
Thank you,
Yacine

Similar Messages

ASM, rebalancing, 3rd party storage and performance

Hi all, I have some questions for the storage experts and I need your opinion about:
1. Which type of ASM is better for the rebalancing perspective (and obviously the performance perspective), but considering the availability as well: Unprotected, 2-way (normal) or 3-way (high)? I know 3-way is the worst because we have to multiply by 3 the space of the database, but has great availability. Which of these do you use in your company?
2. If someone is using EMC/Fujitsu/Hitachi, do you use Unprotected or 2-way (normal) in ASM?
3. Which type of rebalancing (from zero to 11) is the best to use, considering the overall performance , I mean, when you have to add a new disk, ASm will perform the rebalancing.
4. Which is better to use: ASM Cluster File System or Oracle Cluster File System ?
Thanks.

977623 wrote:
1. Which type of ASM is better for the rebalancing perspective (and obviously the performance perspective), but considering the availability as well: Unprotected, 2-way (normal) or 3-way (high)? I know 3-way is the worst because we have to multiply by 3 the space of the database, but has great availability. Which of these do you use in your company?Wrong question IMO. You do not choose normal or high redundancy based on which rebalances the fastest. You make that choice wrt to redundancy and high availability.
The best in this respect is high redundancy. 3 storage servers. Fully redundant I/O fabric layer (3+ I/O paths from each server to each and every LUN). Which means you can loose 2 storage arrays and most of your I/O fabric layer (switches and cables). And the storage layer left will still be able to be effectively used for ASM and the RAC database will not even notice that this destruction happened.
However, this best is not always feasible ito existing architecture, budget and so on. So that drives the requirements and needs and what the best is to meet that.
2. If someone is using EMC/Fujitsu/Hitachi, do you use Unprotected or 2-way (normal) in ASM?That again depends on redundancy levels. If the SAN provides a RAID5 or RAID10 LUN, should you mirror it?
This may makes sense if you have 2 SANS. And with each SAN implementing RAID5, you mirror (via ASM) across SANs.
It makes less sense if you use ASM to mirror (on the same SAN) 2 RAID5 LUNs.
You also may have no choice. For example, migrating a high redundancy diskgroup from a storage server (no redundancy by server), to a SAN (RAID5/10 redundancy by SAN). When migrating ASM diskgroups, you cannot reduce redundancy. You cannot make a high redundancy diskgroup a normal redundancy diskgroup. Or a normal one, an externally redundant diskgroup.
In such a case you normal/high redundancy diskgroup on the new SAN (with its RAID5/10 LUNs), still need its own mirrors in ASM.
3. Which type of rebalancing (from zero to 11) is the best to use, considering the overall performance , I mean, when you have to add a new disk, ASm will perform the rebalancing.How busy is the I/O layer? What production processing is running? How will this be impacted by using power 11? How soon does the old (dropped) disks need to be physically decommissioned? Etc.
There is no single correct answer to what load balancing power setting to use.
4. Which is better to use: ASM Cluster File System or Oracle Cluster File System ?For what purpose?
For RAC database purposes only? ACFS. As OCFS adds another set of kernel drivers, kernel services, and another Interconnect (ocfs needs its own IP Interconnect that is typically run over the public IP network of the cluster, and that can be/should be run over the private IP network of the cluster).
Why add more moving parts (ocfs) when ACFS is available?
Then again - why use ACFS when you are not running Grid Infrastructure? Or why makes your cluster file system dependent on Grid/CRS to be running (with ASM), when OCFS's moving parts are significantly fewer and less complex?
As with most things in Information Technology - there is no overall "best". The "best" depends on a number of factors, and the business requirements that need to be met.

3rd Party RAID Card options - must make a decision

I've been on the Mac with NLE for high end corporate work since early 90's but only now moving from a 10 bit uncompressed SD edit suite to FCP and I need your valued feedback for a Mac Pro arriving soon. I've spent hours poring over all forums, Apple and otherwise, to select the right raid solution. The situation is that we will edit NTSC into 2009 and make the transition to HD later in the year. So, the initial set-up will be three 1 TB Seagate 7200.11's with a 320GB for O/S (and perhaps more in optical bay for scratch, etc.) I prefer to install the three video drives internally and go with a hardware driven card (Raid 5) that also provides support for external drives if we add later. Caldigit's is the only card that appears to cover all the misc. requirements but the forums list issues with 3rd party storage vs Caldigit's box. Other cards have pros and cons so I'm asking you to tell me what is working in your shop and also whether I should just purchase a 3rd party external enclosure and set up the Seagates there. If so, card recommendation is also critical.

Hi,
I find installing a RAID 5 inside the Mac Pro has too many limitations. I would rather keep the boot drive in its own internal bay and be able to mount a boot camp disk or other backup disks internally when needed.
A better solution for most users is to mount the RAID 5 externally. The FirmTek SeriTek/5PM enclosure and the HighPoint RocketRAID 2314 combination provides a high quality external RAID 5 solution that is quiet, fast and dependable. You can learn more about it here:
http://www.amug.org/amug-web/html/amug/reviews/articles/firmtek/5pm/
http://www.firmtek.com/seritek/seritek-5pm/
http://www.amug.org/amug-web/html/amug/reviews/articles/highpoint/2314/
http://www.amazon.com/exec/obidos/ASIN/B000NAXGIU/arizomacinusergr
There are other solutions that work well too. However, the controllers tend to be much more expensive. RAID 5 users looking for a quality solution at a very reasonable price will find the SeriTek/5PM and RR2314 combination works well.
If you don't mind paying more the Areca ARC-1680ix-12 SAS controller reviewed by AMUG is another high performance option that works well with SATA direct connect enclosures. You can read more about it here:
http://www.amug.org/amug-web/html/amug/reviews/articles/areca/1680ix12/
Have fun!

Service desk integration with 3rd party tool

Hi all,
I've problems understanding the setup of connecting a 3rd party service desk tool with solman itsm.
So far it's clear that I need to activate and configure the service provider and consumer in soamanager.
The webservice then will be called by the 3rd party tool with corresponding data.
However, according to spro I need to define a value mapping for incoming/outgoing calls.
I do not understand this mapping... the WSDL of webservice ICT_SERVICE_DESK_API contains lots of fields, but in spro -> value mapping I can only define the following fields (which are hard coded in type pool AIICT):
SAPCategory
SAPComponent
SAPDatabase
SAPFrontend
SAPIncidentID
SAPIncidentStatus
SAPInstNo
SAPOperatingSystem
SAPSoftwareComponent
SAPSoftwareComponentPatch
SAPSoftwareComponentRelease
SAPSubject
SAPSystemClient
SAPSystemID
SAPSystemType
SAPUserStatus
What about attachments, priority etc.?
Will the interface parameters mapped to these ones?
For what purpose do I need to maintain the value mapping?
Can you give me a hint?
Regards, Richard Pietsch

can you please check the WIKI Solution manager Service Desk Integration with third party service desk - SAP Solution Manager - Security and Authorizat…

3rd party adapter integration into XI

Dear Experts
I wanted to know how 3rd party adapters are integrated into XI?

Hi Dheer,
There many third party adapters available in market.
One example is seeburger:
U need to follow the below steps for integration into XI:
For the same requirement you need to follow the below steps:
1) First deploye the Std seeburger mapping provided by see burger on XI
2) If you are using the AS2 adapter then you have to install the AS2 server on XI server.
3) Once you install the std seeburger on SAP XI server you will see the AS2,X400,OFTPS,VAN adapter on XI ID.
5) You need to call the std mapping in the adapter module which does the conversion from EDI to XML and XML to EDI.
if u need process then let me know I will send u the configuration threads which is required for integration.
EDI Adapter by SeeBurger
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/206e2b65-2ca8-2a10-edad-f2d1391644cb
B2B(EDI) Integration using SAP Netweaver XI and Seeburger AS2 Adapter
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00f9cdf5-d812-2a10-03b4-aff3bbf792bf
Integrating XI with SeeBurger
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6dc02f5d-0601-0010-cd9d-f4ff9a7e8c33
Brief about seeburger:
Seeburger adapters like OFTPS,AS2,X400 are used for B2B scenario where the file is coming through WAn network or mailbox. As XI dont have capability to convert the EDIFACT format file to XML the same work will be done by seeburger adapters.
The SEEBURGER Business Integration Converter (BIC) is an any-to-any format converter, used to translate EDI data and legacy data formats into XML and vice versa. It can also be used for complex, high performance XML-to-XML mappings or to interface to existing JDBC data sources.
Supported EDI formats include:
ANSI
EDIFACT
INHOUSE
IDOC
XML Schema
XML DTD
CSV
Delimited Data
positional data
SWIFT
EANCOM
and many more.
See for converting the EDI XML to EDI and XML-EDI you need to have a seeburger mapping program at the adapter module which does the conversion. For this module you need a BIC tool of seeburger which provides the different module program for EDI to XML and XML-EDI. This program needs to be deployed on XI and through adapter it has to be called for conversion.
refer belwo weblog:
/people/nithiyanandam.au2/blog/2008/02/20/handling-edi-interfaces-using-seeburger-bic-modules
Thnx
Chirag
Edited by: Chirag Gohil on Feb 25, 2008 12:51 PM

3rd Party Search Engine Integration - some property not rendering

Hi,
I have tried to integrate a 3rd Party Search Engine into TREX following the published example.
I have successfully integrated and search results from the 3rd party engine are showing up.
However, some properties like cm_description, cm_contentlength, cm_modifedby are not rendering; their value are null; the search layout are specified correctly.
I only managed to set
1) cm_displayname
2) cm_contenttype
3) cm_id
and are showing up.
The setting of the rest of the properties are done in the same way and put into the propertymap.
Any idea why are the not rendering?? Any help appreciated. Thanks!

Hello Thilo,
I tried to deploy the original package com.customer.search.par, but unfortunately I got also an error with this package.
The disadvantage is, that I don't get an error message during start-up in one of the logger - for cause analysis.
I got the following error message within KM:
java.lang.NullPointerException
     at com.sapportals.wcm.repository.runtime.CmSystem.getResourceImpl (CmSystem.java:774)
     at com.sapportals.wcm.repository.runtime.CmSystem.getResource (CmSystem.java:325)
     at com.sapportals.wcm.repository.runtime.CmAdapter.getResource (CmAdapter.java:81)
     at com.sapportals.wcm.portal.service.KMServiceImpl.afterInit (KMServiceImpl.java:260)
     at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstanceStep2(PortalServiceItem.java:736)
What can I do at this point?
Best regards,
Walter

3rd Party Web Service Integration

I am a complete beginner with SAP Process Integration. I could do with a simple 'To Do' List on what I should do and in what order to do it so that I can 'talk' to external 3rd party web service. In a nutshell, I will be using 3rd party web service to create document for eventual printing, so I will need to populate XML with various database fields. I have been provided with the WSDL files for the web service.
Appreciate any help, o matter how small.

Hi Huw,
Please have a look at the following links and see if it helps you.
Re: communicating with a 3rd party system using webservices
calling external web service from ABAP Program
Re: Web service & Soap adapter Examples
Best Regards

Integration with with 3rd Party Document management System

Hi
We are implementing Invoice Management in SAP, using the Opentext VIM ECC Addon.
The Customer has a 3rd Party Document Management System called DocHarbour which is NOT Archivelink enabled.
The process flow is that Invoices will be scanned and available in a share drive somewhere.
Using SAP and Invoice Management Work, we would like to attached these documents to the relevant SAP Documents, and then post them to the 3rd Party Doc Management System , but the Images must be retreival in SAP at any time .
Everything tells me the 3rd party Doc Management System needs to be ArchiveLink enabled for this work.
Is anyone able to shed any light on this issue , provide possible solutions , workarounds or infor ?
Any help or information appreciated.
Thanks in advance.

Dear Minesh
My suggestion would be use SAP Content server provided by SAP as is easily available and easy to setup.
Doing Integration with third party involves much time and efforts.
Client always thinks of Moon. Always show him his city.
With Regards
Mangesh Pande

1) Is there North Bound Interface / API from SAP Solution Manager available for 3rd party integration? i. The list of the modules that are being managed by SAP Solution Manager(s) ii. The performance metrics of those modules/components at th

1)
Is there North Bound Interface / API from SAP Solution Manager available for 3rd party integration?
i. The list of the modules that are being managed by SAP Solution Manager(s)
ii. The performance metrics of those modules/components at the high level
iii. The information about Early Watch Alerts (or situations to watch for)
2)
Is there a full SNMP interface for getting the above information from SAP Solution Manager?
3)
Is that understanding that SAP has SNMP support for forwarding alerts to a 3rd party system, correct?
4)
Does SAP has both free and licensed? If yes then what are the advantages of licensed over the open/free version?

Mugunthan
Yes we have applied 11i.AZ.H.2. I am getting several errors still that we trying to resolve
One of them is
===========>>>
Uploading snapshot to central instance failed, with 3 different messages
Error: An invalid status '-1' was passed to fnd_concurrent.set_completion_status. The valid statuses are: 'NORMAL', 'WARNING', 'ERROR'FND at oracle.apps.az.r12.util.XmlTransmorpher.<init>(XmlTransmorpher.java:301)
 at oracle.apps.az.r12.extractor.cpserver.APIExtractor.insertGenericSelectionSet(APIExtractor.java:231)
please assist.
regards
girish

3rd party payment integration with ADF application

Hi ADF experts,
We have a requirement to integrate our ADF application with 3rd party payment gateway.
For this we have created 2 servlets(one to post data, and one for relay response) which will talk to payment gateway.
Since we are using servelts, we wont have access to bindings or any of ADF features. We manage the handshake between servlets and ADF app by passing data through session variables.
I am not happy with this solution, even though it works in our test environment. I would prefer a complete ADF soultion rather than using servelts/jsps.
Is there a standard way(either inbuilt in ADF or extensions) to integrate 3rd party gateway with ADF application which is safe and secure?
Jdev used: 11.1.1.1.5
Payment gateway used: authorize.net
thanks
-Venkat

You can access adf application module from a servlet. All you have to do its to setup a pagedef for the servlet.Check out my blog http://tompeez.wordpress.com/2011/12/16/jdev11-1-2-1-0-handling-imagesfiles-in-adf-part-3/ Which shows how to do this.
I'm not aware of standard integration to a payment service.
Timo

3rd party integration: How to get XML Schema (.xsd) for a custom entity, to use with a mapper

Is there an easy way to get the xml schema/DTD for a custom entity, specifically an .XSD file for that entity (which will then be used to create a map to be able to transform the fields of the entity to a 3rd-party message format)?
So have a custom entity with lots and lots of fields. Each of the fields will map to a differently named field to match the schema of the 3rd party entity. A very common situation. Looking to use a tool like the Biztalk mapper or Altova's MapForce to generate
an .xslt file to transform the downloaded entity (service.Retrieve with all columns) to the new format. (Will implement a typical VETR pattern.)
Apparently with CRM 4 there was a call that provided this, but from 2011 has not been available. Working with a crm 2015 system.

That will give a descriptor of the table and allow creation of an .XSD file, but it's really complex in terms of types, and the there's type conversion. It might be an easy way to get a schema, with the downside being it's hard to use that schema.
It seems easier to do a fetch of the record with all fields filled in using service.Retrieve, and then converting this to xml, using Microsoft's guidance leads to using https://msdn.microsoft.com/en-us/library/hh675409.aspx which will serialize the entity
into XML with all the fields converted to type string, and with complex fields likewise converted to strings with additional information about the type.
Using this it's possible using an number of tools to create an easier to use .XSD file.
However, it would seem most integrations of this type are using 3rd party CRM connectors. Perhaps this is why Microsoft hasn't provided anything direct (and took away what they did have in crm4.0 due to it generating a hard to use .XSD or due to letting
their partners continue income streams from selling connectors").
But without using 3rd party connectors, or following the still tedious method of generating .XSD (a useable .xsd), have not yet come up with an easy, automatic way to get an .XSD or to easily integrate with 3rd party message format.

Enabling iPod Touch to be a storage device - optimal 3rd party application

The ONLY disappointment I have had with my beloved iPod Touch 32 is that it is the ONLY iPod not recognised by Windows or Mac OS as a storage device!!
In fact I only chose the 32GB version for that expected benefit - my dealer was shocked when I discovered this stupid limitation and offered to give me my money back!
I understand there are a couple of 3rd party applications that enable the Touch to be recognised as a storage device (to do daily file backups).
Has anyone had any experience with any of these apps? Which is optimal (simple, reliable and unlikely to cause software conflicts that mess up the reliability of the Touch?)
I am running firmware version 3.0 (happily).
Thanks for your time,
Simon.

It is ridiculous that the iPod Touch cannot mount as a device enabling use of free space for data storage. 3rd party apps are now addressing this limitation.

User-Exit / Badi / BTE for STWB_WORK for integrating 3rd party tool

Hi,
I need a user-exit / badi / BTE for the transaction STWB_WORK user test worklist. I'm trying to integrate a 3rd party tool to this transaction. When a worklist from this transaction is selected, i'll run the 3rd party tool executable from abap coding in the user-exit/badi/bte. Can anybody help me find one?
thanks,
Venky

Hello Venky,
I saw your question in sdn and I am wondering, if you got a solution for your question.
I will be very happy, if you can help me you. I have the same problem as you.
cu Manfred

Web Crawler development or 3rd Party web crawler integration in portal

Hi Experts,
I am working on eCommerce based applications using SAP CRM. Web Crawler in XCM is not working as expected like publishing the content to search engines, indexing the product or catalog information etc.
Is there anyway we can integrate 3rd Party Web Crawlers with SAP CRM or XCM application.
Please let me know your inputs at the earliest.
Thanks,
Madhan

Hi Madhan,
we're facing the same issue, did you have any hints about that?
many thanks
BR
Roberto

Using Weblogic LDAP JAAS credentials for 3rd party authentication

Hello to all!
I'm posting this question because I'm developing a software layer that will connect a weblogic based web application, with LDAP authentication, to a 3rd party application, also with LDAP authentication, and I'm having difficulties in getting a javax.security.auth.Subject object from the weblogic server.
I already have a way of doing it, but it requires that a username and a password exist in some sort of storage, in order to work (either hardcoded (which is to be avoided as much as possible) or stored in a file (which is to be avoided if possible, but if nothing better exists...)).
I'm using a Weblogic 11g server, with LDAP authentication (LDAP provider placed in last at the provider list, with flag SUFFICIENT) and I'm developing the software layer using Oracle's jDeveloper 11g Release 1.
Now, this 3rd party application requires a javax.security.auth.Subject object in order to perform authentication.
How do I get this from the weblogic server ?
Of the following approaches, can you tell me which are the most correct ones ?
<ul>
a)
 LoginContext lc = null;
 try {
 lc = new LoginContext("<JAAS instance name>");
 lc.login();
 } catch (LoginException e) {
 e.printStackTrace();
 javax.security.auth.Subject subject = lc.getSubject();

</ul>
<ul>
b)
 LoginContext lc = new LoginContext("<JAAS instance name>"
 new MyClass.CallbackHandler(userid, password));
 lc.login();
 javax.security.auth.Subject subject = lc.getSubject();
 javax.security.auth.Subject.doAs(subject, myClassObject);

</ul>
<ul>
c)
 javax.security.auth.Subject subjectA = weblogic.security.Security.getCurrentSubject();
 subjectA.doAs(subjectA, myClassObject);

</ul>
Thanks in advance,
Nuno B.

Here is a document on Monitoring and Reporting Tool Integration into Network Admission Control.
http://www.cisco.com/en/US/netsol/ns466/networking_solutions_white_paper0900aecd801dee49.shtml

3rd party storage: AoE/Coraid integration

Similar Messages

Maybe you are looking for