Connector Migration 1.0 - 1.5

Hello
I have developed a J2EE Connector using the 1.0 specification recently.
Now I want to migrate to the 1.5 specification.
Which are the most important issues I have to consider?
Are there any guidelines, samples or documents about that migration available?
Thx,
Pardo

Michael,
The Oracle9iAS Migration Assistant is a tool that helps facilitate the migration of a 9iAS middle-tier install. This tool was introduced in version 9.0.2 and covered the "core" components of 9iAS (OHS, OC4J, and Web Cache). The tool continues to expand in scope, and will cover all 9iAS mid-tier components in version 9.0.4. (By the way, components that are not covered by the 9.0.2 Migration Assistant have their migration steps documented in the Migration Guide.)
Many 9iAS components, such as Portal, utilize a database schema. This backend is not migrated by the Migration Assistant, but rather with scripts.
Regards,
Jeremy Lizt

Similar Messages

GTC Connectors migration in OIM11gR2

Hi
We had exported entire GTC resource object and when we tried to import in another env, we see dependency errors on GTC Schedulers even though the schedulers exists in the xml.
What are the steps to migrate GTC Connectors(Flatfile and DBAPP) from one environment to another?
Do I have to import GTC Schedulers first and then Resource Object,Process Form and Process Definition? Does the reconciliation and provisioning work after import without issues?
Pls share ur ideas.

Make sure you are exporting the Generic Connector type object, and not the Resource Object. There are configurations that only come when you export this way. Otherwise you only get the resource and process definition workflow, and none of the configurations.
You might also need to export the provider definition as well and import.
-Kevin

Google Apps Connector: Migrate from 1.0.4455 to 1.1.5658.jar

Hello IDM Gurus,
Recently I upgraded our IDM instance from 8.1 with patch 14. My
understanding is that this aggregation of patches would also allow us to
utilize the new Google Apps (org.identityconnectors.googleapps-1.1.5658.jar) connector.
http://wikis.sun.com/display/IdentityConnectors/Google+Apps+Connector
1st question: How does one migrate from an existing instance of the Google Apps connector 1.0.4455?
Resources->Migrate Adapters->Migration Wizard (Does not list the Google Apps Resource)
Thank you for any assistance or documentation you may be able to provide.
- IDMxml

I think you had copy from some where i.e pdf, doc file. Write in notepad, don't copy, paste it and try.
In error clearly showing some kinds of junk character ie. "ûrepository"
Edited by: 953040 on Apr 10, 2013 10:47 PM

Business connector migration

Hello ,
We are planning to migrate BC 4.8 from one server to another with different Suse Linux to RedHat Linux.
1.We are wondering how the BC 4.8 can be migrated.?
2.What are the required information to migrate..?
3. Do we need to take export of any configuration or file system level data?
Thanks in advance.
Regards,
Hari

Hi,
Make sure that u have the right installables for installing the BC in RedHat linux.
As far as I know BC is out dated and is not in maintenance so I would prefer migrating to PI instead. As the BC is web based, I guess al the configurations has to be carried out again as per the config guide.
Hope this clarifies.
Regards,
Varadharajan M

Business Connector to SAP XI migration

Hi Experts,
1)Customer is using Business connector with R/3 46C .
2) Now R/3 4.6C will be Upgraded to ECC6
3) We need to first find out if the BC will work with ECC6 or not. If not we will need to give them the Approach for BC to XI Migration.
if XI has to be used what will happend to the interfaces running in BC ...is their any way that we can use that in XI and work....
or ...we need to do developmet from the scrach...
Thanks
Rupesh

Hi,
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a8424011-0d01-0010-e19d-e5bd8ca52244
http://www.sap-hefte.de/download/dateien/917/052_lesesprobe.pdf
Business connector --
WAS - Business Connector
business connector documentation
SAP Business Connector
Business connector
Will Business Connector 4.6 be affected by new Daylight savings changes
Business connector
More info on XI can be found at https://service.sap.com/xi
and webAS on http://help.sap.com/saphelp_nw04/helpdata/en/f3/e20f3adfd0a706e10000000a114084/frameset.htm
Check this also-
http://help.sap.com/saphelp_nw2004s/helpdata/en/6f/1bd5c2a85b11d6b28500508b5d5211/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b4f3755a-0401-0010-b6b3-9b65bb7d4503
http://www.yellow2b.com/Yellow2B-Content_C-Content_full_1112108163571.html
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a8424011-0d01-0010-e19d-e5bd8ca52244
Thanks,
Satya Kumar

