Migrating from SAP DMS to File Server

Hi,
Our client is currently using the SAP DMS to store documents for the EHS module. This has brought with it lot of handicaps.. primarily the huge size of the database. There is an initiative now to move from SAP DMS to a file server where the files would be physically stored whereas the linking would be made via SAP EHS module.
This effectively means that the things would remain as they were.. only that the specifications in EHS would now be pointing to a new location for its documents.
My question is whether this is a techinallly feasible solution and second how should the migration be done. keeping in mind that the linkages should be kept intact.
Suggestions are solicited... points are guaranteed.
Thanks!
Aviroop

Hi Aviroop,
Got any idea about how File server works with DMS ?
I am in urgent need for details about the file server functionality and configuration.
Can I use a sharepoint site (internet site0 as a file server?
Pls send me some documents regarding this to my mail id [email protected]
Thanks in advance and warm regards
Purnendu

Similar Messages

How to use XI to retreive document files from SAP DMS?

Hello XI experts,
We have external application php that runs on separate non-sap server.
I am willing to retrieve document from SAP DMS (documents management system) via XI and forward them to this application. The files are usually ms office format when you display them ( but I am not sure how they are stored in database)
Anyone can tell me please if I can use XI for this purpose?
How is going to be the connection and the retrieval done on DMS side ?
What adapter will be used and how the file will be transferred via XI?
Also I will appreciate any directions in connecting the php application side. What Adapters will be used , how doc file can be send (I guess as an attachments )?
Appreciate any help!

hi check
FG : CVBAPI
U have Standard BAPI to communicate with DMS system meeting your requrment
some bapis
BAPI_DOCUMENT_CHECKOUTVIEW     Check out document for display
BAPI_DOCUMENT_CHECKOUTVIEW2    Check out document for display
BAPI_DOCUMENT_CHECKOUTVIEWX    Check out document for display
BAPI_DOCUMENT_CREATE                   Create Document
rgds
srini

What is the easiest way to download a document from SAP DMS with C#?

Hi,
I've been sifting through this forum and looked at various posts and sample code, but so far my quest hasn't been fruitful.
What is the easiest way to download a physical document file from SAP DMS using C#? I'm using the NCo 3 (SAP .NET
Connector 3).
Requirements
- As few dependencies as possible (not adding or changing functionality in SAP)
- C# code (MS Visual Studio 2012)
- SAP Environment: NetWeaver 7.4.0
Thanks for all help.
Regards,
Frank

We've been using BAPI_DOCUMENT_CHECKOUT2, but there seems to be a limitation. From what I've found on Google, you must enable the use of the SAPGUI through the flag UseSAPGUI when connecting to SAP. It works, but my issue is that when I use it on a web server, I end up with some error when trying to start the GUI. There is very little recent information for this out there right now.

Migration from SAP BC To SAP P.I

HI Experts ,
I am required to do migration from SAP BC to SAP P.I. I would require the following Info/Help from you as i have not worked on such scenario before this!
1) What kind of challenges can be faced during migration from BC to XI?
2) What is the best practise for doing the same?
3) Can you share some scenario from where i can have some idea how to do migration?
4) Generally how much time it takes in migration activity if ther are not much interfaces involved in it?
Would appreciate your valuable inputs on the same!
I have read How to guide docs on how to do migration from BC to XI but not convinced with the content
Regards
Saras Jain

