Show TOC

Background documentationConfiguration of SAPMEINT Standard Interfaces

 

The following documentation describes where to verify and modify the values SAPMEINTCTC creates for the SAPMEINT standard interfaces.

The SAPMEINT standard interfaces are installed and configured using the SAPMEINTCTC configuration wizard. For more information, see SAP ME Installation Guide available at Start of the navigation path http://service.sap.com/instguidesInformation published on non-SAP site Next navigation step SAP Business Suite Applications Next navigation step SAP Manufacturing Next navigation step SAP Manufacturing Execution 15.1 End of the navigation path.

Recommendation Recommendation

If the SAPMEINTCTC template was interrupted by any reason, resolve the root cause issue and re-execute the CTC wizard according to the Installation Guide.

If you notice any incorrect configurations, re-execute the SAPMEINTCTC wizard with correct values according to the Installation Guide. Only advanced users may need to edit the values entered by SAPMEINTCTC.

End of the recommendation.
Configuring Data Sources in SAP NetWeaver Java AS

SAPMEINTCTC creates two data sources, SAPMEINT and SAPMEWIP. These data sources are used by the SAPMEINT interfaces.

Data Source

Data Source Alias

Description

SAPMEINT

jts/SAPMEINT

Used to do CRUD operations on SAPMEINT database

SAPMEWIP

jts/SAPMEWIP

Used to read data from SAP ME WIP database

To modify the data source configurations, proceed as follows:

  1. Log on to SAP NetWeaver Administrator using the following URL: http://<AP Java host>:<HTTP port>/nwa.

  2. Choose Start of the navigation path Configuration Management Next navigation step Infrastructure Next navigation step Application Resources End of the navigation path.

  3. Search for SAPMEINT or SAPMEWIP as the Resource Name.

  4. Select the desired data source and make the necessary modifications on the following data source properties:

A data source for the MS SQL Server database is configured as follows:

Parameters

Field

Example Value

Driver Name

SAPMEINT_SQL

SQL Engine

Vendor SQL

Isolation level

Default

JDBC Version

2.0 (with XA support)

Object Factory

DataSource Type

ConnectionPool data source

CPDS Class Name

com.microsoft.sqlserver.jdbc.SQLServerConnectionPoolDataSource
Connection Pooling Parameters

Field

Example Value

Initial Connections

10

Maximum Connections

25

Maximum Time to Wait for Connection

120
Additional Properties

Field

Example Value

URL

Default instance:

jdbc:sqlserver://PROTEUS:1433

Name instance:

jdbc:sqlserver://PROTEUS\SAPME:1433

Password

******

User

qa_nwsapme61wip

Database Name

SAPMEWIP

Server Name

PROTEUS

A data source for the Oracle database is configured as follows:

Parameters

Field

Example Value

Driver Name

SAPMEINT_ORA_10_2

SQL Engine

Vendor SQL

Isolation Level

Default

JDBC Version

2.0 (with XA support)

Object Factory

Data Source Type

ConnectionPool Data source

CPDS Class Name

oracle.jdbc.pool.OracleConnectionPoolDataSource
Connection Pooling Parameters

Field

Example Value

Initial Connections

10

Maximum Connections

25

Maximum Time to Wait for Connection

120
Additional Properties

Field

Example Value

URL

jdbc:oracle:thin:@ PROTEUS:1527:SAPME

Password

******

User

qa_nwsapme61wip

Server Name

PROTEUS

After creating the data sources, make sure that the SAPMEWIP and SAPMEINT data sources are running and in a Fully Available state.