Ex2007 - Ex2013 Migration - Change in Send Connector = Transport.ServerCertMismatch.Monitor

I am in the final stages of a 2007->2013 migration that has gone very well. I was just about to move my Send Connector over to the Exchange 2013 side when my monitors alarmed that "Transport.ServerCertMismatch.Monitor" had gone unhealthy.
There is not a whole lot of information out there, but I did find this in each of the MBX logs:
Microsoft Exchange could not find a certificate that contains the domain name mail.domain.com in the personal store on the local computer. Therefore, it is unable to support
the STARTTLS SMTP verb for the connector Internet e-mail with a FQDN parameter of mail.domain.com. If the connector's FQDN is not specified, the computer's FQDN is used. Verify the connector configuration and the installed certificates to make sure that there
is a certificate with a domain name for that FQDN. If this certificate exists, run Enable-ExchangeCertificate -Services SMTP to make sure that the Microsoft Exchange Transport service has access to the certificate key.
I checked my SAN and I do have mail.domain.com in it. I also confirmed that the Send Connector was using mail.domain.com as its HELO/EHLO reply. I have cycled the service and that did not seem to help either. Mail will still flow in my
testing, but I do not like unhealthy statuses so I would prefer to fix it.
Thoughts?

Did you install and enable an SSL certificate with the "mail.domain.com" SAN on the Exchange 2013 CAS for the available Exchange services?
Normally, when migrating from Exchange 2007, you need to request a new SSL certificate which includes the legacy namespace in the SAN field and install it both on the new Exchange 2013 and the legacy Exchange 2007 servers.
Step by Step Screencasts and Video Tutorials

Migration Exchange 2003 to 2010 routing connector

Hello
At least we deside to migrate from 2003 to 2010 Exchange now i'm preparing and stuck around one question.
In our Exchange 2003 organization we have couple backend servers and one frontend on which OWA is installed.
OWA server placed to second routing group others backend server in first routing group.
Roitung group connected to each other by connector.
So the question - when i install CAS Exchange 2010 he asked me with which Exchange 2003 server i want to create connector - which server i should choose? Backend or Frontend which placed in different RG?

It doesn't really matter, it is a connector between your 2010 and 2003 servers.
You can choose the backend servers as it will reduce one hop in your case. Do make sure that you make the connector redundant by adding atleast two 2003 and 2010 servers as source and target servers in both connectors.
There will be two connectors - one from 2003 to 2010 and another from 2010 to 2003.

Migrating AD adapter to Exchange connector

Hello!
I am looking for a bit of direction here. At a customer's site we have an AD adapter. Through it we are also provisioning the Exchange mailboxes by setting a couple of attributes. But there was never an Exchange resource defined. Now that we are about to migrate to connector based resources I am wondering what is the procedure for Exchange. Should we skip the connector for that and go about as we did before or do we need to re-hack our forms and workflows to provide for a new resource which would be the Exchange mailbox?
Regards,
/hydrazine

Well, we are on the AD adapter going through a win 2003 gateway today, talking to win 2008 AD's with an Exchnange 2003 somewhere in the mix.
today the forms basically set a few important exchange attributes in the AD and call an after action bat script on the gateway to make home and profile directories...
Nwo they are moving to Exchange 2010 and the connector could probably do the job, but moving all the other stuffover to a connector from adapter has shown to be a daunting task, especially for a product that is dead in the water as it stands... so what we do is to remove those exchange attributes from the adapter works, sending arguments down to a file on the gateway instead (through the after action script)
this file in turn is scanned by a powershell scripts which in turns makes all the changes needed in exchange, filesystems and lync, its not much really thats needed... it then signals back to the admins IF anything goes wrong so they can look see... otherwise stuff is just logged as per usual
so, no need to update the gateways from 2003 since powershell works on them to (though they will get upgraded eventually) and the powershell script is responsible for talking to exchange and lync so no need for IdM to know anything about it... hence no need for connectors and minimal developing time for some small scripts... for a system that will be replaced soon enough anyway...
All in all, its a scratch built solution, but it will do until they replace it...

Migrate from 2003 to 2010 - Receive Connector Authentication

I'm in the process of upgrading a remote office from Exchange 2003 to Exchange 2010. Today, we changed the IP's on their firewall so that 2010 Hub Transport is handling mail. Normally, I always create a new Receive Connector for receiving mail
from the internet. I leave it as Anonymous users only and receive on internal IP of the server.
When I send an e-mail from the internet to a 2010 user, the mail is delivered fine, I'm assuming through the new "Anonymous" access connector I created. However, when I send e-mail from the internet to a 2003 user, I get the following NDR
with this error:
Reason: 530 5.7.1 Client was not authenticated
I was able to fix the problem by adding Anonymous authentication to the Default receive connector. I'm wondering why this connector is being chosen over the Internet connector though, and why only for 2003 users? Is it bad to leave the Default
Connector allowing anonymous access? I've always left that connector alone and created a new Internet connector which has seemed to work in the past.

