BIP20000 - BIP20057
- BIP20000
- Integration server <insert_1> started using work directory <insert_2> at version <insert_3>.
- Severity
- 0 : Information
- BIP20001
- Integration server <insert_1> stopped.
- Severity
- 0 : Information
- BIP20002
- Integration node <insert_1> started at version <insert_2>.
- Severity
- 0 : Information
- BIP20003
- Integration node <insert_1> stopped.
- Severity
- 0 : Information
- BIP20004
- Integration server <insert_1> started by integration node <insert_2> at version <insert_3>.
- Severity
- 0 : Information
- BIP20005
- Create integration server <insert_1>.
- Severity
- 0 : Information
- BIP20006
- Delete integration server <insert_1>.
- Severity
- 0 : Information
- BIP20007
- Start integration server <insert_1>.
- Severity
- 0 : Information
- BIP20008
- Stop integration server <insert_1>.
- Severity
- 0 : Information
- BIP20009
- Restart integration server <insert_1>.
- Severity
- 0 : Information
- BIP20010
- User <insert_1> logged in.
- Severity
- 0 : Information
- BIP20011
- User <insert_1> logged out.
- Severity
- 0 : Information
- BIP20012
- User <insert_1> failed to log in.
- Severity
- 0 : Information
- BIP20013
- User <insert_1> is locked out after too many failed login attempts from IP address <insert_2>.
- Severity
- 0 : Information
- BIP20014
- User <insert_1> is not authorized to make request <insert_2> <insert_3>, reason <insert_4>.
- Severity
- 0 : Information
- BIP20020
- Received REST Request with method <insert_1> and path <insert_2>.
- Severity
- 0 : Information
- BIP20021
- Completed REST Request with method <insert_1> and path <insert_2>, the HTTP response status is <insert_3>.
- Severity
- 0 : Information
- BIP20030
- Creating resource <insert_1> of type <insert_2>.
- Severity
- 0 : Information
- BIP20031
- Action state change <insert_3> on resource <insert_1> of type <insert_2>.
- Severity
- 0 : Information
- BIP20032
- Successfully completed state change <insert_3> on resource <insert_1> of type <insert_2>.
- Severity
- 0 : Information
- BIP20033
- Failed to completed state change <insert_3> on resource <insert_1> of type <insert_2>.
- Severity
- 0 : Information
- BIP20034
- Deleted resource <insert_1> of type <insert_2>.
- Severity
- 0 : Information
- BIP20035
- Rejecting action <insert_3> for resource <insert_1> of type <insert_2>.
- Severity
- 0 : Information
- BIP20036
- Successfully completed action that <insert_3> resource <insert_1> of type <insert_2>.
- Severity
- 0 : Information
- BIP20037
- Failed to complete action <insert_3> on resource <insert_1> of type <insert_2>.
- Severity
- 0 : Information
- BIP20040
- Deploy of BAR file <insert_1> was completed successfully.
- Severity
- 0 : Information
- BIP20041
- Deploy of BAR file <insert_1> was completed successfully, but there were one or more failures which may mean the deployed resources are unable to execute.
- Severity
- 0 : Information
- BIP20042
- Deploy of BAR file <insert_1> was rejected.
- Severity
- 0 : Information
- BIP20043
- Stopping all deployed resources prior to deploy of the bar file <insert_1>.
- Severity
- 0 : Information
- Explanation
- The deploy operation requested that all applications are stopped while the deploy occurs.
- BIP20044
- Restarting all deployed resources following deploy of the bar file <insert_1>.
- Severity
- 0 : Information
- Explanation
- The deploy operation requested that all applications were stopped for the duration of the deploy. The deploy is complete and the applications are being restarted.
- BIP20045
- Stopping all deployed resources prior to delete of resources.
- Severity
- 0 : Information
- Explanation
- The delete operation requested that all applications are stopped while the delete occurs.
- BIP20046
- Restarting all deployed resources following delete of resources.
- Severity
- 0 : Information
- Explanation
- The delete operation requested that all applications were stopped for the duration of the delete. The delete is complete and the applications are being restarted.
- BIP20050
- The offline command <insert_1> created resource <insert_2> of type <insert_3>.
- Severity
- 0 : Information
- BIP20051
- The offline command <insert_1> will action state change <insert_4> on resource <insert_2> of type <insert_3>.
- Severity
- 0 : Information
- BIP20052
- The offline command <insert_1> successfully completed state change <insert_4> on resource <insert_2> of type <insert_3>.
- Severity
- 0 : Information
- BIP20053
- The offline command <insert_1> failed to complete state change <insert_4> on resource <insert_2> of type <insert_3>.
- Severity
- 0 : Information
- BIP20054
- The offline command <insert_1> deleted resource <insert_2> of type <insert_3>.
- Severity
- 0 : Information
- BIP20055
- The offline command <insert_1> rejected action <insert_4> on resource <insert_2> of type <insert_3>.
- Severity
- 0 : Information
- BIP20056
- The offline command <insert_1> successfully performed the action <insert_4> on resource <insert_2> of type <insert_3>.
- Severity
- 0 : Information
- BIP20057
- The offline command <insert_1> failed to perform the action <insert_4> on resource <insert_2> of type <insert_3>.
- Severity
- 0 : Information