GroupWise System Name

I am planning a new secondary domain and Post Office for our system and was going through the checklist which I thought would be good to keep around filled out. I got to the GroupWise System name but I cant find it in the Administration console.
Any ideas?
Sincerely,
Ken

Click "System" in the left pane, then "Information" in the right pane.
HTH
Uwe
Novell Knowledge Associate
Please don't send me support related e-mail unless I ask you to do so.

Similar Messages

  • Change Groupwise system name, po name and domain name?

    Hello Board,
    we want to migrate a Groupwise 7 System (Netware) to a Groupwise 8 System (Linux).
    Doesnt sound that difficult, but we dont want to use the names for the system name, the post office and the domain (groupwise domain, _not_ internet domain) which were used on the old system.
    Currently iam trying the way mentioned in TID 10077372, which mentions merging the two systems and then delete the old System.
    Am i on the right way? Do you have any hints?
    Any help appreciated.
    best regards
    sven

    Grewes,
    Ok you have a GW system(s) that you do not like the names and you want to change them. Not a problem. As you stated, and as Tommy said -merging works.
    The process you need is to build a new GW system -same as the version you have running preferred. Set it up as you like it -name-wise. Then, merge the older systems (branches) into the new system you built. Then you will have to build new domains/post offices and move mailboxes from the old GW branches into the new domains/post offices. When its all done -delete the old, and you are done.
    I have done many different variations of this type of migration/merge/consolidation. It works, its just a lot of work. Just make sure to plan it all out on paper first, document it, then go forward.
    Good Luck!
    Take Care.
    Gregg A. Hinchman
    Consultant
    [email protected]
    www.HinchmanConsulting.com
    A Novell Consulting Partner
    317.329.0288 Office
    413.254.2819 eFax
    "Courage is doing what is right."
    "Do not be bound to any doctrine, theory or ideology, even Buddhist ones. All systems of thought are guiding means, not absolute truth." Thich Nhat Hanh, Vietnamese monk.
    Book Travel @: www.booknewtravelnow.com
    >>>
    From: grewes<[email protected]>
    To:novell.support.groupwise.migrations
    Date: 8/20/2009 6:56 AM
    Subject: Re: Change Groupwise system name, po name and domain name?
    Thank you for your reply.
    I do not want to keep the names.
    If i want to link this domain to another branches domain and the domain
    is called the same this doesnt work AFAIK.
    grewes
    grewes's Profile: http://forums.novell.com/member.php?userid=3563
    View this thread: http://forums.novell.com/showthread.php?t=383606

  • Cannot change GroupWise User Name in GW Mobility Service 2.0

    Hi,
    In GW Mobility Service 2.0 I can no longer change the "GroupWise User Name" value, which I need for the the address book selection. I need to change it, because we use AD authentication. This sets the username value to CNAME, which is different from our logon names (sAMAccountName). I can only change the "Mobility User Name""now. In 1.2.5.299, I was able to change it.
    As a result, I'm unable to add new users to the system. Anyone know how to fix this?
    Iwan

    Originally Posted by dzanre
    iwan wrote:
    > I don't add users via the web interface. I add them to an AD user group, at
    > which point they are automatically added to the system. Once they are added, I
    > change the name and sync them. I've added over 100 users like this in the
    > previous version. I don't know why it does not work anymore. It does allow me
    > to change the "Mobility User Name".
    This has actually long been an issue, and I had failures even with 1.2.5. I
    think you got lucky. This is a known problem with using LDAP groups for adding
    users.
    Also, you say that you were using AD groups, and this is definitely not
    supported. eDirectory is the only supported LDAP server for Mobility and that
    has always been the case.
    So, I'm afraid that if this was working before, it was totally by accident.
    Danita
    Novell Knowledge Partner
    GroupWise Mobility Service 2.0 Guide - Caledonia Guide to the GroupWise Mobility Service 2.0
    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below...
    Hi,
    I'm sorry to hear that. I've been using it with AD as an LDAP source for quite some time without any issues. I still use it for authentication to the web interface itself. It would still work if I could just modify the "GroupWise User Name", like I could in the previous version. It doesn't seem logical to allow changing the "Mobility User Name" and not the "GroupWise User Name".
    I am adding users through the web interface now and abandoned adding them via the LDAP group option (still use AD auth on the devices). I don't want to use eDir as I'm trying to move away from it. Every system within our company authenticates using AD. I only have eDir for GroupWise and with the next version of GW coming up and fully supporting AD, I can finally go to a single Directory.
    When I migrate to GW 2014, will I be able to select GroupWise for authentication in Mobility Service and have the POA use AD authentication? Effectively giving Mobility Service AD authentication through GW? If so, the only thing that would not work is adding users via a group (if eDir is not used anymore).
    Iwan

  • Logical system name for acknowledgement in BPM

    Hi,
    I have a szenario:
    IDOC --> BPM --> MAIL
    Inside BPM I check the message and depending on an xml-element I stop the process or I send the message by mail.
    When I stop the process the BPM sends back an acknowledgement and in SXMB_MONI I can see an error of the acknowledgement:
    "Sender Test_BPM_IDOC_TO_MAIL kann nicht in ein ALE Logisches System umgeschlüsselt werden" (Sender can not convert in a ALE logical system)
    What can I do?
    Possible Solution 1:
    I can define my BPM "Test_BPM_IDOC_TO_MAIL" as a logical system (including WE20 for ALEAUD).
    Possible Solution 2:
    I can enter an existing logical system name in the "adapter specific attributes".
    BUT it is not use the same logical system name twice (BAD ... or is there a workaround?
    Is Solution 1) a common way?
    Thanx
    Regards
    Wolfgang Hummel

    Hi,
    there are many ways:
    some for aleaud are described in my book:
    <a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
    >>>>Is Solution 1) a common way?
    no this is not good a good idea
    BTW
    you can also supress aleaud raport IDX_NOALE
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • Logical System Name Not appearing in the Business System

    Hi,
    Initially we had created a Technical system with Client 700 without a "Logical System Name" in SLD. hence the 'logical system name' in 'business system' was also Blank.
    Now, since we are implementing the IDOC to file scenario; we need to maintain the "Logical System Name" in the client and which in turn should reflect in our Business System in SLD.
    Though we maintained the Logical System Name in the Technical System --> Client --> Logical System Name; we are unable to see the same(Logical System Name) in Business System ('Integration' tab)
    Please also note that Business System is of the ROLE: Integration server.
    When we go to business system in SLD ---Integrtaion tab ---Logical System Name -- is still blank.
    Can anyone please help us to update the 'Logical system name' in Business System in SLD?
    Regards,
    Rehan

    Hi Sunil,
    I followed your link till
    Bussiness System -> select your bussiness System -> in Below pane u will find Details of your bussiness system ->amongs the various tabs available select Integration Tab->U will See option for technical system beside that u will see option for change ->click this ->u will be taken to Logical system ->there u define u r logical syatem name and then save the entries.
    When I clicked the option chnage ---> "Change Associated Technical System" appeared, It didn't take me to Logical system.
    But in turn I clicked hyperlink corresponding to Technical systems, it took me to technical system --> clients tab --I have entered the Logical system name.
    When I go back to Business system again its not showing the Logical system name in Integration tab.
    regards,
    rehan

  • IDOC sender: Error in Logical system name?

    Hi,
    In my current project, the IDOC sender system logical name is P2PCLNT100 but the SLD system name is P2P.
    Its an IDOC to proxy scenario. At the receiver system side, the schemeAgencyID is getting populated at P2P and not P2PCLNT100, due to which there is an error on the receiver's side.
    Following is already checked:
    1. SLD has maintained the proper logical system name for the P2P system
    2. The IDOC xml on the XI system has the sender port properly populated as P2PCLNT100
    3. I have also debugged the program on the receiver side and fails at a point where it checks the logical system name from the database BBP_BACKEND_DEST.
    On the receiver system, the followed error is shown as follows:
    - <STANDARD>
      <CONTROLLER />
      <FAULT_TEXT>An error occured within an XI interface: SLD system P2P is not known Programm: SAPLBBP_BD_MAPPING_SAPXML1; Include: LBBP_BD_MAPPING_SAPXML1F1Y; Line: 96</FAULT_TEXT>
      <FAULT_URL />
      <FAULT_DETAIL />
      </STANDARD>
    Thanks in advance for the useful answers.
    Sowkhya

    Hi,
    1. R/3 system's logical system name and SLD business system's logical system name has the same.
    Is there a need to have the business system name in SLD to have the same name as R/3 system logical name?? As far as my knowledge goes, business system and logical system need not have the same name. Correct me if in the case IDOC sender scenario is different..
    2. SLDCHECK shows following message:
    Summary: Connection to SLD does not work
    The issue still persists. Will SLDCHECK correct solve the issue?
    Regards,
    Sowkhya

  • Logical system name in business system (SLD)

    Hi,
    While creating business system in SLD what should give for the logical system name?
    Should the logical system name exists in ABAP stack or the new one?
    Thanks.

    Hi,
    If you are creating the BS for SAP R/3 in SLD means we have to give the LS name which we had in SAP R/3( goto SALE and take the LS from there)
    Goto Assign LS-----take the client which you are using for SAP R/3 and take the LS name assigned to that Client
    Regards
    Seshagiri

  • Logical  system name to be updated while client copy--URGENT HELP REQUIRED

    Hello All,
       I have a  query regarding the "Logical System name" updation during Client copy.
      When we make a client copy(SRM Masters) for the Production system(SRM),the Old Logical system name for backend(which is attached to the SRM masters) gets copied to the new Client (Copy) which needs to be updated.
      There is  a  std transaction BDLS through whcih w e can change the current Logical system name to  a  new one but this  seems to work fine for System copy but not for Client copy.
      So when i make  a client copy of  SRM masters  for Production system,is there  any other std  way wherein i can change the "Logical system name " for the  backend or  do i have  to write a  CUSTOM program wherein entries  for  the Backend Logical system name in tables like CRMMLSGUID will  be updated  with  the new  Logical system name?
       Any help on this is  appreciated.
    Thanks & Regards,
    Disha.

    Disha,
    Yes, I did it twice and it worked fine.
    The R/3 GUID is sent by the OLTP system (R/3) in R/3 message header.
    SRM checks this GUID in CRMMLSGUID table.
    If is not the same one, then replication process fails.
    The only solution I found was to delete this entry. It is automatically recreated with the new GUID with the next replication, with FM CRMT_OLTP_LOGSYS1, called in BAPI_CRM_SAVE.
    Look at OSS note 588701 & 765018 for deletion of CRMMLSGUID.
    The issue is exactly ours: around system/client copy.
    In an CRM environment, this is more critical, because we make a huge use of the middleware. But in our case, and especially after system/client copies, we can go, even if SAP does not guaranty anything, because we don't care about "old" replicated data (I don't care about old BDOCs, that should even be deleted after processing).
    We have to take some risks sometimes...
    Rgds
    Christophe

  • Sun would like your help with the "System Name Already In Use"  error

    A couple of users have reported getting an erroneous "System Name Already in Use" error when re-registering a system after a fresh Solaris re-install. We'd like your help in tracking down this problem.
    The scenario is this:
    * Install Solaris 10 and register with updatemanager,
    * Wipe out the installation and re-install Solaris.
    * re-register with updatemanager.
    The system erroneously reports that the system name is already in use. It is supposed to detect a duplicate registration of the same system.
    We have not been able to reproduce this error in our lab.
    If this has happened to you, would you let us know at [email protected]?
    Here are the things that we would like to ask of you:
    * If you run "updatemanager -debug" if will create a log file /tmp/basicreg<timestamp>.log.
    * Details on the exact hardware you have (make/model/configuration).
    * Details on the steps you took to get to the bad state. REALLY detailed!
    Thanks!
    Based on what we know now, we believe you can work around the issue by either:
    * Changing the host name and re-registering.
    * Creating a different user account and registering the host to that account.
    Some previously-posted workarounds are known NOT to work:
    * Wait 24 hours and try again.
    * Do some "ccr" incantations and try again.

    Hi,
    Can you drop me an email as i am a sun employee and i will be able to check if the swup frontline team have received any support cases on this issue and then we can work with you directly to resolve the issue.
    Scott Wallace

  • Reg: Table name where logical system name will store in R/3 and CRM..

    Hi
    We are trying to replicate the sales order from CRM 5.0 to ECC 6.0. we mainatined publication, site, subscription and rfc connections. When the sales order is created in the CRM the BDOC is getting posted but it is picking up the wrong logical system which we were using earlier. Due to this wrong logical system, out-bound queue is getting generated in CRM but In-bound queue is not getting generated in the ECC.
    Can anybody tell me where (in which table) we need to modify the things for getting the correct logical system.
    Regards

    Hi,
    In CRM:  look for the table CRMMLSGUID. This should have the logical system name of the R/3 that it is connected to CRM and also the GUID. To check if the GUID is correct cross check with GUID from R/3 table CRMPRLS.
    In R/3: look for the table CRMRFCPAR. This will give you all the RFC connections that R3 is connected to. If you want to check whether the CRM RFC value is defined correctly compare it with RFC destination in the Administration Console (smoeac) from CRM.
    If the entries are matching then the systems are connected correctly if not you need to look at the RFC destinations from SM59 transaction.
    Hope this helps.
    Thanks,
    Karuna.

  • Logical System and Logical System Name

    Hi,
       I would like to create the following  and please tell me how do I go about doing this. I am doing this because I am trying to implement both RFC/Idoc to File and File to Idoc/RFC. The basis admin guys are unavailble at the moment so I am on my own at this moment.
    Creating a port(I suppose I need to do this on the R3. What are the steps involved)
    Create a Partner Profile

    Hi Sonia,
    For XI communicating with SAP R/3 through Idocs ALE settings need to be done,
    just go through the following steps and Configure ALE :-
    SAP XI
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (IDX1)
    a) Select create new button
    b) Enter the port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Load Meta Data for IDOC (IDX2) a) Create new
    b) IDOC Message Type
    c) Enter port created in IDX1.
    SAP R/3
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (We21)
    a) First Select Transactional RFC and then click create button
    b) Enter the destination port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Create Partner Profile (WE20)
    a) Create New
    b) Create the Partner no. name as same the logical system name of the destination system.
    c) Select Partner type LS
    d) Enter details for Type: US/USER, Agent, and Lang.
    e) Click on the + button to select the message type.
    f) Select Partner no. and LS which ever create above.
    g) Select Message type
    h) Select Process code related to the Message type.
    I) save.
    In SLD – System Landscape Directory
    TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
    Ts for Third Party (Logical system):-
    BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
    BS for Third Party (Logical system):-Enter the XI logical system name.
    In Transaction SALE
    Define and Assign the logical system name.
    Regards,
    Ashwin M
    Reward If helpful

  • How to get RFC Destination and Logical System name dynamically

    Hi all,
    I have a RFC FM written in CRM. I need to call this FM in R/3. So, i use the syntax " Call function <func> destination <destination name>. My problem is that i need to fetch the destination name dynamically..
    There is a way to do so in CRM which is as follows:
    DATA:  lt_siteselect TYPE TABLE OF siteselect INITIAL SIZE 0,
               ls_siteselect TYPE siteselect.
      CALL FUNCTION 'SMOF0_READ_SITESELECT'
        TABLES
          to_siteselect = lt_siteselect.
      READ TABLE lt_siteselect INTO ls_siteselect
             WITH KEY sitetypeid = cl_smw1_siteprovider=>c_sitetype_r3oltp.
    The above piece of code returns the site and also takes care of the client you are currently working on. But the specified FM is present only in R/3..
    I want to achieve the functionality fulfilled by the above code in R/3.
    Kindly help.
    Useful answers will be rewarded.
    Thanks in advance,
    Karan Merwana
    I can not use FM LOG_SYSTEM_GET_RFC_DESTINATION as for that i need to provide the logical system name. And the logical system name would be different for different clients.
    Message was edited by:
            Karan Merwana

    For those referring this thread later, I could not find a solution to this and ultimately had to do away with hardcoding of system names based on the DEV, Q, and PROD system names.
    If anyone does manage to get a workaround, please let me know.

  • RFC and Logical System names

    Hello......is it necessary to have RFC and Logical system name for the connected system to be identical?Is there any explanation behind this if thats true....

    Hi Gaurav,
    It is recommended, but not mandatory, right, Muthuraman?
    The system uses some transactions to determine which RFC will be used for the communication between one system and another, for example, in transaction 'Define backend systems' in SPRO, you can define that the current SRM client has an ECC backend system named X and the RFC destination for this X system is Y (not necessarily the same name).
    Regards,

  • Logical system name vs. destination name - CUA -

    Hey experts,
    at the moment I´m thinking about using the CUA in our SAP environment for role distribution.
    In this scenario I need destinations to the child systems (of course!). In all manuals I found it say, that i HAVE to create destinations which have the same name as the logical system. However, this is not possible cause this is against corporate name conventions.
    So I tried to use different destination names, but when I use the function "text comparison" (SU01->Roles) it always fails and says that the destination to the child system is missing.
    So here my question: How can I tell the CUA not to search for destinations named like the logical system????
    Thx in advance, nice weekend
    Oliver

    Hey John,
    piece of cake ;).. that's what I thought at first. Unfortunately it´s not that easy. This is because of  partially really strict restrictions within the SAP-Software.
    At the one Module, you can choose the destination, is used for a particular group of functions. At the next, you simply can´t. SAP says "you need to have a destination, named as the logical system name". And there is no way around.
    Maybe I´am the first guy being disturbed by this "feature"....
    Of cause, I already placed several posts within the basis section... but still.. no way around. In one case I even opened a ticket at SAP... (I already posted the answer above) ....
    Thx anyways!
    Oliver

  • JDBC to Idoc scenario - change of logical system name

    Hi,
    I have a JDBC to idoc scenario that worked. Now i had to change the logical system name from my sender system from ABC_123 into ABC123 in the SLD (Business System - Integration - Logical System name). I did so and also refreshed my Cache.
    Afterwards I started the process, but it failed in the Receiver system. The idoc is correct expect of the partner name. My receiver system expect ABC123 - as I changed in the SLD - but PI send ABC_123.
    If io look in SXI_CACHE - Services my Business System still got the "old" name (ABC_123).
    Did i miss something resp. how can i load the current configuration from SLD?
    Thanks in advance
    Michael

    Hi Michael,
    Again Import the changed logical system in the Integration directory of you PI system.
    And check the scenario (Sender Agreement, Receiver agreement ) what system they are reflecting.
    If they are showing old system then you have to replace the business system in all the scenario.
    Edited by: Rajhans Abhay on Jan 7, 2010 3:14 PM

Maybe you are looking for