Hi,
According to your description, exchange 2010 like a relay server, and relay the email to exchange 2003 when you send a email from the internet to a 2003 user.
As Ed mentioned, when you add the correct IP address where the traffic comes from on the receive connector, then it would ensure that the correct receive connector would be used.
The following article for your reference:
Resolve 530 5.7.1 Client was not authenticated
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

To migrate SAP business connector scenario to SAP XI.

Hi,
I want to migrate my IDoc-http sap bc scenario to sap xi.
1:What the basic things do i need ?
2:what basic steps do i need to perform to migrate a sap bc scenario to sap xi?

Hi Shewta,
from a BI perspective, please check the HowTo-Papers available in this area.
You find them at:
<a href="https://websmp202.sap-ag.de/~form/sapnet?_SHORTKEY=00200797470000073641&_SCENARIO=01100035870000000202">SAP Service Marketplace HowTo guides</a>
Cheers
SAP NetWeaver 2004s Ramp-Up BI Back Office Team

Migration from Business Connector to XI

Experts,
when migrating from BCo to XI, what is the approach?
What r the things that can be considered?
How can we compare XI and BC?
Any links should help me.
Thanks,
-Naveen.

Hi,
Have a look on:
this SDN thread:
How to move SAP BC config automatically to SAP XI?
this SAP doc:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b4f3755a-0401-0010-b6b3-9b65bb7d4503
others found thanks to google:
http://www.reply.it/upload/File/pdf_boxjolly/eng/CAPR05_sapXI_ENGLISH.pdf
http://www.asug.com/client_files/Calendar/Upload/MigrateToXI%20ohio%20asug.ppt
Moreover a session will be organized to the SAP tech:
https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/92e6dde6-0901-0010-f3a3-9ed771f90e71 [original link is broken]
Hope this help you
Mickael

Business Connector 4.8 migration issue - missing options on home screen

Hi Guys,
I have migrated BC 4.7 to 4.8
I have used the transfer.zip etc to get the config settings etc
The system is up...and appears to running...
However we use an application called pocket manager
So when I go to
http:
servername:5552\wpm\home.dsp I get the login page - good
I then get a screen that says logout...
However this screen is supposed to show
Publishing and
And Administration
I am unsure how on how to get these option back)
I know above is using 5552 - this is what the old dev system was using and prod users 5553
Any help or pointers would be gratefully received

Hi Guys,
Missing Parmeters.xml and java mem change
so copyed the above .xml file from old box,
and chnaged the java.bat file
to a bigger mem size resolved the issue

Remove legacy Send connectors from Exchange 2010 after migration

Hello.
I have just removed the last legacy exchange 2003 server form our organisation.
I followed the official MS documentation for this and the remove went to plan with no errors.
The only issue I now have is that I have 2 legacy exchange send connectors in the Hub Transport view.
I have tried to disable and remove them but I get an undocumented error. The warning I get in the exchange server event logs is as follows
Process w3wp.exe () (PID=8148). Object [CN="Connector name",CN=Connections,CN="Organisation Name",CN=Routing Groups,CN="Group Name",CN=Administrative Groups,CN="Org Name",CN=Microsoft Exchange,CN=Services,CN=Configuration,DC="Domain
Name",DC="local"]. Property [HomeMtaServerId] is set to value ["Domain Name"/Configuration/Deleted Objects/Microsoft MTA
DEL:1bfa936f-c57e-4b7d-ad03-258acb560ad3], it is pointing to the Deleted Objects container in Active Directory. This property should be fixed as soon as possible.
Is ADSI edit the best way to remove these entries or is there another way to disable and remove?
Regards
Lee Gregory

Hi,
If the legacy send connector is no longer needed, it is ok to remove it from ADSIEdit.
For reference: select configuration as Connection point > domain > Services > MS Exchange > organizaiton name > Administrative Groups > Exchange Administrative Group > Routing Groups > First Routing Group > Connections
Regards,
Rebecca Tu
TechNet Community Support

Help With Migration From Exchange 2007 To Exchange 2013

