Exact Globe+ Integration

Portway provides integration with the API-layer of Exact Globe+ (previously known as Globe Next) through proxy endpoints, enabling external applications to interact with Globe+ data and services. This integration relies on environment-specific headers to route requests to the correct database instance.

Overview ​

The Exact Globe+ integration uses Portway's proxy endpoints to forward requests to the internal Globe+ REST services. Each request must include proper environment configuration to ensure data is accessed from the correct database and server.

Configuration Requirements ​

Environment Headers ​

All requests to Globe+ endpoints require two critical headers that are automatically added based on the environment:

These headers are configured in the environment settings and automatically injected into proxy requests.

Environment Settings ​

Each environment must be properly configured in the settings:

// environments/500/settings.json
{
  "ServerName": "YOUR-SERVER",
  "ConnectionString": "Server=YOUR-SERVER;Database=500;Trusted_Connection=True;",
  "Headers": {
    "DatabaseName": "500",
    "ServerName": "YOUR-SERVER",
    "Origin": "Portway"
  }
}

Available Globe+ Endpoints ​

Proxy Endpoints ​

You can configure the availability of the Globe+ endpoints, by configuring a proxy endpoint.

Composite Endpoints ​

These endpoints handle complex operations that require multiple related transactions:

Sales Order Creation ​

POST /api/{env}/composite/SalesOrder
Content-Type: application/json

{
  "Header": {
    "OrderDebtor": "60093",
    "YourReference": "Connect async"
  },
  "Lines": [
    {
      "Itemcode": "ITEM-001",
      "Quantity": 2,
      "Price": 0
    },
    {
      "Itemcode": "ITEM-002",
      "Quantity": 4,
      "Price": 0
    }
  ]
}

This composite endpoint:

1. Creates sales order lines with a shared TransactionKey
2. Creates the sales order header using the same key
3. Returns the complete order information

Financial Entry Creation ​

POST /api/{env}/composite/FinancialEntry
Content-Type: application/json

{
  "Header": {
    "Journal": "90",
    "Description": "Invoice payment"
  },
  "Lines": [
    {
      "GLAccount": "1000",
      "Amount": 1000,
      "Description": "Payment received"
    },
    {
      "GLAccount": "1300", 
      "Amount": -1000,
      "Description": "AR clearing"
    }
  ]
}

This composite endpoint:

1. Creates financial lines with a shared TransactionKey
2. Creates the financial header to complete the transaction
3. Ensures balanced entries

Authentication with Globe+ ​

The proxy endpoints handle Globe+ authentication transparently:

1. Requests are forwarded with Windows authentication
2. The service account running Portway must have Globe+ access
3. Individual API tokens control access to specific endpoints

Error Handling ​

Globe+ specific error responses are preserved and forwarded:

// Globe+ validation error
{
  "error": {
    "code": "ValidationError",
    "message": "Customer 60093 not found",
    "details": {
      "field": "OrderDebtor",
      "value": "60093"
    }
  }
}

URL Rewriting ​

Portway automatically rewrites Globe+ URLs in responses to maintain proxy routing:

• Original: http://localhost:8020/services/Exact.Entity.REST.EG/Account(guid'123')
• Rewritten: https://api.company.com/api/500/Account(guid'123')

This ensures that related links in responses continue to work through the proxy.

Transaction Management ​

TransactionKey Handling ​

Composite endpoints manage TransactionKey automatically:

1. A unique GUID is generated for the transaction
2. The key is applied to all related records
3. Globe+ processes the records as a single unit

Atomic Operations ​

Composite endpoints ensure atomicity:

• All steps must succeed for the operation to complete
• Failures in any step roll back the entire transaction
• Detailed error information is provided for troubleshooting

Troubleshooting ​