Configuring SAPMEWIP Data Server in SAP MII

  1. In the SAP MII main menu, choose Start of the navigation path Data Services Next navigation step Data Servers End of the navigation path.

  2. Select Data Source and choose SAPMEWIP.

  3. Make the desired modifications:

    Field

    Value

    Name

    SAPMEWIP

    Connector

    Datasource

    Connector Type

    SQL

    Data Source

    jdbc/jts/SAPMEWIP

    Enabled

    Selected

    Date Prefix

    '

    Date Suffix

    '

    Days Retention

    7

    Description

    SAPMEWIP

    Internal Date Format

    MM/dd/yyyy HH:mm:ss

    Max. Retry Count

    5

    Retry Interval

    60000

    Server Package

    com.sap.xmii.Illuminator.connectors.IDBC

    Note Note

    If the database is Oracle, use the following parameter values:

    Date Prefix: TO_DATE('

    Date Suffix: ','MM/DD/YYYY HH24:MI:SS')

    End of the note.

  4. Save your entries.

  5. Choose Status to verify connectivity to the SAPMEWIP.

    The status must be Running.

Configuring SAPMEINT Data Server in SAP MII

Note Note

You can use one database to store both SAP ME and SAPMEINT data if needed. For more information, see SAP Note 1409811Information published on SAP site — SAP ME System Landscape Recommendations.

End of the note.

  1. On the SAP MII main menu, choose Start of the navigation path Data Services Next navigation step Data Servers End of the navigation path .

  2. Select Data Source and choose SAPMEINT.

  3. Make the desired modifications:

    Field

    Value

    Name

    SAPMEINT

    Connector

    Datasource

    Connector Type

    SQL

    Data Source

    jdbc/jts/SAPMEINT

    Enabled

    Selected

    Date Prefix

    '

    Date Suffix

    '

    Days Retention

    7

    Description

    SAPMEINT

    Init. Command

    Internal Date Format

    MM-dd-yyyy HH:mm:ss

    Max. Retry Count

    5

    Retry Interval

    60000

    Server Package

    com.sap.xmii.Illuminator.connectors.IDBC

    Note Note

    If the database is Oracle, use the following parameter values:

    Date Prefix: TO_DATE('

    Date Suffix: ','MM/DD/YYYY HH24:MI:SS')

    End of the note.

  4. Save your entries.

  5. Choose Status to verify connectivity to the SAPMEINT.

    The status must be Running.

Configuring MESYS User in SAP NetWeaver

SAPMEINTCTC creates the MESYS user in SAP NetWeaver where SAPMEINT and SAP ME are deployed. In the case of a clustered environment, SAPMEINTCTC creates the MESYS user in both instances of SAP NetWeaver.

This user is used for any SAP ME API or web service calls. For more information about configuring a user in SAP NetWeaver, see Identity Management.

Configuring Credentials in SAP MII
Credential for SAP ME API and Web Service Calls

SAPMEINTCTC creates the credential SAPMEINT_ME_AUTH in SAP MII. To modify the password for the credential, proceed as follows:

  1. On the SAP MII main menu, choose Start of the navigation path Security Services Next navigation step Credential Stores End of the navigation path.

  2. Choose the credential SAPMEINT_ME_AUTH.

  3. Enter a new password for the MESYS NetWeaver user.

  4. Confirm the password.

  5. Save your entries.

Note Note

Make sure that the password for the MESYS user is also modified in SAP NetWeaver server where SAP ME is deployed.

End of the note.

Recommendation Recommendation

Do not change the user name (MESYS) for this credential.

End of the recommendation.
Credential for BAPI Calls to SAP ERP

SAPMEINTCTC creates the credential SAPMEINT_ALE in SAP MII. To modify this credential, proceed as follows:

  1. On the SAP MII main menu, choose Start of the navigation path Security Services Next navigation step Credential Stores End of the navigation path.

  2. Choose the credential SAPMEINT_ALE.

  3. Enter the desired user name.

  4. Enter a new password for the user.

  5. Confirm the password.

  6. Save your entries.

Configuring Role_SAPMEINT Role in SAP NetWeaver

SAPMEINTCTC creates the role Role_SAPMEINT in SAP NetWeaver where SAP MII and SAPMEINT are deployed and running.

For more information about configuring roles, see Administration of Users and Roles.

Configuring SAP ERP ALE

You need to configure SAP ERP to send IDocs to the SAP MII server. This involves the following procedures:

  1. Creating a logical system for the SAP MII server within SAP ERP

  2. Creating a TCP/IP RFC destination to the SAP MII server

  3. Testing the connectivity of the RFC destination to the SAP MII server

  4. Creating a port

  5. Creating a partner profile configured for the following IDoc types:

  6. Creating a distribution model

For more information, see Customizing for ALE for Communication with SAP ME.

Configuring Message Listener

SAPMEINTCTC creates the message (IDoc) listener in SAP NetWeaver to receive notifications of IDocs from SAP ERP server and download the IDoc. To make modifications to the Message Listener configuration, proceed as follows:

  1. Log on to SAP NetWeaver Administrator using the following URL: http://<host>:<port>/nwa.

  2. Choose Start of the navigation path Configuration Management Next navigation step Infrastructure Next navigation step Application Resources End of the navigation path.

  3. Select Resource Adapters from the dropdown list.

  4. Select the resource configured by SAPMEINTCTC, such as XMIIIDOC01, that you want to modify in the table.

  5. Choose Properties tab in the bottom window.

  6. Edit the properties to match your SAP ERP server.

  7. Save your entries.

Example Example

Field

Example Value

Program ID

XMII_RHEA

Max. Reader Thread Count

1

SAP Client

210

User Name

ALE_USER — a valid SAP ERP user to perform ALE communication

Password

******

Language

EN

Server Name

sapdev.sap.com

Port Number

03

Binding Key

XMIIIDOC — use the default value

For more information, see Customizing for ALE for Communication with SAP ME.

End of the example.

After configuring the resource, make sure that this configuration works by doing the following:

  1. Check that the resource, is in a running and Fully Available state.

  2. In the SAP MII menu, expand Message Services and choose Message Listener.

  3. Select the message listener configured by SAPMEINTCTC, such as XMIIIDOC01 and choose Update.

    Note Note

    If there are correct values in the SAP Server, SAP Client, and Message Name fields, do not choose Update.

    End of the note.

  4. Choose Status.

    The following message appears: Server Connected.

Configuring the Processing Rule

SAPMEINTCTC creates a processing rule for all incoming messages in SAP MII Message Services. The <Name of the IDoc Listener>_ALL_MESSAGES processing rule specifies how incoming IDocs are processed by SAP MII.

We do not recommend that you change this processing rule. To view the details of the rule, proceed as follows:

  1. In the SAP MII main menu, expand Message Services and choose Processing Rule Editor.

  2. Select the <Name of the IDoc Listener>_ALL_MESSAGES processing rule.

  3. View the settings.

SAPMEINTCTC configures this processing rule with the following values:

Field

Value

Name

<Name of the IDoc Listener>_ALL_MESSAGES

Description

<Name of the IDoc Listener>_ALL_MESSAGES

Message Listener

Name of the IDoc Listener

Message Type

IDOC

Message Name

*

Processing Type

Category

Category

SAPMEINT_INBOUND_QUEUE

Category Description

SAPMEINT_INBOUND_QUEUE
Configuring the SAP ERP Server Connection

SAPMEINTCTC configures the SAP ERP server connection in SAP MII to make BAPI calls to SAP ERP. SAPMEINTCTC creates the SAP ERP server connection with the following naming convention <Name of the IDoc Listener>_SAP_JCO, where <Name of the IDoc Listener> is the IDoc Listener configured by SAPMEINTCTC. To modify the configuration, proceed as follows:

  1. On the SAP MII main menu, expand Data Services and choose Connections.

  2. Choose Connect Type JCO.

  3. Choose New.

  4. Select the desired SAP ERP server.

    You can modify the following properties:

    Field

    Value

    Description

    <Name of the IDoc Listener>_SAP_JCO

    Server

    <Your SAP ERP server host name>

    Client

    <Your SAP ERP client for production>

    System

    <Your SAP ERP system number>

    Pool Size

    <Pool size for your JCo resource>

    Language

    EN

  5. Save your entries.

Configuring SAPMEINT MII Web Services in SAP NetWeaver Java AS

SAPMEINTCTC configures the SAP NetWeaver system properties for the SAP MII transactions web services to work. To modify this configuration, proceed as follows:

  1. Log on to SAP NetWeaver Administrator console using the following URL: http://<host>:<port>/nwa.

  2. Choose Start of the navigation path Configuration Management Next navigation step Infrastructure Next navigation step Java System Properties Next navigation step Applications End of the navigation path.

  3. On the Applications tab page, search for the xapps~me~integration~ear application.

    You can edit the following properties:

    Name

    Custom Value

    webservice.authenticationMechanismType

    SAPMEINTCTC configuration defaults this value to 1 and this value should not be modified.

    webservice.UserName

    <SAP NetWeaver User who has the Role_SAPMEINT role assigned to access SAP MII transactions and Web services>

    SAPMEINTCTC configuration defaults this value to the user MESYS.

    webservice.Password

    <User password>

    webservice.EndPointUrlPrefix

    The default value:

    http://localhost:50000/XMII/SOAPRunner

    SAPMEINTCTC configures this value using the server name and port of the SAP MII server.

  4. Save your entries.

Configuring SAPMEINT Workflow

To configure SAPMEINT workflow, you need to log on as the user with the Role_SAPMEINT role assigned.

SAPMEINT Global Configuration

SAPMEINTCTC configures SAPMEINT Global Configuration properties with the values provided during the SAPMEINTCTC configuration process. To modify this configuration, proceed as follows:

  1. In the SAP MII Dashboard menu, choose Start of the navigation path SAP ME ERP Integration Next navigation step Administration Next navigation step Global Configuration End of the navigation path.

    You can modify the following global configuration properties:

    Property

    Description

    Example Value

    SAPMEINT_PartnerMessageDiscriminatorTxn

    See Note below

    SAPMEINTCTC defaults this parameter to an empty value.

    SAPMEINT_CustomerMessageDiscriminatorTxn

    See Note below

    SAPMEINTCTC defaults this parameter to an empty value.

    SAPMEINT_CORRELATION_RETENTION_PERIOD

    Defines a period in minutes for a message that is waiting for next processing in case correlation conditions were not met.

    10

    SAPMEINT_RETRY_RETENTION_PERIOD

    Defines the retention period in minutes for a message to be retried after a system error

    30

    SAPMEINT_OEE_Max_Buckets

    The number of times to display the buckets in the OEE Report

    12

    SAPMEINT_ME_User

    SAP ME user

    MESYS

    SAPMEINT_ME_Application_Context

    The Web context root for SAP ME application

    /manufacturing

    SAPMEINT_ME_Port

    Server port on which SAP ME listens for all HTTP requests

    50000

    SAPMEINT_DB_Vendor

    Database vendor for the SAPMEINT data source

    ORACLE, SQLSERVER

    SAPMEINT_ME_Host

    Host name of SAP ME server

    vmserv1, vmserv.acme.com

    SAPMEINT_IS_PROFILING_ENABLED

    Controls whether Profiling is active (TRUE) or inactive (FALSE).

    TRUE

    Note Note

    The Message Discriminator transaction is responsible for building a valid identifier typeId (DOC_TYPE) for each incoming message to SAPMEINT. SAPMEINT uses this typeId to determine the workflow associated with this message.

    SAPMEINT comes with pre-built standard discrimination logic to determine the typeId of a message.

    If you want to customize this logic, you can configure your discrimination logic using the following Global Configuration properties:

    • SAPMEINT_CustomerMessageDiscriminatorTxn

    • SAPMEINT_PartnerMessageDiscriminatorTxn

    The SAPMEINT system checks if SAPMEINT_CustomerMessageDiscriminatorTxn has been configured; if it has been configured, it executes it; otherwise it executes the transaction defined in SAPMEINT_PartnerMessageDiscriminatorTxn if it has been configured.

    If the value for the output parameter type of these transactions is not empty, SAPMEINT uses this value as the typeId for the message, but if the value returned from these transactions is empty, the standard SAPMEINT discrimination logic executes and tries to find the typeId of the message.

    End of the note.

  2. Save your entries.

Workflow Parameters

SAPMEINTCTC configures SAPMEINT workflows with default values. These default values work for most of the scenarios. If any of the workflow parameters need to be changed, proceed as follows:

  1. In the SAP MII Dashboard menu, choose Start of the navigation path SAP ME ERP Integration Next navigation step SAPMEINT Configuration Next navigation step Workflow Configuration End of the navigation path.

  2. Retrieve the workflow parameter for the desired interface by choosing the Type ID.

  3. Make the necessary modifications.

  4. Save your entries.

Configuring the SAP MII Schedulers

SAPMEINTCTC configures the SAP MII Schedulers to process queued messages in SAPMEINT. To modify this configuration, proceed as follows:

  1. In the SAP MII main menu, choose Start of the navigation path System Management Next navigation step Scheduler End of the navigation path.

  2. Select the desired scheduler.

  3. Modify the desired properties.

    InboundMessageEnqueuer Properties

    Field

    Value

    Name

    InboundMessageEnqueuer

    Description

    Dispatcher for queued inbound SAPMEINT messages

    Enabled

    Selected

    Transaction

    Visiprise/ERPShopFloorIntegration/InboundEnqueuer/InboundEnqueuer

    User

    A valid SAP MII user who has enough permission to run the Scheduler

    Password

    The password for the SAP MII user

    Parameters

    • deleteAfterEnqueuing

      Deletes messages after queuing them in the SAPMEINT message queue. SAPMEINTCTC defaults this parameter with a value of true

    • messageName

      The name of the inbound message to queue. Use * for all inbound messages. SAPMEINTCTC defaults this parameter with a value of *

    • numberOfMessages

      The number of queued messages to be processed for this scheduler task run. SAPMEINTCTC defaults this parameter with a value of 200.

    • serverName

      The name of the message listener. SAPMEINTCTC defaults this parameter with a value of XMIIIDOC01

    Pattern

    Your pattern
    MessageDispatcher Properties

    Field

    Value

    Name

    MessageDispatcher

    Description

    Dispatcher for queued SAPMEINT messages

    Enabled

    Selected

    Transaction

    Visiprise/ERPShopFloorIntegration/frame/dispatchers/simpleDispatcher/SimpleMessageDispatcher

    User

    A valid SAP MII user who has enough permission to run the Scheduler

    Password

    The password for the SAP MII user

    Parameters

    numberOfMessages

    The number of queued messages to be processed for this scheduler task run. SAPMEINTCTC defaults this parameter with a value of 50.

    Pattern

    Your pattern
    MessageEnqueuer Properties

    Field

    Value

    Name

    MessageEnqueuer

    Description

    Dispatcher to enqueue SAP ME outbound messages from the Outbound ME Messages queue into the Integration Message Queue for processing by the Message Dispatcher scheduler job

    Enabled

    Selected

    Transaction

    Visiprise/ERPShopFloorIntegration/SAPMEMessageEnqueuer/SAPMEMessageEnqueuingDispatcher

    User

    A valid SAP MII user who has enough permission to run the Scheduler

    Password

    The password for the SAP MII user

    Parameters

    • deleteAfterQueuing

      Controls if the queued message is deleted after being processed; SAPMEINTCTC defaults this parameter with a value of true

    • numberOfMessagaes

      The number of queued messages to be processed for this scheduler task run. SAPMEINTCTC defaults this parameter with a value of 200.

    Pattern

    Your pattern
    QueueMessageCleaner Properties

    Field

    Value

    Name

    QueueMessageCleaner

    Description

    Dispatcher to delete the old SAPMEINT messages

    Enabled

    Selected

    Transaction

    Visiprise/ERPShopFloorIntegration/MessagePurging/MessageCleaner

    User

    A valid SAP MII user who has enough permission to run the Scheduler

    Password

    The password for the SAP MII user

    Parameters

    messageRetentionPeriod

    The number of hours the messages will be kept in the system after they are received into SAPMEINT. SAPMEINTCTC defaults this parameter with a value of 24.

    Pattern

    Your pattern

  4. Save your entries.

Configuring SAP ME

See SAP ME Configuration for SAP ME ERP Integration.

Configuring Supported SAP ME Plants

SAPMEINTCTC configures supported SAP ME sites that correspond to SAP ERP plants during the SAPMEINTCTC execution. To modify this configuration, proceed as follows:

  1. On the SAP MII Dashboard menu, choose Start of the navigation path SAP ME ERP Integration Next navigation step SAPMEINT Configuration Next navigation step Supported SAP ME Plants End of the navigation path.

  2. On the Supported SAP ME Plants screen, choose the SAP ME site (plant) to modify.

    You can modify the following properties:

    Field

    Example Value

    Plant Language

    E – This value should match with the language field in the IDocs.

    Note Note

    The language field for MATMAS and LOIWCS can be found in SPRAS and the language field for DOCMAS can be found in LANGU.

    End of the note.

    SAP ERP Server

    <Name of the IDoc Listener>_SAP_JCO

    SAP ME Host URL

    http://<host>:<port>

    SAP ERP Server Time Zone

    US/Eastern

    SAP ME Server Time Zone

    US/Eastern
Configuring SAP ME Web Services

SAPMEINTCTC configures SAP ME web services during the SAPMEINTCTC execution. To modify these configurations, proceed as follows:

  1. Log on to SAP NetWeaver Administrator Console using the following URL: http://<host>:<port>/nwa.

  2. Choose Start of the navigation path SOA Next navigation step Application and Scenario Communication Next navigation step Single Service Administration End of the navigation path.

  3. Search for the following web services:

    • AlarmProcessingIn

    • ERPBOMProcessingIn

    • ErpItemProcessingIn

    • NextNumberProcessingIn

    • OperationProcessingIn

    • ErpProductionProcessingIn

    • ErpRouterProcessingIn

    • ProductionProcessingIn

    • ProductionOrderProcessingIn

    • ERPShoporderProcessingIn

    • ItemCustomData

    • ERPUserProcessingIn

    • ServiceOrderProcessingIn

    • ResourceProcessingIn

    • WorkCenterProcessingIn

  4. Select each port type, for example AlarmProcessingIn.

  5. In the bottom window, choose the Configuration tab and select associated ServicePort, for example ProductionAlarmServicePort.

  6. Choose the Security tab.

  7. Choose Edit.

  8. Select the Transport protocol.

  9. Check the User ID/Password under HTTP Authentication.

  10. Save your entries.

  11. Repeat the steps above for each port.

Clearing SAP MII Transaction Cache

As a final step after the configuration of SAPMEINT, clear the transaction cache by executing the following URL:

http://<host>:<port>/XMII/Illuminator?Service=BLSManager&Mode=ClearCache&Type=Transaction