We have an Exchange 2007 Server with Service Pack 3 and Rollup 12 applied.
I installed a new Exchange 2013 Server and then immediately applied CU3.
I am following this Technet article:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
The only deviation from the instruction I have had to do is in Part 2, section 4 “Configure offline address book (OAB)”.
Instead of entering:
Get-MailboxDatabase | Set-MailboxDatabase -OfflineAddressBook "\Default Offline Address Book (Ex2013)"
I had to enter:
Get-MailboxDatabase | Set-MailboxDatabase -OfflineAddressBook "\Default Offline Address Book (Ex2012)"
I believe this is due to the fact that the writer installed from an Exchange 2013 CU1 disk and I only had Exchange 2013.
Also when I tried to run:
Move-OfflineAddressBook -Identity "Default Offline Address Book" -Server SRV-EX2013
I get the following error:
Move-OfflineAddressBook : Failed to create the 'ExchangeOAB' folder on the target server 'SRV-EX2013'. Two possible reasons for the failure are that the System Attendant Service is not running or you do not have permission to perform
this operation. Error message : 'Catastrophic failure (Exception from RESULT: 0x8000FFFF (E_UNEXPECTED))'.At line:1 char:24+ Move-OfflineAddressBook <<<<
-Identity "Default Offline Address Book" -Server SRV-ex2013+ CategoryInfo
: InvalidResult: (Default Offline Address Book:OfflineAddressBookIdParameter) [Move-OfflineAddressBook], LocalizedException
+ FullyQualifiedErrorId : 9250969C,Microsoft.Exchange.Management.SystemConfigurationTasks.MoveOfflineAddressBook
However when I looked at the address books in EAC I could see that “Default Offline Address Book (Ex2012)” was the default and that it contained a copy of the Global Address List. So I did nothing else about it.
I am now at Part 3, section 7 “Move Mailboxes” and it keeps failing.
I am using the EAC so that I at least see the error as using the powershell brings back no results.
Anyway it Syncs the 18 items in the mailbox then fails with:
Data migrated: 936.7 KB ‎(959,145 bytes)‎
Migration rate: 0 B ‎(0 bytes)‎
Error: MigrationPermanentException: Error: An error occurred while updating a user object after the move operation. --> Unable to generate the e-mail address. Unable to load address module ‎'C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\address\SMTP\AMD64\inproxy.dll‎'
for address type ‎'SMTP‎'. Additional message: ‎'Access is denied‎'.
Help??
Tony

Hi,
You can't configure Exchange 2013 to generate other OAB versions, and the OAB generation occurs on the Mailbox server on which the organization mailbox resides.Therefore, to move OAB generation in Exchange 2013, you must move the organization mailbox. You
can only move the OAB generation to another Exchange 2013 mailbox database. You can’t move OAB generation to a previous version of Exchange.
And please refer to the following articles :
Moving OABs between Exchange versions
If you want to upgrade from exchange 2007 to exchange 2013,I recommend you refer to the following article:
Upgrade from Exchange 2007 to Exchange 2013
Exchange version
Exchange organization coexistence
Exchange 2007
Supported with the following versions of Exchange:
Update Rollup 10 for Exchange        2007 Service Pack 3 (SP3) on all Exchange 2007 servers in the
organization, including Edge Transport servers.
Exchange 2013 Cumulative        Update 2 (CU2) or later on all Exchange 2013 servers in the
organization.
Install Exchange 2013 in an Existing Exchange 2007 Organization
You can install a Microsoft Exchange Server 2013 server into an existing Exchange Server 2007 organization, and then move the Exchange resources, such as mailboxes, public folders, and connectors, to Exchange 2013. However, you can't perform an in-place
upgrade from Exchange 2007 to Exchange 2013.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Migration from Exchange 2007 to Exchange 2013

We are migrating from Exchange 2007 to Exchange 2013. We have a new Exchange 2013 server will all of the roles installed, but none of the mailboxes have even been moved yet. We are seeing some of our users getting prompted to accept the self signed certificate
on the exchange 2013 server. Exchange 2007 server is still handling all of the mail flow and connectors. Any reason why some of our users would be prompted with the certificate for the exchange 2013 server even though their mailbox is still on exchange 2007.
Our users are on outlook 2010.
Ed
Ed

Hi,
Could you show us what is the prompt details?
According to your desciption,I recommend you refer to the following methods to troubleshoot:
1.Please check if outlook anywhere been configured to connect exchange 2013.
2.Ctrl+Right click outlook, use “Test E-mail AutoConfiguration” to check all the settings .
Thanks.
Niko Cheng
TechNet Community Support

Connector Migration 1.0 - 1.5

Similar Messages

Maybe you are looking for