Hi Saras,
I am giving you an example senario and a how to do all the steps and why it needed. if you need more information just mail me i'll give you the concerned PDF.
Scenario
SAP Business Connector enables data exchange between an SAP system and
external systems using HTTP and e-mail. SAP Exchange Infrastructure (SAP XI)
replaces SAP Business Connector (SAP BC).
We distinguish between standard scenarios (that do not contain customer-specific
development) and individual scenarios (that do contain services or mappings created
by the customer). The following sections describe how to migrate both types of
scenarios to SAP XI.
Scenario 1 (IDoc HTTP, HTTP IDoc)
An SAP system sends an IDoc to SAP BC or to SAP XI. The IDoc is converted to
XML. It is sent to an external business partner by using HTTP.
An external business partner sends an XML document by using HTTP to SAP BC or
to SAP XI. The document is converted to an IDoc and sent to a connected SAP
system in the internal system landscape.
Scenario 2 (IDoc Mail, Mail IDoc)
An SAP system sends an IDoc to SAP BC or to SAP XI. The IDoc is converted to
XML. It is sent to an external business partner as an e-mail.
An external business partner sends an e-mail to SAP BC or to SAP XI. The
document is converted to an IDoc and sent to a connected SAP system in the
internal system landscape.
Flow Services
Flow services are services that are written in the proprietary graphical-based flow
language of SAP BC.
Java Services
Java services are services that are written in the Java language.
There are several platforms that support Java, including SAP XI. However, the data
model used in the Java services in SAP BC is proprietary.
Stylesheet Transformations
Stylesheet transformations are often used for mapping purposes. They take an XML
document as input, convert it according to rules defined in the stylesheet, which is
also an XML document, and produce an XML document as output.
The XML Stylesheet Transformation Language (XSLT) was defined by W3C (World
Wide Web Consortium), the consortium that defines most of the common standards in modern internet communication, such as HTML and SOAP.
SAP NetWeaver is the open integration and application platform from SAP. With
NetWeaver 04, there is a significant overlap between the functions of SAP
NetWeaver and SAP BC. Many functions provided by SAP BC are offered by SAP XI
as part of SAP NetWeaver, for example, conversion of an IDoc to an XML message,
mapping, routing, and adapters to connect to a large number of third-party back-end
systems. SAP BC is therefore no longer needed. New or updated SAP solutions are
based on SAP NetWeaver. Customers looking for a strategic integration solution for
the complete application landscape should therefore now favor SAP NetWeaver.
The last version of SAP BC was SAP BC 4.7, which was released in June 2003. SAP
BC has not been developed further since this release. SAP BC is not released for
any further platforms (such as Windows 2003) and does not support any further JDK
versions, including the current version (Version 1.4).
For information about the supported SAP BC versions, JDKs, and operating systems,
see SAP Note 309834. For information about the support and maintenance strategy
for SAP BC, see SAP Note 571530. Customers who still use SAP BC need to be
aware of the following:
A solution based on SAP BC cannot be a strategic, long-term solution.
A solution based on SAP BC is based on technology that was implemented in
2003 and that is no longer further developed.
SAP BC is supported on limited platforms and for limited JDKs only. Vendor
support for some of these platforms and JDK versions will soon be
discontinued.
SAP BC and SAP NetWeaver are based on different technologies: SAP BC is based
on webMethods proprietary Integration Server, whereas SAP NetWeaver is based
on open standards, such as BPEL4WS (business process execution language for
web services). Therefore, only parts of an SAP BC implementation, such as XSLT
mappings, can be migrated to a solution based on SAP NetWeaver. Any custom
programming based on SAP BC, such as SAP BC flow language, is unlikely to be
reusable in the SAP NetWeaver context.
Purpose of this Migration Guide
The purpose of this migration guide is to provide scenario-based descriptions of the
migration from a companys system landscape that uses SAP BC to exchange
documents with business partners, to a system landscape that uses SAP XI instead.
This migration guide outlines, for certain scenarios, the individual steps a company
has to take to replace an existing SAP BC implementation with SAP XI.
The basic steps in the back-end systems are:
Defining the logical systems
Maintaining the ALE distribution model
Maintaining partner profiles and EDI ports
Maintaining RFC destinations
The basic steps in the SAP XI system are:
Maintaining the System Landscape Directory
Configuring the IDoc adapter
Maintaining the receiver determinations, interface determinations, and
interface agreements
Maintaining the communication channels
The type of scenario to migrate typically has an impact on the communication channels only.
Scenario 1 IDoc/HTTP
IDoc HTTP Using SAP BC
Within the system landscape of a company, an SAP system sends an IDoc
asynchronously to SAP BC. SAP BC converts the IDoc into a standard IDoc XML
document. The fields of the IDoc are not modified, that is, the conversion does not
involve any mapping of source fields to target fields. After conversion, SAP BC uses
HTTP to send the XML document synchronously to an external URL of a business
partner.
System Landscape
An SAP system and SAP BC are installed within the same system landscape
of a company.
The following information is defined in the SAP system to allow data
exchange between the SAP system and SAP BC:
o An RFC destination and a logical system for SAP BC
o The distribution model is maintained, if necessary
The following information is defined in SAP BC:
o An SAP server with an alias is defined. For this SAP server, the
information that the SAP BC requires to connect to the SAP system is
specified.
o A listener is configured to listen to requests from the SAP system.
o A routing rule with the transport type XML is configured for the
specific sender, receiver, and message type. The routing rule
determines how a message is to be routed and where it is to be routed
to. The scenario described does not use an ACL, (Access Control List
to restrict execution permissions for this routing rule) or pre-processing
or post-processing SAP BC services.
4.2 IDoc HTTP Using SAP XI
Check the prerequisites described above under Prerequisites for Standard
Scenarios.
The IDoc adapter is used to receive an IDoc from an SAP back-end system and
convert it to XML.
The adapter used to post this XML to an external destination is the plain HTTP
adapter.
To set up the communication channel, perform the following steps:
1. Locate the routing rule in SAP
Business Connector.
In the Administration View, choose
Adapters Routing to navigate to
Routing Rules.
2. Select the details of the relevant routing rule.
To display the details, choose the green triangle (Edit).
Transport is typically set to XML and a URL is specified. You can use this
URL in your SAP XI settings.In some cases, Transport is set to
B2B Service and the parameters Server Alias, Folder and Service
exist. This is the same as when Transport is set to XML and has the
URL http://<serverhost>:<port>/invoke/<folder>/<service>.
You can find <serverhost> and<port> in the definition of the
remote server under Settings >Remote Server in the Administration
View.
3. Set up the communication channel in the Integration Directory using the parameters from the SAP BC routing rule.
Use the following settings:
Adapter Type: HTTP Receiver
Transport Protocol: HTTP 1.0
Message Protocol: XI Payload in HTTP Body
Adapter Engine: Integration Server
Addressing Type: URL Address
Target Host, Service Number,and Path need to be set in accordance with the SAP BC routing rule. HTTP Proxy Host and HTTP Proxy
Port can be set if required.All other parameters have no corresponding values in SAP BC and should be set to their default values.
regards
Aashish Sinha
P : Reward points if helpful

