TWS for Apps, SAP configuration

SAP side configuration:

Copy the 4 correction and transport files from the Tivoli Workload Scheduler home directory to the SAP R/3 server and import them into the SAP R/3 database, as follows:

     1. On your SAP R/3 database server, log on to the SAP R/3 system as an administrator.

     2. Copy the control file and data file from the <TWA_home>\methods directory to the following directories on your SAP R/3 database server:

copy  control_file to /usr/sap/trans/cofiles/
copy data_file to /usr/sap/trans/data/

The names of control_file and data_file are different for releases and are located in <TWA_home>\methods with the following names and formats:
      For SAP R/3 releases earlier than 6.10:

control_file: K000xxx.TV1, K900xxx.TV2
data_file: R000xxx.TV1, R900xxx.TV2

      For SAP R/3 releases 6.10, or later:

control_file: K9000xx.TV1, K9007xx.TV1
data_file: R9000xx.TV1, R9007xx.TV1

where xx is a digit generated by the SAP system

Specifically, for Tivoli Workload Scheduler for Applications version 8.5 the following files are used:
      For SAP R/3 releases earlier than 6.10:

for standard jobs scheduling: K000538.TV1, R000538.TV1
for IDoc monitoring and job throttling: K900294.TV2, R900294.TV2

      For SAP R/3 releases 6.10, or later:

for standard jobs scheduling: K900044.TV1, R900044.TV1
for IDoc monitoring and job throttling: K900751.TV1, R900751.TV1

TWS side configuration (on the server where TWS for Applications was deployed):

After a new TWS4APPS installation, if you try to start a SAP job, you will get missing library error(s), to fix the problem, take the following steps:
      1. Check the LINK and search for SAP Remote Function Call libraries, to see which RFC libraries are needed – check the OS type where TWS4APPS is installed and look it to the .pdf table.
      2. The libraries should be available on SAP WebSite (help from SAP team may be needed, to download them).
      3. The libraries are compressed in car format, with file extension .sar, once you uncar them, copy the content of lib directory to the agent there TWS4APPS is installed in the <TWA_home>\methods folder.

Example of how to uncar the .sar file:

RFC_7-10009745.SAR
SAPCAR_315-20010450.exe

Place the SAPCAR and the CAR file in the same directory

./SAPCAR_315-20010450.exe -xvf RFC_7-10009745.SAR

Copy the content of lib directory, from the newly created directory tree, to the agent where TWS4APPS is installed, in the <TWA_home>\methods folder.

TWS Licensing

TWS Licensing can be performed (based on the needs):

1. Using PVU (Processor Value Unit) licensing  - recommended for a high number of jobs.
2. Using per jobs licensing - recommended for a high number of servers where the jobs needs to run

   1. PVU (Processor Value Unit) licensing it is a unit of measure by which the program can be licensed. The number of PVU entitlements required is based on the processor technology defined by processor value, brand, type, and model number in other words it is based on the CPU cores available to the machine (server) physical / virtual where TWS is deployed and runs jobs, a detailed list can be found on IBM site in PVU table.
e.g. An AMD Opteron: 1 socket with 8 cores per socket has a PVU value of: 1 x 8 x 50 = 500
An Oracle/Sun SPARC M6: 8 sockets with 6 cores per socket has a PVU value of: 8 x 6  x 120 = 5760

Also TWS PVU Licensing supports Sub-Capacity (Virtual) Licensing, in some cases, which in short words you only need to license the cores assigned to a virtual machine rather then the whole cores of the physical one (more details can be found on IBM Passport Advantage Virtualization Capacity (Sub-capacity) Licensing page).
e.g. In you have a Linux farm of 64 physical cores and a virtual machine with 8 cores assigned and it is running TWS you can licence only 8 cores.

!!!!!! Important For Sub-Capacity (Virtual) Licensing iLMT (IBM License Metric Tool) needs to be deployed on each of the systems for which you want to apply the Sub-Capacity licensing.

!!!!!! Important For TWS For Applications the Sub-Capacity (Virtual) Licensing doesn't apply, always you need to license the physical cores on the machine (be careful where you deploy TWS for Apps)

   2. Per jobs licensing in other words you will licence the number of jobs ran (aka 10 MONTHLY JOBS License).
e.g.
Number of daily executed jobs: 500
Number of monthly executed jobs (multiply by 31 ): 15,500
Number of groups of 10 jobs: 1,550 (divide by 10 as the part is per 10 Monthly Jobs)
List price of IBM Workload Automation for 10 jobs equals: X
List price is calculated at 1,550 job packs of 10 jobs multiplied by X.


Additional details about Standby or backup systems — For programs running or resident on backup machines, IBM defines three types of situations: cold, warm and hot. In cold and warm situations, a separate entitlement for the copy on the backup machine is normally not required and typically no additional charge applies. In a hot backup situation, the customer needs to acquire other licenses or entitlements sufficient for that server.

• Cold: A copy of the program may reside, for backup purposes, on a machine as long as the program is not started. There is no additional charge for this copy. 
• Warm: A copy of the program may reside for backup purposes on a machine and is started, but is idling, and is not doing any work of any kind. There is no additional charge for this copy. 
• Hot: A copy of the program may reside for backup purposes on a machine, is started, and is doing work. The customer must acquire a license or entitlement(s) for this copy and there will generally be an additional charge. Doing work includes, for example, production, development, program maintenance, and testing. It also could include other activities such as mirroring of transactions, updating of files, synchronization of programs, data, or other resources (for example, active linking with another machine, program, database or other resource, and so on), or any activity or configurations that would allow an active hot switch or other synchronized switch-over between programs, databases, or other resources to occur. In the case of a program or system configuration that is designed to support a high availability environment by using various techniques (for example, duplexing, mirroring of files, or transactions, maintaining a heartbeat, active linking with another machine, program, database, or other resource), the program is considered to be doing work in the hot situation and a license or entitlement must be purchased. 

!!! Note: For TWS masters, if they run only TWS application jobs e.g. FINAL, the licence is not required.

Examples of calculation:
A TWS env. as in the picture below:

And the current price for both cases:

The licence calculation will be:
1. Using PVU licensing:

• ERP Server: Oracle/Sun SPARC M6: 8 sockets with 6 cores per socket PVU usage: 8 x 6 x 120 = 5,760
• Warehouse: AMD Opteron: 2 sockets with 8 cores per socket PVU usage: 2 x 8 x 50 = 800
• ETC: Intel Xeon 7500: 1 socket with 6 cores per socket  PVU usage: 1 x 6 x 120 = 720
• TWS Master doesn't run jobs no PVU usage.

For 1 year the TWS PVU licence and support will be: (5,760 + 800 + 720) x 40.5 = 294,840 USD

2. Using per jobs licensing:

• ERP Server: running 500 jobs / day, in a month 500 x 31 = 15,500, divide by 10 as the part is per 10 Monthly Jobs is 1,550 groups
• Warehouse: running 50 jobs / day, in a month 50 x 31 = 1,550, divide by 10 as the part is per 10 Monthly Jobs is 155 groups
• ETC: running 10 jobs / day, in a month 10 x 31 = 310, divide by 10 as the part is per 10 Monthly Jobs is 31 groups
• TWS Master doesn't run jobs no PVU usage.

For 1 year the TWS per job licence and support will be: (1,550 + 155 + 31) x 56.25 = 97,650 USD.

So in this particular case TWS per job licence will be the best fit as it costs ~67% less.