-
Notifications
You must be signed in to change notification settings - Fork 2
/
README
67 lines (37 loc) · 1.77 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
GitHub repository for building AXIS java object from BIG-IP WSDLs
Requirements:
This is tested on linux machines with the following packages
installed an in the executatble path:
maven2
and have Internet access to the maven public repositories.
Instructions:
Step 1. Edit the pom.xml file setting the properties to your BIG-IP.
This will enable the build to login to your and download your version
of the iControl WSDLs.
You need to edit the following three properties starting on line 11.
<properties>
<bigip>192.168.200.145</bigip>
<bigipusername>admin</bigipusername>
<bigippassword>admin</bigippassword>
</properties>
You can test your values by opening a web browser to:
https://[bigip]/iControl/iControlPortal.cgi
and when prompted for basic credentials use the [bigipusername] and [bigippassword]
you put in the pom.xml file. The build script will attempt to fetch the
WSDL files from your BIG-IP each time you run it. The actual git script objects are
less than 50kB (basically size of a jpeg on a web page) so you can keep different
version of the iControl jar for each version of BIG-IP you code against.
Step 2. Use maven to build AXIS java objects and optionally install them
To build you can issue:
mvn package
If you are only working with one version of the iControl object (or just the latest!)
you can also install the jar file into your local maven repository
mvn install
Note:
If the credentials to get to the BIG-IP or wrong or the BIG-IP can not be reached,
the build process will do very little and build an empty jar file. No WSDLs = no
java objects!
You will see the build script first get the WSDLs and then build each. If you
do not see this, then it had problems getting to your BIG-IP to get the WSDLs.
Enjoy!
John Gruber