Connect from SAP gateway to RFC server failed - Java StandAlone app X SAP RAC System

Dears,
I'm developing a Java application (RFC SERVER) with JCo3 and I need to connect to SAP RAC system.
I have configured the TCP/IP connection via transaction SM59, but when I try to start my server I face the error below (dev_jco_rfc.trc):
==========================================================================================
**** Error file opened at 20140714 112024 Brasilia Time Rel 3.0.10 (2013-08-08) [720.440]
Error: >Mon Jul 14 11:20:24,636<    RfcException: [null]
    message: Connect from SAP gateway to RFC server failed
Connection parameters: TYPE=A DEST=VSPAGUE ASHOST=cpe1601 SYSNR=01 SAPROUTER=/H/155.56.49.28 PCS=1
LOCATION    SAP-Gateway on host ld7624.dmzwdf.sap.corp / sapgw01
ERROR       hostname 'cpe1601' unknown
TIME        Mon Jul 14 16:20:25 2014
RELEASE     740
COMPONENT   NI (network interface)
VERSION     40
RC          -2
MODULE      /bas/740_REL/src/base/ni/nixxhl.cpp
LINE        193
DETAIL      NiHLGetNodeAddr: hostname cached as unknown
COUNTER     3
    Return code: RFC_FAILURE(1)
    error group: 102
    key: RFC_ERROR_COMMUNICATION
==========================================================================================
This problem happens when my app executes the line:
JCoServer myServer = JCoServerFactory.getServer(myServerName);
My system properties:
jco.client.lang=EN
jco.destination.peak_limit=10
jco.client.client=800
jco.client.passwd=********
jco.client.user=********
jco.client.sysnr=01
jco.destination.pool_capacity=3
jco.client.ashost=/H/155.56.49.28/H/cpe1601
jco.server.connection_count=3
jco.server.gwhost=/H/155.56.49.28/H/cpe1601
jco.server.progid=VSPAGUE
jco.server.gwserv=sapgw01
jco.server.repository_destination=VSPAGUE
Using SAP Logon i can connect to server cpe1601 system E16 without problems.
Please, I really need some help, because my knowledge on SAP platform is minimum.

