on 03-22-2016 7:04 PM
Dear Experts,
I have a distributed installation and my Message Server is under a Z/OS environment. So far so good.
As supposed, SUM does not run under z/OS, we also have a solution for that, we will bring Message Server to AIX, so it will work BUT we may count problems now:
1 - Changing the Message Server from z/OS to AIX will interfere in users access as they use LogonGroup to connect.
2 - My Portal/BW/PI... totally points to Message Server on z/OS, and we should have a lot of work to change it.
3 - The master question is that we want to run SUM over 2 weekends and it triggers problems 1 and 2, Weekend 1, run the preparation and let it on the step
before of executing. Weekend 2, run the Execution Phase
Do you guys have any idea of how I can get over it?
Regards,
Gabriel
Have you checked the latest SUM guide? Download the SUM guide for version 16 and check the chapter 3.19 Update of Distributed and High Availability Systems
>> Process
The update process for a high availability system is briefly outlined below:
1. If necessary, you change your HA system configuration and clean up profiles. For more information, see section Preparing the Update of Distributed and High Availability Systems [page 98].
2. You start the Software Update Manager on the host with the primary application server instance. If this instance is installed on one of the Microsoft Failover Cluster nodes, start the Software Update Manager on the cluster node where the primary application server instance runs.
3. The Software Update Manager checks the profile directory and, if the ASCS instance is installed with a different host name, assumes that the update runs in a distributed or high availability environment.
4. If prompted, you install a temporary license key in the shadow system and in the system during downtime. For information about license keys, see https://support.sap.com/licensekey.Note
Note that the new temporary license will not be removed automatically after the update. You can delete the temporary license manually after the update. Prior to this, use transaction SLICENSE to check whether the old license still exists.
5. If you are running the ASCS instance on a separate host, and the operating system on this host is different from that on the primary application server instance, at the end of the downtime you are prompted to install the latest SAP kernel on the separate host with the ASCS instance.<<
If they users use logon groups to access the SAP system then there shouldn't be any problem. As long as the message server is reachable they should be able to connect.
In addition the blog about says this:
>> If a more powerful machine is required for the R3load processes, it might be an option to run the SUM on a powerful Additional Application Server (AAS) instance with free resources.
In general, SUM and SUM with DMO may be executed not only on the Primary Application Server (PAS), but also on an Additional Application Server (AAS). However, running SUM with DMO on an AAS is only supported if your system has a separate ASCS instance.<<
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Gabriel,
Are you facing any issue while running the SUM while keeping the Message server on Z/OS.
With Regards
Ashutosh Chaturvedi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Gabriel,
You can create a alias hostname similar to the existing z/OS host name on an existing AIX system.
Use the alias name for the message server and it will not affect the existing configuration of connection management.
You can involve the OS and Network team to do so.
If you have a spare server of AIX , you can keep the same host name and instance number of message server.
Then start the SUM.
With Regards
Ashutosh Chaturvedi
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.