pacemaker+corosyncでのtomcat連携について

★以下について、tomcat@tomcat.serviceを作成することでtomcat登録が正常に行えました。
しかし、なぜpacemaker+corosyncはtomcat.serviceではなく、tomcat@tomcat.serviceを
必要としていたのでしょうか？
【追記】tomcat@tomcat.serviceは既存のtomcat.serviceをコピーして作成しました。

pacemaker+corosyncに、リソースとしてtomcatを登録したいのですが、下記エラーが発生し、登録に失敗します。

Jan 27 06:33:11 [32248] osact       lrmd:   notice: operation_finished: Tomcat_Cluster_start_0:5314:stderr [ Failed to start tomcat@tomcat.service: Unit not found. ]

エラー要因はなんでしょうか？
※tomcat@tomcat.serviceが無いことらしいのですが、
/usr/lib/systemd/system配下には、tomcat.serviceおよびtomcat@.serviceは
存在します。
※pacemaker+corosyncを介さずに、systemctl start tomcat で正常にtomcat起動でき、http://localhost:8080へも正常アクセスできることは確認済みです。

■環境情報
OS:CentOS7.3.1611
pacemake:1.1.15
corosync:2.4.0
tomcat:8.5.11

■(追記)pcs config実行結果

[root@osact ~]# pcs config 
Cluster Name: cluster_os
Corosync Nodes:
 osact ossby
Pacemaker Nodes:
 osact ossby

Resources:
 Resource: VIP (class=ocf provider=heartbeat type=IPaddr2)
  Attributes: ip=192.168.172.9 cidr_netmask=24
  Operations: start interval=0s timeout=20s (VIP-start-interval-0s)
              stop interval=0s timeout=20s (VIP-stop-interval-0s)
              monitor interval=10s (VIP-monitor-interval-10s)
 Resource: Web_Cluster (class=ocf provider=heartbeat type=apache)
  Attributes: configfile=/etc/httpd/conf/httpd.conf statusurl=http://127.0.0.1/server-status
  Operations: start interval=0s timeout=40s (Web_Cluster-start-interval-0s)
              stop interval=0s timeout=60s (Web_Cluster-stop-interval-0s)
              monitor interval=1min (Web_Cluster-monitor-interval-1min)
 Resource: Tomcat_Cluster (class=ocf provider=heartbeat type=tomcat)
  Attributes: statusurl=http://127.0.0.1:8080/ java_home=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-0.b13.el7_3.x86_64/jre catalina_home=/usr/tomcat8 tomcat_user=tomcat
  Operations: start interval=0s timeout=60s (Tomcat_Cluster-start-interval-0s)
              stop interval=0s timeout=120s (Tomcat_Cluster-stop-interval-0s)
              monitor interval=1min (Tomcat_Cluster-monitor-interval-1min)

Stonith Devices:
Fencing Levels:

Location Constraints:
  Resource: VIP
    Enabled on: osact (score:INFINITY) (role: Started) (id:cli-prefer-VIP)
    Disabled on: ossby (score:-INFINITY) (role: Started) (id:cli-ban-VIP-on-ossby)
Ordering Constraints:
  start VIP then start Web_Cluster (kind:Mandatory) (id:order-VIP-Web_Cluster-mandatory)
  start Web_Cluster then start Tomcat_Cluster (kind:Mandatory) (id:order-Web_Cluster-Tomcat_Cluster-mandatory)
Colocation Constraints:
  Web_Cluster with VIP (score:INFINITY) (id:colocation-Web_Cluster-VIP-INFINITY)
  Tomcat_Cluster with VIP (score:INFINITY) (id:colocation-Tomcat_Cluster-VIP-INFINITY)
  Resource Sets:
    set VIP (id:pcs_rsc_set_VIP_Tomcat_Cluster) setoptions score=INFINITY (id:pcs_rsc_colocation_set_VIP_Tomcat_Cluster)
    set VIP Tomcat_Cluster (id:pcs_rsc_set_VIP_Tomcat_Cluster-1) setoptions score=INFINITY (id:pcs_rsc_colocation_set_VIP_Tomcat_Cluster-1)
Ticket Constraints:

Alerts:
 No alerts defined

Resources Defaults:
 No defaults set
Operations Defaults:
 No defaults set

Cluster Properties:
 cluster-infrastructure: corosync
 cluster-name: cluster_os
 dc-version: 1.1.15-11.el7_3.2-e174ec8
 have-watchdog: false
 last-lrm-refresh: 1485467664
 no-quorum-policy: ignore
 stonith-enabled: false

Quorum:
  Options:
[root@osact ~]#