Hi Markus,
Changing ASHOST=ld7624.dmzwdf.sap.corp as you have suggested, I got the error message: Connect to SAP gateway failed ...
As you could see, the host I'm connecting is from SAP RAC Service.
Here in our company we have only SAP Logon and my RFC Application, and I can connect to SAP remote system via SAP Logon with this settings:
System Connection Parameters
Description: SAP ECC 6.0
Application Server: cpe1601
Instance Number: 01
System ID: E16
SAProuter String: /H/155.56.49.28/H/
Below the connection information I received from SAP RAC SUPPORT for testing purposes:
    E16 System:
    SID: E16
    Client: 800
    System Number: 01
    Server: cpe1601
    Component Version: SAP ERP Central Component 6.0 Enhancement Pack 6 Suite on HANA
    User: ********
   Password: ********
   SAProuter String:
   If you don't plan to use SAPRouter at your end,
   /H/155.56.49.28/H/

Connect from SAP gateway to RFC server failed

Good day and a happy new year to you all!
I am failing to connect to my SAP BW system from BEx. The logon fails with this message:
>>>>>Start<<<<<<<<<<
Error Group
RFC_ERROR_COMMUNICATION
Message
Connect from SAP gateway to RFC server failed
Connect_PM GWHOST=10.16.64.77, GWSERV=sapgw02, ASHOST=10.16.64.77, SYSNR=02
LOCATION    SAP-Gateway on host bwsys / sapgw02
ERROR       timeout during allocate
TIME        Sat Dec 31 13:16:19 2005
RELEASE     640
COMPONENT   SAP-Gateway
VERSION     2
RC          242
MODULE      gwr3cpic.c
LINE        1785
DETAIL      no connect of TP sapdp02 from host 10.16.64.77 after 22 sec
COUNTER     2
>>>>>>>>>END<<<<<<<<<<<<
I only experience this problem when connecting using any BEx component, but, I can successfully connect to the SAP BW system from SAP gui.
Additionally, I have the service 'sapdp02' defined in the services file, both on the workstation and the server.
What could be wrong or missing in my configuration?
Regards,
Joao.

hi Joao,
check if oss note 447882 relevant
you may ask basis for help
Symptom
You want to access the customer system using the BEx Analyzer.The connenction fails:The system displays the error RFC_ERROR_COMMUNICATION.In the detail screen, the system displays message "Partner not reached" (host 192.168.4.2, service sapgw 00).
Other terms
SAP Gateway, RFC_ERROR_COMMUNICATION, partner not reached
Reason and Prerequisites
The SAP gateway host is deactivated or the TCP/IP port 33xx (where xx corresponds to the system number) is not open.
Solution
Issue statement ping <IP address> (In this example:192.168.4.2) No reply: Boot SAP Gateway host required.
An answer:Check whether the TCP/IP port 33xx is open (where xx corresponds to the system number) and start the SAP gateway.
The TCP/IP port is also partially defined in the services file as an sapgw<SID> or sapgwxx entry (where xx corresponds to the system number). The services file is in the Windows directory or in WinNT/System32/drivers/etc.

Remote Connection from SAP to MS-SQL server

Hello Experts,
We have been following 2 options so far and we have come across some issues
The first Option is to call a stored procedure (this is our preferred method) which does the data transfer for us
We have been able to test this scenario successfully from SQL Server side
However, while calling the stored proc via native SQL from ABAP we have come across an issue which is due to SQL 2005 changes (Schema implementation and difference in the security context)
While calling the stored procedure from the ABAP Code we have an error
The program short dumps with runtime error DBIF_DSQL2_SQL_ERROR, exception CX_SY_NATIVE_SQL_ERROR. The database error code is 15274, and the error text is
"Access to the remote server is denied because the current security context is not trusted."
This issue is new after the SQL Server 2005.
We are trying to resolve that.
Secondly we have been trying the DBCON option as well as per OSS Note 323151
We have a few things thatu2019s impacting our scenario:
The remote servers are in a different domain
The remote servers are located in DIZ
Remote server is a named instance
Remote server has been configured with a different port than standard (1565) u2013 All Connection strings will need port in there
The Database name starts with a numeric value
Due a combination of factors as mentioned above the standard approach does not work
Have any of you used this approach while connecting from SAP to MS-SQL server? Do you know of any successful methods to connect to SQL using ABAP (or not) from SAP.
Thanks in advance,

Yes,
DBConnect & UDConnect.
Works like a charm.
We write data into a MS-SQL database via DBConnect & an ABAP program (using open sql).

Migrating from SBS 2011 to Windows Server 2012R2 Standard with 365

Im looking to move SBS 2011 to Server 2012R2 standard and with a 365 migration as well.
Im thinking
BPA for AD (health check)
Add the Server2012R2 as a DC
Ensure replication
Move DHCP
Change DNS
Now this is where I get lost, now Im lost to use either dirsync or add essentials service, I have gone for standard and 30 cals with the option as I have 28 users and the essentials service would make everything quite nice for remote access and backups
etc.... however I don't know whether to just use dirsync with password replication instead ?
Currently Im aiming towards getting the dc up and running then enabling essentials on the dc but I dont know how it will effect SBS and having essentials on the same network and sync'ing people to the cloud ? So Should I use DirSync on a different server
instead to sync up to azure ?
Finally with 365 I have only ever done a migration involving an export of pst's from an exchange box and then on a new domain with new pc's and reimport the pst's on the user accounts in outlook.
However I have read when migrating to 365 was using exchange 2010 there was a application
to move everything across however you needed an ssl cert iirc ? so I dont know how it works now since the nice new dashboard upgrade (assuming the tool has been updated like dirsync)
along with the above how does AD now know where exahcnge if you use the migration app with an ssl cert and is it a case of still running the 365 config tool to configure each user to look at their mail in the
cloud ? Also is it a good idea to enable essentials from the start of the 2012r2 dc for replication top 365 or to use dirsync ?
then finally when replications is all good start transferring the FSMO roles over to the new DC and demote and remove the SBS server
I have seen (below) but i dont think it covers this scenario and I cant be the only person in this situation =\ ?
http://blogs.technet.com/b/infratalks/archive/2012/09/07/transition-from-small-business-server-to-standard-windows-server.aspx
http://social.technet.microsoft.com/Forums/en-US/f552ef12-07a9-4f7a-bf5e-24500c3e1dc3/migrate-sbs-2011-to-server-2012-standard?forum=smallbusinessserver
http://social.technet.microsoft.com/Forums/en-US/e1d4b09f-8857-4ef6-9a80-6a906e76b688/how-to-migrate-sbs-2011-to-standard-2012-server?forum=smallbusinessserver

Hi,
Would you please let us know current situation of this issue? If any update, please feel free to let us know.
à
Currently Im aiming towards getting the dc up and running then enabling essentials on the dc but I dont know how it will effect SBS and having essentials on the same network
and sync'ing people to the cloud?
I’m a little confused with the description. Did you mean that set up DC (Windows Server 2012 Standard) and
then install the Windows Server Essentials Experience role? If so, when you migrate, please refer to the article:
Migrate from Previous Versions to Windows Server 2012 R2 Essentials or Windows Server Essentials Experience
Regarding to migrate Exchange to Office 365, please refer to following articles.
Migrate
All Mailboxes to the Cloud with a Cutover Exchange Migration
Step-By-Step:
Migrating from Exchange 2007 to Office 365
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft
does not guarantee the accuracy of this information.
Meanwhile, there is an additional article that you can refer to:
Manage Office 365 in Windows Server Essentials. It may help us to understand Office 365 in Server Essentials clearly.
If anything I misunderstand, please don’t hesitate to let me know.
Hope this helps.
Best regards,
Justin Gu

Search not working in site collections migrated from MOSS 2007 to SharePoint Server 2013

I have few site collections migrated from MOSS 2007 to SharePoint Server 2013 using database attach (first to 2010 and then to 2013).
When I search for anything in these migrated sites, I get "Nothing here matches your search".
Checked the crawl log for these sites and see this error for all items.
The content processing component failed to process the security descriptor of the item. ( The input ACL is invalid (1210 / 2072).; ; SearchID =
Some-Random-GUID )
Search works fine in newly created sites in 2013 environment.
Please help.

Hello
Did you migrate your users to claims when you migrated the databases?
$wa = Get-SPWebApplication http://yourdom.com
$wa.MigrateUsers($true)
$wa.ProvisionGlobally()
I assume the sites that work and the migrated content are in the same database?
MCITP-EA | "Never test how deep the water is with both feet"

Crystal report- Connect from SAP gateway to RFC server failed

Hi All,
I am trying to connect to a SAP R3 system from crystal reports but it gives me below error.
Please note : Transports have been imported and also the roles CRYSTAL_ENTITLEMENT and CRYSTAL_DESIGNER. My user is a member of these roles which were release along with Best practice reports v1.31
Error :
Logon failed.
Details: CMALLC : rc= 27 > Connect from SAP gateway to RFC server failed
Connect_pm GWHOST=10.10.4.63, gwserv=SAPGW30, SYSNR= 30
Location SAP-gateway on host ply.log.com/sapgw30
Error timeout during allocate
TIME ....
Release 700
Component SAP Gateway
Version 2
RC 242
Module gwr3cpic.c
LINE 1996
Detail no connect of TP sapdb30 from host 10.10.4.63 after 20 sec
Can you please help us solving this error.
Thanks
Chetan

Hi Stratos,
The SAP Version is ECC 6.0.
The below transports have been imported.
u2022 Open SQL Connectivity transport (K900574.r21 and R900574.r21)
u2022 Info Set Connectivity transport (K900575.r21 and R900575.r21)
u2022 Row-level Security Definition transport (K900576.r21 and R900576.r21)
u2022 Cluster Definition transport (K900585.r21 and R900585.r21)
u2022 Authentication Helpers transport (K900578.r21 and R900578.r21)
Thanks & Regards,
Chetan

Error: Connect from SAP gateway to RFC Server failed

Hi
I am trying to connect SAP server using the java (JCO connection), and getting following error. While I am able to connect to the same sever using SAP Logon pad with the same ipaddress (hostname) and logon credentials.
Please kindly help.
Erro: Connect from SAP gateway to RFC server failed.
Connect_PM GWHOST = hostname, GWSER = sapgw03, ASHOST=hostname, SYSNR=03
LOCATION SAP-Gateway on host hostname / sapgw03
ERROR timeout during allocate
TIME Wed Oct 31 05:31:45 2007
RELEASE 640
COMPONENT SAP-Gateway
VERSION 2
RC 242
MODULE gwr3cpic.c
LINE 1795
DETAIL no connect of TP sapdp03 from host hostname after 22 sec
COUNTER 3

Hi K Patil,
Acording to me you are faceing this issue because the entry of your backend System is not in the SLD (System Landscape Directory ) of your server.
to make this work you have to make entry in the SLD of your server
fort that plesae acess this link.
Re: JCo connection Error
Re: wt is SLD.. how to do configure it
Please Reward Points if Helpfull.
Regards
Vinit
Edited by: Vinit Soni on Dec 19, 2007 7:20 AM

Migration from Sun Java System Portal Server to the Oracle Portal

Hi, I'm in charge of evaluate the viability of a project that comprises the migration from Sun Java System Portal Server to the Oracle Portal. so I'm wondering if there is a kind of out of box migration tool in Oracle Portal or exists some guidelines to do the migration. In the other hand there is the option of migrate from Sun Java System Portal Server to Oracle WebCenter?
Thanks in advance!

The migration path for Sun Portal Server is Oracle WebCenter Suite. WebCenter is a significantly different architecture so there are no tools planned for the migration. However, we do plan to document and publish a whitepaper once we've assisted a few of the initial customer migrations.

Migrating from MCS7845 to UCS C210M2 Server for CUCM8.0

Customer Alpha has CUCM and Nortel.
(I.) Following is the CUCM Cluster breakup:
   - Location X: PUB, SUB1, SUB2
   - Location Y: SUB3
   - Location Z: SUB4, SUB5
(II.) Location Z, Block-A has 10,000 users on Nortel which need to be moved to CUCM8.0 for which the following two new SUBSCRIBER's added to the existing CUCM Cluster:
    - SUB6, SUB7
    - SUB6 & SUB7 will be installed on a UCS C210M2 server
    - Customer will be shipped with two UCS C210M2 with dual quad core 5640 processor
2.In Location Z, currently SUB4 and SUB5 are on MCS 7845 server.
Need to Migrate SUB4 and SUB5 on UCS C210M2 Server from MCS7845.
This way, Location Z with SUBSCRIBERS(SUB4, SUB5, SUB6 and SUB7) will migrate to UCS C210M2 server platform.
Rest of the locations namely- LocationsX & LocationY will continue running on MCS7845 platform.
Need to understand the Migration strategy (point wise) keeping in mind, the PUB is in LocationX still on MCS and only the SUB- SUB4, SUB5, SUB6 and SUB7 will be on UCS platform in locationZ.
Please share the steps required to perform this type of Migration.
Thanks & Regards
Sumit

Hi Gajanan,
Thanks for your prompt reply.
SUB4 Migration from MCS7845 to UCS C210M2 server involves the following steps:
Take SUB4 out of the Network.
Install SUB4 on UCS C210-M2 server, just as a fresh install and ensure the same SUB4 name is assigned on UCS what its there on the MCS7845 platform.
While installation of SUB4, it ask for PUB details like IP Address, assign the reqd. details.
Migrate the users assigned to SUB4 with SUB5 for the time being, this step should have been performed in the beginning.
Once the installation is complete, you can re-install the users from SUB5 to SUB4.
Database replication will take place from PUB
Please confirm if Step4 is required or when we take the Backup using DRS of SUB4 and after the installation of SUB4 on UCS C210, restore the backup on SUB4 and then it would populate the users/phones that were tregistered with SUB4 on MCS 7845 platform on to UCS C210M2 platform.
Do we need to take DRS of the PUB or SUB4?
Can you please put the steps in the correct order.....
Follow the same steps fro SUB5 Migration from MCS7845 to UCS C210M2 server platform.
Thanks & Regards
Sumit

Migration of SAP DMS documents from RFC Archive to SAP HTTP Content Server

Can anyone verify the correct OSS for the migration of documents from an RFC Archive repository (non SAP) in SAP DMS to a SAP Content Server HTTP Repository. Most of the OSS notes seem to indicate HTTP to HTTP migrations or based storage category migrations.
Which is the most suitable for this?
Edited by: Athol Hill on Oct 30, 2009 2:35 PM

Dear Athol,
If you want to move the originals from an archive or vault to a Content
Server, please use the DMS_KPRO_CONVERT and DMS_KPRO_CONVERT2 report I
would kindly ask you to see teh documentation on DMS_KPRO_CONVERT report
in transaction SE38, which explains the whole process and gives
necessary information.
This conversion program offers two possibilites:
- Complete migration:
The meta data of the document info record and the checked-in original
application files are migrated together. The checked-in original
application files are transported into the storage catgories.
- Step-by-step migration:
In the first step meta data is migrated. The original application files
remain in the old storage data. The migration of original application
files starts after you have processed the files with the integrated
viewer and checked them into a secure storage area.
Best regards,
Christoph

Transfer files from SAP R/3(unix server) to windows

Hi TechGurus,
We have a requirement where in , we are extracting data from SAP table into a text file using OPEN DATASET in TEXT MODE.
Then using a third party tool (Connect-direct), we are transferring text files to windows server using unix script, in binary mode.
The problem is that that the data is being transferred in blocks,each time beginning transfer from a new line.That is, after say transferring 25KB data it transfers next 25KB data from a new line. What happens as a result is that records
after particular amount of data is broken and remaining data transfer begins from new line.
The file size is around 25 MB.There is no such problem while transferring file of size 10 KB.
We are uploading the data from text file on windows server into MSAccess.
And error occurs during this process.
Assured points for helpful answers
Thanks in advance!!

Hi,
If you want to transfer file between different SAP servers then you can use the function module EPS_FTP_PUT. You need to have a RFC destination (with sufficient authorizations for the RFC user). The meaning of the importing parameters of the function module are quite obvious. Of course, SAP offers us more than this function module:
- EPS_FTP_GET
- EPS_FTP_MPUT
- EPS_FTP_MGET
Kishi.

Migrating from SAP DMS to File Server

Similar Messages

Maybe you are looking for